Deputy vs When I Work vs Homebase vs a Custom Scheduling App: What 150 Staff Cost in 2026

Deputy, When I Work and Homebase against a custom shift scheduling app for a multi-location hourly team: published prices read 5 November 2026, yearly totals at 50, 150 and 300 staff, and when to build.

Deputy vs When I Work vs Homebase vs a Custom Scheduling App: What 150 Staff Cost in 2026 blog banner

Short answer: a 150-person hourly team across 8 locations pays about $6,700 to $16,200 a year for shift scheduling at the prices the vendors publish, depending on the tool and plan, and about $20,000 to $48,600 over three years. At 300 staff the same tools cost $12,600 to $32,400 a year. A custom scheduling app built as a first production version costs $15,000 to $50,000 once, so the build starts to pay for itself when your scheduling rules do not fit a plan or when headcount keeps growing. Every vendor figure below was read from the vendor's own pricing page on 5 November 2026.

If you want a range for your own build first, the AI development cost calculator gives one in about a minute.

Published prices, side by side

RoutePlan and priceWhat the price coversSource, read 5 Nov 2026
DeputyLite $5, Core $6.50, Pro $9 per user per month; minimum $30 a month per invoiceScheduling and time tracking per user; Pro adds location hierarchies, Messaging+ and Analytics+deputy.com/pricing
When I WorkEssentials $2.50, Pro $5, Premium $8 per user per monthMulti-location scheduling from Essentials; role permissions on Pro; API access, webhooks and SSO on Premiumwheniwork.com/pricing
HomebaseEssentials $30, Plus $70, All-in-One $120 per location per month; Basic is $0 for one location and up to 10 employeesUnlimited employees per location on paid plans; priced by location, not by personjoinhomebase.com/pricing
Custom scheduling app, first production version (KUMO Starter Build)$15,000 to $50,000 once, typically 2 to 3 months, code and data in your own accountsSchedules, shift swaps, approvals, rules and payroll export built to your operationKUMO published band
Custom app with several integrations or a staff portal (KUMO)$50,000 to $100,000 onceAdds POS, payroll, HR or customer-facing workKUMO published band
Ongoing engineering after launch (KUMO)$5,000 to $10,000 per month, or less once stableChanges, monitoring and upgradesKUMO published band

How to read these numbers. Subscription prices are the vendors' published list prices on the date shown, before taxes, overages, add-ons and seat growth. The custom-build figures are market ranges from 2026 studio cost guides, for the build only: hosting, model usage, third-party fees and ongoing engineering (about $4,000 to $12,000 a month in the same guides if you have no engineers) sit on top, and we say so wherever a total is compared. A standard tool is the right answer when your workflow fits it; configuration is enough when the gap is small; a custom build is justified only by a specific complexity named on this page, not by preference.

Two details on the vendor pages change the arithmetic. Deputy's prices are labelled USD excluding taxes, and its page does not say whether the figures assume monthly or annual billing, so we use them as listed. Homebase shows "$70" and "$0" together on its Plus plan without saying which is current; we used $70, the figure in its comparison section. Deputy's Pro plan also says "Contact us" in the comparison table, so treat $9 as the listed price rather than a guaranteed one.

What 50, 150 and 300 staff actually cost

These totals are KUMO's arithmetic on the published prices above. Per-user tools scale with headcount, so we multiplied each rate by the number of users; Homebase scales with locations, so we used 3 locations for 50 staff, 8 for 150 and 15 for 300.

50 staff. Deputy Core is $325 a month ($3,900 a year) and Pro $450 ($5,400). When I Work Pro is $250 ($3,000) and Premium $400 ($4,800). Homebase Plus at 3 locations is $210 ($2,520) and All-in-One $360 ($4,320).

150 staff. Deputy Core is $975 a month ($11,700 a year) and Pro $1,350 ($16,200). When I Work Pro is $750 ($9,000) and Premium $1,200 ($14,400). Homebase Plus at 8 locations is $560 ($6,720) and All-in-One $960 ($11,520).

300 staff. Deputy Core is $1,950 a month ($23,400 a year) and Pro $2,700 ($32,400). When I Work Pro is $1,500 ($18,000) and Premium $2,400 ($28,800). Homebase Plus at 15 locations is $1,050 ($12,600) and All-in-One $1,800 ($21,600).

Over three years at 150 staff, Deputy Pro comes to $48,600, When I Work Premium to $43,200 and Homebase All-in-One to $34,560. At 300 staff, Deputy Pro reaches $97,200 and When I Work Premium $86,400, which is above the whole Starter band. The fee follows headcount (or location count), not the value the scheduling creates: every hire raises the bill.

What the subscription does not include

Four costs sit outside the pricing tables and decide whether a plan stays cheaper than a build.

