Revenue Management.
An in-platform financial layer that models money as a state machine — turning candidate pipeline motion into forecasted, booked, and lost revenue in real time.
At a glance.
"Revenue isn't real until there's an offer on the table — so that's exactly where the number should appear, and not a stage sooner."
What it is, why it exists.
Revenue Management brought the entire financial layer inside HireBound. It ties a revenue model to every role, calculates money automatically as candidates move through the pipeline, and gives Team Owners a live dashboard of forecasted, booked, and lost revenue — down to the individual recruiter.
Agencies were running their financials in spreadsheets alongside the platform — manually tallying which placements had closed, which were still in play, and which had fallen through. Numbers were always stale, and the cost of a candidate backing out after an offer was completely invisible.
The core design challenge was modeling money as a state machine. Revenue isn't a single number; it changes meaning depending on where a candidate sits. An offer released is forecasted money — real, but not guaranteed. A candidate joined is booked money — invoice it. A candidate who backs out is lost money — and that loss needs to be counted, not quietly erased. Getting those states and their trigger points right was the whole job.
The rules that shaped the system.
The mandate: give agencies a trustworthy, real-time view of revenue that updates itself as recruiters do their normal work — without forcing revenue complexity onto customers who don't need it.
Opt-in by Design
Revenue Management is disabled by default and enabled by Team Owners from Admin Settings. Not every customer is an agency tracking placement fees, so the feature stays invisible until switched on.
The product stays clean for non-agency customers; agencies get depth without imposing it on anyone else.
Configure Once
Revenue models attach to the role, not the opening. The same role (e.g., Backend Engineer for a given client) carries the same fee structure across every opening it appears in.
No repetitive setup and no chance of inconsistent numbers across openings for the same role.
Pipeline Drives Revenue
Revenue calculates itself off stage changes recruiters already make. The acceptedCTC field appears exactly when a candidate hits "Offer Released," and money flows through the states automatically from there.
Recruiters do no extra data entry; the dashboard is just a truthful read of their existing work.
What we learned, card by card.
How agencies think about revenue
Studied the two standard compensation structures in Indian recruitment (fixed fee and percentage-of-CTC, with 8.33% as the common rate).
Agencies fundamentally distinguish committed from projected revenue — treating them as different numbers with different jobs.
Built the model around both compensation structures rather than forcing one, and split the dashboard into Forecasted vs. Booked.
Where revenue becomes real
Mapped the candidate lifecycle to find the honest trigger point for calculating money.
Anything before "Offer Released" has no CTC and therefore no number to calculate; "Joined" is when money is truly earned.
Set the two trigger points precisely — Offer Released for Forecasted, Joined for Booked — and ruled out calculating at earlier stages.
Cost of backouts
Recognized that a candidate backing out after an offer isn't a neutral event — it's lost revenue and a quality signal.
Silently removing that candidate from the forecast would hide a real financial cost and erase a signal about pipeline quality.
Designed Backout Candidates and Lost Revenue as first-class columns — visible, managed, and reportable.
Consistency with existing dashboards
Reviewed HireBound's existing "Recruiters Performance" and "Teams Performance" tables.
A hierarchical Team → Recruiter structure was already the mental model admins were using.
Modeled the revenue dashboard on the same pattern so admins met a familiar layout instead of learning a new one.
Revenue as a state machine.
Revenue is modeled as a state machine, not a static value. Each state is anchored to a real moment in the candidate pipeline — no silent numbers, no phantom forecasts.
Candidate Created
Candidate enters the pipeline. No revenue yet — there is no CTC to calculate.
Interview
Candidate progresses through interviews. Still no revenue — nothing has been offered.
Offer Released
acceptedCTC is captured. This is the first honest moment for money.
Forecasted Revenue
The number becomes real for cash-flow forecasting — visible to Team Owners, not yet invoiceable.
Joined
Candidate joins. Forecasted → Booked. This is invoiceable revenue.
Booked Revenue
Moves from the forecast into realized revenue on the dashboard.
Backout
Candidate backs out after offer. Forecasted → Lost. The cost is counted, not quietly erased.
Lost Revenue
Feeds the Backout Candidates column and the Quality Score — pipeline health becomes measurable.
Modeling revenue as a state machine means every number on the dashboard traces back to a specific pipeline event — the platform can always answer why a number changed.
Fixed Fee vs. Percentage of CTC.
Two compensation structures exist in Indian recruitment, and Revenue Management supports both — attached at the role level so every opening for that role inherits the same math.
Fixed Fee
A flat placement fee agreed with the client, independent of the candidate's CTC. Predictable, simple, and common for retained or executive search engagements.
Used when the agency and client agree on a per-placement price upfront.
Percentage of CTC
A share of the candidate's annual Cost to Company. 8.33% is the standard rate in Indian recruitment (one month's CTC), and is the default in the model.
Used when compensation is variable and tied to seniority — the majority of contingent recruiting.
Both models needed to exist because forcing one would silently misprice half the market. The role-level attachment means the calculation is decided once and applied everywhere.
Team → Recruiter hierarchy.
The dashboard intentionally mirrors HireBound's existing performance tables — Team aggregate first, individual recruiters drilling down beneath — to reduce learning effort for admins already using the platform.
Team Level
- Forecasted Revenue — committed but not yet earned
- Booked Revenue — realized, invoiceable
- Lost Revenue — surfaced from backouts
- Quality Score — team-wide pipeline health
- Achievement % — against target, color-coded (green 80%+, yellow 50–80%, red below)
The first row an admin sees — the team's financial state at a glance.
Recruiter Level
- Forecasted Revenue — recruiter's own pipeline
- Booked Revenue — placements they closed
- Lost Revenue — attributed backouts
- Quality Score — closure minus backout rate
- Achievement % — same color-coding, individual scale
Same metric shape as the team row, so the mental model doesn't change between levels.
Achievement % is color-coded (green 80%+, yellow 50–80%, red below) for at-a-glance status — a leadership can scan the table without reading numbers.
Contribution and business outcomes.
Modeled revenue as a state machine
Forecasted → Booked, with Lost as a branch — and defined the exact stage triggers that move money between states.
Made the "Offer Released" call
Anchored calculation to the first moment a real CTC exists — not earlier — so the number is always defensible.
Designed Backout & Lost Revenue as first-class columns
Turned invisible drop-off into a managed metric leadership can act on.
Specified the Quality Score
Recruiters are judged on pipeline health (closure minus backout), not raw offer volume — aligning incentives with closeable revenue.
Role-level configuration + opt-in module
Attached revenue models at the role level to eliminate repetitive setup, and kept the whole module opt-in to protect non-agency users from complexity.
Hierarchical Team → Recruiter dashboard
Color-coded achievement (green 80%+, yellow 50–80%, red below) for at-a-glance status, mirroring existing performance tables.
Pulled agency financials out of spreadsheets and into the platform — one source of truth, always current.
Gave Team Owners a live cash-flow forecast by separating committed from projected revenue.
Made the cost of candidate backouts visible for the first time, enabling recruiter-level quality conversations.
Increased stickiness with the core agency ICP by owning a workflow they previously ran outside the product.
Created a quality metric leadership can act on, shifting recruiter incentives from volume toward closeable pipeline.
Learned, improved, next.
Revenue Management did more than add a dashboard — it taught the platform to understand money the way an agency does: as something that's forecasted, then booked, and sometimes lost.
By anchoring every number to a real moment in the pipeline and making loss as visible as gain, the discipline underneath the feature turned out to matter more than the surface: draw the state boundaries once, and every downstream view stays honest.
It turned HireBound from a system that tracked candidates into one that tracked the business — the next chapter is compounding on that foundation with invoicing, targets, and forecasting workflows.