Everyman Brand Archetype
Automotive
HRIS/HCM
Deputy
Won hourly-workforce management by connecting scheduling, time tracking, and compliance in one shift-based operating system, despite ADP, Workday, and UKG’s enterprise scale and When I Work’s SMB simplicity.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Deputy proved product-market fit through repeat usage across shift-based businesses: the roster became the reference point for clock-ins, breaks, overtime, timesheet approval, and compliance. It served more than 1.5 million workers and 375,000 workplaces across more than 100 countries. Expansion into payroll, HR, messaging, and analytics followed demonstrated usage of the core scheduling and time-attendance workflow.
Question this model answers
We need to know whether we have product-market fit.
BUSINESS MODEL
SaaS
HOW THEY BUILT IT
'- Founded in Australia; built a cloud workforce-management platform for hourly and shift-based work.
- Made the roster the core system: scheduling, clock-ins, breaks, overtime, timesheet approval, and compliance derive from the same shift plan.
- Expanded into Deputy HR, payroll through Paycor, messaging, analytics, tasking, and demand forecasting.
- Served more than 1.5 million workers and 375,000 workplaces across more than 100 countries.
- Priced per user per month: Lite at $5, Core at $6.50, and Pro at $9, with HR at $2, Messaging+ at $1.95, Analytics+ at $1.50, and Deputy Payroll via Paycor at $8 plus a $49 monthly base fee.
- Introduced a $30 monthly minimum spend on Lite, Core, and Pro plans from September 2025.
HOW TO ARCHITECT IT
1. Identify an operational record that governs daily work—shift, job, order, appointment, or asset.
2. Build the core workflow around that record so every downstream action derives from it.
3. Make compliance and auditability part of the workflow, not a separate reporting layer.
4. Add modules only when they reuse the core record and create a natural expansion path.
5. Price per active worker or operational unit, because that is the customer’s value unit.
6. Use integrations to connect payroll, HR, and finance without owning every adjacent system.
7. Avoid expanding into full HCM before the core operational workflow is reliable across industries. The common mis-build is adding HR modules before scheduling and time data are trusted as the system of record.
DISTRIBUTION MODEL
Product-Led Growth, SEO, Partnerships, Direct Sales
HOW THEY OPERATIONALIZED
'- Self-serve trials and published per-user pricing let shift-based businesses adopt scheduling and time tracking without a long procurement process.
- SEO captured demand for employee scheduling, time and attendance, shift planning, and Deputy alternatives.
- Payroll, HRIS, POS, and accounting integrations embedded Deputy in the customer’s operational stack.
- Partners and resellers extended implementation and localization across retail, hospitality, healthcare, and staffing.
- Direct sales targeted multi-location businesses needing demand forecasting, compliance, and enterprise controls.
HOW TO REPLICATE WHAT WORKED
What Worked
Use self-serve entry pricing to acquire shift-based businesses, then expand through payroll, HR, and analytics modules as operational dependence grows.
Trap if Copied Blindly
Product-led distribution fails if the workflow requires complex compliance configuration; self-serve onboarding can create poor implementations and churn in regulated industries.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — DEMAND-DRIVEN LABOR OPTIMIZATION. The gap is connecting sales, foot traffic, appointments, and operational demand directly to staffing decisions and labor cost.
GOLDMINE 2 — COMPLIANCE-NATIVE SCHEDULING. Predictive-scheduling, break, overtime, and union rules remain fragmented; a compliance engine embedded in scheduling can become a durable differentiator.
GOLDMINE 3 — EMBEDDED PAYROLL FOR FRONTLINE WORK. Instant pay, earned-wage access, and payroll automation can deepen the platform’s role in hourly work.
THE TRAP TO WATCH
THE PIT — PER-USER PRICING DURING SEASONALITY. Retail and hospitality businesses add temporary staff during peaks; monthly per-user billing can create bill shock and churn.
THE SECOND PIT — HR MODULE SPRAWL. Adding HR, payroll, and analytics before the scheduling workflow is reliable can create integration debt and support burden.
MOVE WITH CAUTION
Do not build payroll or compliance features without jurisdiction-specific accuracy; wage-and-hour errors create direct financial and legal liability.
2
MARKET
MARKET TYPE
Red Ocean
WHY THEY WON
Workforce management is a Red Ocean with ADP, Workday, UKG, Ceridian, When I Work, and numerous scheduling tools. Deputy’s opening was the hourly-workforce wedge: scheduling, time tracking, and compliance needed to operate as one workflow rather than disconnected tools. It exploited this by making the roster the system of record and pricing per worker. The lesson is that a Red Ocean entrant can win by owning the operational record for a specific workforce type.
Deputy compared segments and concentrated on hourly, shift-based businesses across retail, hospitality, healthcare, and staffing. These customers had recurring scheduling complexity, compliance exposure, and multi-location operations. Deputy avoided competing head-on with enterprise HCM suites for office-based workforces and instead built around the operational reality of shift work.
Question this model answers
We need to identify the best market segment.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Deputy entered by attacking the segment enterprise HCM vendors underserved: hourly, shift-based, multi-location businesses that needed modern scheduling and time tracking without enterprise-suite complexity. It avoided a frontal attack on Workday and ADP’s payroll and HCM strength, instead building a mobile-first operational workflow. The critical bet was that shift-based businesses would adopt a modern platform for scheduling and time tracking before expanding into payroll and HR. The prerequisite was reliable compliance logic and payroll integrations; the approach would fail if compliance errors or poor mobile reliability undermined trust.
FOOTHOLD STRATEGY
Beachhead Strategy
THE HOW
Deputy’s initial beachhead was hourly, shift-based businesses needing scheduling, time tracking, and compliance in one system. They were reachable through self-serve trials, SEO, and partner channels; they could pay because labor cost, compliance risk, and manager time were recurring problems. Deputy solved the job of managing shift-based work. The path outward was from scheduling and time attendance to payroll, HR, analytics, and enterprise workforce management.
MARKET TYPE PLAYBOOK
RULE 1 — TARGET THE UNDERSERVED WORKFORCE TYPE: Hourly and shift-based work has different needs from salaried enterprise HR.
RULE 2 — MAKE COMPLIANCE OPERATIONAL: Breaks, overtime, and wage rules must be embedded in scheduling.
RULE 3 — PRICE PER ACTIVE WORKER: The worker is the customer’s value unit and scales with operations.
RULE 4 — FAILURE MODE: A workforce entrant fails if payroll or compliance errors undermine trust in the core scheduling workflow.
In a Red Ocean, entrants win by owning the operational record for a specific workforce or workflow.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Identify the workforce or workflow the incumbent treats as secondary.
RULE 2 — Build a mobile-first, operationally native experience for that segment.
RULE 3 — Use integrations to connect to the incumbent’s strengths without competing everywhere.
RULE 4 — Reject a flanking attack if the incumbent can extend into the segment without disrupting its core product.
A flanking attack is appropriate when incumbents are strongest in a different buyer value or workforce type.
A beachhead strategy works when one workforce segment has concentrated pain, reachable buyers, and a clear expansion path.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Choose a segment with recurring operational complexity and compliance exposure.
RULE 2 — Solve the complete core workflow before adding modules.
RULE 3 — Use the beachhead’s references to enter adjacent industries and larger accounts.
RULE 4 — A beachhead fails when the segment is too seasonal or too customized to create repeatable economics.
Deputy’s beachhead was hourly, shift-based businesses needing scheduling, time tracking and compliance in one system; failure occurs when the segment is too seasonal or too customised to create repeatable demand.
HOW TO APPLY MARKET ENTRY STRATEGY
Deputy attacked the hourly, shift-based, multi-location segment that enterprise HCM vendors underserved; failure occurs when an incumbent can extend into the segment without disrupting its core.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN SELF-SERVE OPERATIONAL SAAS:
1. PUBLISHED PER-USER PRICING REDUCES EVALUATION FRICTION. Shift-based businesses can estimate cost and start without a sales cycle.
2. OPERATIONAL SEO CAPTURES HIGH-INTENT DEMAND. Buyers search for scheduling, time tracking, and compliance solutions.
3. PAYROLL INTEGRATIONS CREATE EXPANSION. Connecting to payroll and HR systems makes the platform part of the operational stack.
WEAKNESS
Self-serve adoption can attract very small businesses whose support and compliance needs exceed their revenue contribution.
GROWTH CAMPAIGNS
Employee-scheduling and time-and-attendance SEO; free trial and self-serve onboarding; payroll and HRIS integration campaigns; demand-forecasting and labor-optimization campaigns; Deputy Payroll via Paycor launch; retail, hospitality, healthcare, and staffing vertical campaigns; enterprise security and compliance campaigns.
| So What
Deputy’s strongest campaign was the shift-as-system-of-record message: scheduling, time tracking, compliance, and payroll all derive from the same operational record.
| Key Learning
In operational software, the winning wedge is the record that governs daily work, not the feature with the broadest appeal.
| How to Use
Identify the operational record that governs your customer’s daily work, then build every downstream workflow from it.
3
MONEY
REVENUE MODEL
Subscription, Usage-Based
Deputy chose per-user monthly pricing: Lite at $5, Core at $6.50, and Pro at $9 per user per month, with add-ons for HR, messaging, analytics, and payroll. This meter aligned cost with the number of workers being scheduled and managed. The $30 monthly minimum introduced in September 2025 protected economics for very small accounts.
Question this model answers
We need to choose the right pricing metric.
PRICING STRATEGY
Tiered Pricing, Usage-Based Pricing, Add-On Pricing
WHY THEY WON
Customers pay recurring per-user subscription fees for scheduling, time tracking, and workforce management, plus add-ons for HR, messaging, analytics, and payroll. Revenue expands as headcount grows, locations multiply, and customers adopt higher tiers or modules. Gross margin depends on support, compliance updates, SMS and messaging costs, payroll processing, and integration maintenance.
TARGET AUDIENCE
Small shift-based businesses (Lite; want scheduling, time tracking, and compliance); multi-location retailers and hospitality groups (Core; want auto-scheduling, forecasting, and labor optimization); larger hourly-workforce operators (Pro; want SSO, access controls, and 24/7 support); businesses needing payroll (Payroll add-on; want integrated payroll and HR).
Deputy charges per user per month: Lite at $5, Core at $6.50, and Pro at $9. Add-ons include HR at $2, Messaging+ at $1.95, Analytics+ at $1.50, and Deputy Payroll via Paycor at $8 per user plus a $49 monthly base fee; a $30 monthly minimum applies to monthly Lite, Core, and Pro plans from September 2025.
CUSTOMER BUYING BEHAVIOUR
A manager or operations leader typically begins when scheduling, timesheets, or compliance create visible administrative cost. It evaluates Deputy against scheduling tools and workforce-management suites; adoption starts with scheduling and time tracking, then expands into payroll, HR, and analytics.
WILLINGNESS TO PAY
CORE INSIGHT
Customers are not buying scheduling software; they are buying controlled labor cost and compliance assurance.
RULES OF ADOPTION
RULE 1 — PRICE PER WORKER: The worker is the unit that scales with the customer’s operations and value received.
RULE 2 — SELL LABOR OPTIMIZATION: Demand forecasting and auto-scheduling reduce overstaffing and overtime.
RULE 3 — MAKE COMPLIANCE OPERATIONAL: Break, overtime, and wage rules must be enforced in the workflow.
RULE 4 — WATCH THE SEASONALITY TRAP: Per-user monthly pricing can create bill shock when temporary staff are added during peaks.
The buyer is really buying labor-cost control, evidenced by operations, HR, and payroll budgets.
REVENUE RISK
Seasonal workforce volatility: Retail and hospitality businesses add and remove temporary staff, creating revenue volatility and potential bill shock.
Payroll and compliance liability: Wage-and-hour, break, or overtime errors create direct financial and legal exposure.
HCM bundling: ADP, Workday, UKG, and payroll providers can bundle workforce management into broader HR contracts.
SMB support burden: Small businesses may require disproportionate onboarding and support relative to their subscription value.
Integration dependency: Payroll, POS, and HRIS integrations are important to adoption but create maintenance and partner dependency.
Funding/valuation: Deputy serves more than 1.5 million workers and 375,000 workplaces across more than 100 countries; current ARR, funding, and valuation are not publicly disclosed in the available evidence.
4
MOTION
Deputy chose product-led growth for smaller and mid-sized shift-based businesses: published per-user pricing, free trials, and self-serve onboarding let managers adopt scheduling and time tracking without a sales cycle. It added sales assistance for multi-location and enterprise customers needing compliance, forecasting, and payroll. This hybrid fit the buyer: operational value was immediate, but larger deployments required configuration and support.
Question this model answers
We need to choose between product-led growth and sales-led growth.
GROWTH EXPANSION MODEL
Land & Expand, Product Line Expansion
HOW THEY EXPAND
Deputy expanded from scheduling and time attendance into HR, payroll, messaging, analytics, tasking, and demand forecasting. It expanded within accounts as headcount, locations, and workforce complexity grew. Product-line expansion deepened the platform’s role in hourly work, while geographic expansion extended Deputy across more than 100 countries.
COMPETITIVE STRATEGY
Freemium User Acquisition
HOW THEY COMPETE
A manager searches for scheduling or time-tracking software → starts a Deputy trial → creates a roster and invites workers → workers clock in, swap shifts, and submit timesheets → compliance and payroll workflows depend on the roster → the business adds HR, analytics, messaging, or payroll → more workers and locations increase subscription revenue. The loop compounds when the roster becomes the operational system of record. It requires reliable mobile usage, compliance accuracy, and payroll integrations; it breaks if seasonal staffing creates bill shock or compliance errors undermine trust.
GTM
Deputy runs a product-led GTM with sales assistance for larger accounts.
$5–10M ARR
Self-serve trials and published pricing acquire shift-based businesses; the roster creates immediate operational value; payroll, HR, and analytics expand account value. The primary motion is product-led for SMB and mid-market, with sales-assisted expansion for multi-location and enterprise deployments. The transferable implication is that operational SaaS should make the core record immediately useful, then expand into the workflows that depend on it.
SUSTAINING MOATS
High Customer Lock-In
The moat is Deputy’s role as the system of record for hourly work: rosters, shifts, clock-ins, breaks, timesheets, compliance records, and payroll data accumulate in one platform. Once scheduling, time attendance, and payroll depend on Deputy, replacement disrupts daily operations. The moat strengthens with each worker, location, and module; it weakens if payroll or compliance data remains external.
| Why This Moat Lasts
Customer lock-in lasts when the platform becomes the authoritative source for recurring operational data.
| Standard Rules
RULE 1 — OPERATIONAL RECORD DEPENDENCE: Rosters, timesheets, and compliance records cannot be replaced without disrupting daily work.
RULE 2 — PAYROLL CONNECTIVITY: Payroll and HR integrations deepen workflow dependence.
RULE 3 — MULTI-LOCATION SCALE: More locations and workers increase migration cost.
| The Signal
Deputy served more than 1.5 million workers and 375,000 workplaces across more than 100 countries, with published per-user pricing and payroll, HR, messaging, and analytics expansion. The moat does not protect against seasonal workforce contraction, compliance errors, or HCM-suite bundling.
ARR
JOURNEY
Pre-$1M ARR
BUILD THE SHIFT WORKFLOW. Deputy focused on scheduling, clock-ins, and timesheets for hourly work.
WATCH: mobile reliability and manager adoption.
$1–5M ARR
PROVE COMPLIANCE VALUE. Break rules, overtime, and wage-and-hour workflows made Deputy more than a scheduling app.
WATCH: jurisdiction complexity and support burden.
$5–10M ARR
EXPAND INTO PAYROLL CONNECTIVITY. Payroll and HRIS integrations deepened the platform’s role in workforce operations.
WATCH: integration maintenance and partner dependency.
$10–50M ARR
SCALE MULTI-LOCATION WORKFLOWS. Deputy added demand forecasting, labor optimization, and enterprise controls for larger operators.
WATCH: implementation complexity and sales efficiency.
$50–100M ARR
ADD HR AND PAYROLL MODULES. Deputy HR, Messaging+, Analytics+, and Deputy Payroll via Paycor expanded account value.
WATCH: module sprawl and seasonal billing friction.
$100M+ ARR
NOT REACHED as a publicly disclosed standalone milestone; Deputy serves more than 1.5 million workers and 375,000 workplaces, but ARR is not publicly disclosed.
BREAKDOWN
THE STANDARD
Build around the operational record that governs daily work, then expand into the workflows that depend on it.
THE SEQUENCE
1. Identify the record that governs the customer’s daily operations—shift, job, order, or appointment.
2. Build the core workflow around that record so downstream actions derive from it.
3. Make compliance and auditability part of the workflow.
4. Price per active worker or operational unit.
5. Add modules only when they reuse the core record and create a natural expansion path.
Deputy used the roster as the system of record, then expanded into time tracking, compliance, payroll, HR, and analytics.