Rebuilding a workforce marketplace model after the business changed
A workforce technology company had completed a fast commercial pivot, but its planning model still followed worker activity and localization assumptions that no longer drove the business. The post-pivot company was an employer-and-recruiter marketplace with placement volume, a platform commission, a smaller SaaS layer and occasional implementation revenue.
Placement value remains visible before the platform commission becomes recognized revenue.
Employer seats and subscription price explain recurring software revenue separately from placements.
Historical employer-account activity establishes the base for each forward assumption.
Sales and marketing spend can be tested against first-year account economics instead of an obsolete engagement metric.
WHY THIS WASN’T A TEMPLATE EXERCISE
The model had to respect
how the business actually moved.
The reconstructed structure separates placement GMV from recognized platform revenue, keeps SaaS and implementation revenue distinct, applies stream-specific deductions only where they belong and bridges historical account activity into the forecast.
The old KPI described a product the company no longer sold
Worker activity could still be calculated, but it no longer explained how the post-pivot business acquired employer accounts or earned revenue. Keeping it as the primary driver would have made a tidy model of the wrong company.
Gross placement value was not platform revenue
Employers paid for completed placements, but most of that value belonged elsewhere in the marketplace. The model had to preserve gross merchandise value while recognizing only the platform take rate as core revenue.
Each revenue stream carried different economics
Marketplace commission, employer software subscriptions and implementation work could not share one margin assumption. The SaaS layer carried a partner deduction that did not apply to the marketplace rake, while implementation could be absent for a new account.
MODEL ARCHITECTURE
From operating activity
to a decision-ready view.
Each layer has one job. Together they keep the commercial story, unit economics and cash consequences on the same timeline.
Historical account base
Employer accounts, placements and existing revenue are normalized into an actuals bridge before any forward growth assumption is applied.
Placement volume
Account cohorts, placements per account and average placement value build gross merchandise value by period.
Platform rake
A configurable take rate converts eligible placement GMV into recognized marketplace revenue without losing the gross-volume view.
SaaS and implementation
Employer seats and price generate software revenue; the applicable partner share is deducted only there, while implementation fees remain a separate optional stream.
Go-to-market economics
Sales and marketing costs are linked to first-year account value with explicit units, timing and cohort-level acquisition assumptions.
Integrated forecast
Revenue schedules, operating costs, statements, cash needs and scenario outputs produce a consistent set of planning and pitch-deck metrics.
WHAT THE ANALYSIS SURFACED
Useful answers,
without exposing client data.
The takeaways are intentionally qualitative. Exact assumptions, calculations and outputs remain inside the confidential client model.
A model can stay mathematically correct after becoming commercially wrong
The legacy formulas were not necessarily broken. The problem was that their main activity driver no longer represented the company that management needed to plan.
GMV and recognized revenue needed separate ladders
Placement count and average placement value explain marketplace throughput; the take rate then explains the platform share. Blending those layers would overstate revenue and hide sensitivity to commission terms.
The smaller revenue stream carried the most specific deduction
A third-party share applied to employer software revenue but not to placement commission. Stream-level logic kept that narrow contractual cost from distorting the larger marketplace engine.
A small unit ambiguity could distort acquisition spend
The source described go-to-market cost in cents per first-year account-revenue dollar without an unambiguous unit. A labeled ratio control was necessary before that assumption could support forecasts or sensitivities.
MODELING APPROACH
The working system
behind the answer.
- Historical actuals and normalized employer-account cohorts
- Employer acquisition, activation and placement-volume schedule
- Placement GMV, average placement value and platform-rake build
- SaaS seats, pricing and stream-specific partner-share schedule
- Optional implementation-fee assumptions by new account
- Sales and marketing cost tied to first-year account economics
- Integrated P&L, balance sheet, cash flow and scenario controls
- Pitch-deck metrics reconciled to the operating forecast
CASE CONFIDENTIALITY
This anonymized case explains the post-pivot operating and revenue logic without naming the company, founder, product, software partner, recruiters, customers, markets, dates, pipeline, pricing, take rate, account values, acquisition costs or forecast. The source brief, linked pitch deck, client diagrams and financial outputs remain private. The illustration is an original fictional workforce marketplace rather than a real office, product interface, team or client network.