saascode
project & workflow operations·run 153 · Jun 2026

StaffTriage

A human-led resource-planning workspace that reconciles employee-approved skills, project requirements, availability and workload, then models engagement-level margin scenarios while keeping individual assignment and employment authority with managers.

Genesis score5.92/10
Make StaffTriage real.0/500
500 more votes and StaffTriage is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
2Confirmed resource-management products
1Confirmed standardized skills taxonomies
0Reviewed margin-aware equivalents found
The case

The research confirms resource-management products but found no reviewed internal staffing product centered on engagement-margin scenarios. A named signal was miscategorized as a hiring tool and is excluded as direct competition. The skills taxonomy interface is real but requires a commercial license for production.

StaffTriage should separate project requirement, worker-stated skill, evidence, manager validation, availability, workload, accommodation and protected constraints, staffing scenario, engagement cost and margin estimate, manager decision, employee consultation, assignment command and project outcome. Historical project margin cannot establish an individual's profitability or worth.

The product must not rank people, infer skills from private messages, use protected traits or proxies, recommend adverse employment action or optimize the workforce for lowest cost. Employees need access, correction and meaningful human review. Margin is modeled at engagement level after feasible staffing, never as a per-person score.

Who pays — and why

Resource and delivery leaders at small professional-services firms balancing project fit, workload and engagement economics.

What it unlocks
A project demand record with client boundary, services, outcomes, required and learnable skills, seniority need, location and time constraints, accessibility, start and end, budget assumptions, owner and approval
A worker-controlled capability profile with declared skill, evidence, validation, interest, development goal, availability, workload, schedule, location, contractual boundaries, accommodations access boundary, correction and expiry
A staffing scenario separating eligible team combinations, requirement coverage, gaps, workload and schedule conflicts, development opportunities, engagement cost assumptions, margin range, uncertainty and reviewer comments
A decision chain with manager rationale, employee consultation where required, conflict and accommodation review, approval, assignment command, destination acknowledgment, correction and project outcome
How Genesis scored it
5.92across seven criteria
tension 6temporal 8blindspot 5buyer 6leverage 6convergence 5why-not 5
8
Temporal window

Current vertical workflow investment supports timing.

6
Productive tension

Project fit and economics must coexist with fairness, development, worker voice and human authority.

5
Why nobody did it

The private workflow-data thesis is clearer than the historic barrier.

Why it scored well

A clear services-firm buyer, confirmed resource tools and a requirement-to-scenario model make the workflow concrete.

What's holding it back

The direct competitor signal was wrong; skills inference, employee rights, bias, accommodations, private compensation and manager adoption create high risk.

Signals detected3 sources crossed
SignalGenesis research

SignalGenesis research

SignalGenesis research

Direction briefstafftriage.md
stafftriage.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.