The upgrade that unlocks the integration. On When I Work, API access and webhooks sit on Premium at $8 a user, and Deputy's per-user add-ons run on top: payroll at $8 per user plus a $49 monthly base fee in the US, HR at $2, Messaging+ at $1.95 and Analytics+ at $1.50 (the last two come with Pro). Homebase payroll is $49 a month plus $6 per employee paid. At 150 staff, the add-ons can add $5,000 or more a year to the base plan.

Messages. Deputy charges for SMS per 160 characters, from 1 cent in the US. A schedule change that notifies 40 people costs little, but a team that texts shift offers all day pays for every message.

Rules the plan cannot model. Standard tools handle shifts, swaps and time-off requests. The cases that need workarounds are qualification rules (only certified staff on a station), rest periods between shifts, advance-notice premiums that differ by city, cross-location coverage with different pay rates, and approvals that go through a manager hierarchy.

Where the data lives. Availability, swap history and hours sit in the vendor's system. Moving off later means exporting history and retraining staff. A schedule in your own database stays yours.

Which route fits your operation

Four questions decide this faster than any feature list.

1. How many people are scheduled, and how fast is that growing? Per-user pricing doubles when headcount doubles. Between 150 and 300 staff, three years of fees reach the same size as the Starter band, so the decision moves from price to fit.

2. How unusual are your rules? If shifts, swaps and time off are all you need, a plan does it. If qualifications, rest periods or location-specific pay rules matter, you are paying for workarounds.

3. What must it connect to? Payroll, POS and HR systems are standard integrations. Anything beyond them is integration work whichever route you pick; AI workflow automation covers what that wiring involves.

4. Who sees what? Managers who approve only their own location, area leads who see several and owners who see all of them are permission rules. Building them in from the start is easier than retrofitting them on a plan.

A worked example: 8 locations and 150 staff

Picture a service business with 8 locations, 150 hourly staff, certified roles at some stations and a different overtime rule in two cities.

Homebase All-in-One: about $11,500 a year, priced by location. It handles standard shifts and time tracking; the certified roles and the city rules become manual checks.

Deputy Pro: about $16,200 a year plus payroll and HR add-ons if used. It models locations and roles, but rules specific to your operation still sit outside the plan.

Custom: a senior team builds schedules, swaps, the qualification rules, the city-specific overtime logic and a payroll export on your own database. It costs $15,000 to $50,000 once, plus ongoing engineering. The fee no longer grows with headcount, and the rules match the business. On the arithmetic above, the lower end of the Starter band is under two years of Deputy Pro at this size. For a similar multi-location decision on appointments, see Calendly vs Acuity vs Setmore vs custom, and for approval workflows see Monday vs Asana vs Smartsheet vs custom.

What a custom scheduling app includes at KUMO

KUMO builds internal tools and operations software for 10 to 100 person businesses that have no engineers of their own. A Starter Build ($15,000 to $50,000) is a launched first production version: the schedule and shift-swap flows, the rules you specified, manager permissions by location, payroll export, deployment into your own cloud account and a handover another engineer can continue from. Two to three months is typical, and the code is yours from day one. If you are moving off a tool, no-code to custom explains how the move is staged so staff and history carry over.

KUMO's founders built Volopay's first production version as its founding engineers, and the FLIN case study walks through another production build from scoped brief to launch. That is adjacent proof: a different product, with the same scoping, launch and handover discipline.

To get a band for your own operation, book a free 30-minute call with an engineer. Bring your headcount, your number of locations and the scheduling rules your current tool cannot handle.

FAQ

How much does shift scheduling software cost in 2026? At prices read on 5 November 2026, Deputy runs $5 to $9 per user per month, When I Work $2.50 to $8 per user per month, and Homebase $30 to $120 per location per month. For 150 staff across 8 locations that is roughly $6,700 to $16,200 a year.

Deputy vs When I Work vs Homebase: which is cheapest? For a large team in few locations, Homebase is cheapest because it charges per location. For a small team in many locations, When I Work's per-user rates are lowest. Deputy is the highest priced of the three at every size we calculated.

How much does a custom scheduling app cost to build? A first production version from a senior team costs $15,000 to $50,000 and typically takes two to three months. With several integrations or a staff portal it runs $50,000 to $100,000. Ongoing engineering is $5,000 to $10,000 per month, or less once stable.

When does it make sense to leave a scheduling app? When three years of fees approach the build cost, when rules need manual workarounds, or when you want schedules and hours in your own database. Two or more of those is the time to price a move.

Does Homebase charge per employee? Its paid plans are priced per location with unlimited employees, per its pricing page read on 5 November 2026. Payroll is a separate add-on at $49 a month plus $6 per employee paid.

Last verified 5 November 2026. Deputy prices from deputy.com/pricing, When I Work from wheniwork.com/pricing, Homebase from joinhomebase.com/pricing, all read on that date. Yearly and three-year totals are KUMO's arithmetic on those published prices. KUMO bands are KUMO's published prices.