Capstan pricing, every number on one public page.

All fourteen come with it, and you pay for none of them separately. Every module is included in every paid plan at no extra charge, switched on when the plan starts, and none appears on an invoice at any headcount. That is an inclusion rather than a discount: the product carries each module at zero and skips it when it bills, so there is no arrangement to withdraw at renewal, and the plan per-seat price is the only charge. There are no add-ons and nothing is bought or metered module by module. The modules still need a paid plan underneath them, so a free workspace gets the core only. Payroll here means the input pack we compile for your payroll partner rather than a payroll engine: we compute no statutory payroll and file nothing with any authority.

Everything in the core column on this page. The free plan is the complete core HRIS: people, leave, attendance, onboarding, documents, workflows, self-service and reports, for up to 20 active employees. It is not a trial and it does not expire. The limit counts concurrently active employees, so someone who has exited and someone serving out their notice do not use up one of your twenty. The one thing the free plan does not carry is the modules; the whole module platform comes with a paid plan. The twenty are not lost when you do pay: a paid plan carries them, and charges you for the employees past twenty.

No. The modules come with a paid plan. A workspace on the free plan stays on the core HRIS: the in-app catalogue shows those modules locked, with an upgrade prompt rather than a subscription quietly starting underneath it. The rule is enforced in the database function that grants an entitlement, not in the interface, so there is no path around it. The practical consequence for you: the free core is genuinely free rather than a metered surface, and moving to a paid plan turns on the whole platform at once, at no extra charge, rather than starting a stack of per-module bills.

The twenty-first concurrently active employee is refused until the workspace moves to a paid plan. The limit is enforced at the point an employment is activated rather than in the web interface, so a scheduled activation that runs at midnight hits exactly the same wall a person clicking a button would. Nothing about the software changes when you move: every plan runs the identical core, and no core feature is behind the boundary. What a paid plan buys is the headcount limit going away and the whole platform, all fourteen modules, coming with it. What it costs at that moment is one seat, not twenty-one: the twenty free seats are carried into the paid plans, so the plan charge starts at the twenty-first person. Hiring one person cannot take you from paying nothing to paying for a whole roster.

Only the ones past twenty. The twenty seats that are free on the free plan are carried into the paid plan instead of being withdrawn when you start paying, so a workspace of twenty-one people is charged the plan rate on one seat, a workspace of sixty is charged on forty, and a workspace of twenty or fewer is charged nothing at all. The per-seat plan charge on the employees past twenty is the whole bill: every module is included in the plan, so nothing is added on its own unit. The twenty are the free core carried forward, and the modules come with the plan.

No. Growth is the single paid tier, and every paid workspace runs the identical product on it. There is no second tier to upsell you to and nothing held back for one. Some controls that enterprise buyers often ask about, single sign-on with SAML and IP allow-listing, are not built yet, and we would rather say so than sell a tier around them: when they ship they arrive for everyone on the paid plan, not behind a higher price.

Everyone on the roster when the count is taken: people who have joined, whose last working day has not passed, and who have not exited. That includes someone working out their notice, because they are still employed and still using the product. Your plan then charges that roster less the twenty seats it includes, and nothing else bills: the whole module suite is part of the plan, so there is no separate per-module count on top of your seats.

No, and it is worth keeping them apart even though they share a number. The cap is a limit: it counts concurrently active employees, it is enforced at the moment an employment is activated, and it refuses the twenty-first activation on a free workspace until that workspace moves to a paid plan. Someone who has exited and someone serving out their notice are not active, so neither uses up one of those twenty places. The included seats are an amount of money rather than a limit: they come off the billed count, which is your roster as of today and does include people on notice, and they refuse nothing, because a paid workspace has no headcount limit to refuse anything against. The practical difference shows up in one case. Twenty active people plus two on notice is inside the free cap, so that workspace can stay on the free plan; the same workspace on a paid plan has a roster of twenty-two, which is two billable seats.

Monthly by default. The rate is quoted per employee per month, and a new paid workspace lands on the monthly cadence, which re-reads your seat count each month. If you would rather commit for longer you can prepay a term instead: quarterly at the base price, half-yearly with 5% off, or annual with 10% off. Those discounts are data in the price book rather than something written into the software, which is why they are published on the pricing page and can change without a release. Whichever cadence you pick, the plan and the whole included module suite sit on one term with one renewal date, so there are no staggered per-module renewals to juggle. A cadence change applies at your next renewal, never mid-term.

New people are billed rather than riding free until renewal. On the monthly cadence the seat count is re-read each month; on a prepaid term a monthly true-up bills the net new seats since your last baseline, prorated from the day it runs to the end of your term, on its own invoice that settles like any other and shares your renewal date. Billable seats are the ones past the twenty your plan includes, so a workspace that grows from eighteen people to twenty-two is charged on two seats rather than on four. Seats you lose are not refunded on the day; on a prepaid term the count comes down at your next renewal. Because every module is included in the plan, there is nothing to enable or disable for a fee: your bill only ever moves with your seat count.

One of the two books published on the pricing page: USD, or INR for Indian tenants. Your billing currency is derived from your billing country at setup, India in rupees and everywhere else in US dollars, so it follows where you are rather than being a picker you choose. The selector at the top of the pricing page switches what you see, never what you pay. Each book is a flat set of figures set directly, not a live foreign-exchange feed and not one book multiplied into another, so an invoice never contains a conversion we would not honour. If a currency has no book configured, invoicing is blocked rather than charging dollar-sized numbers under a different currency code.

Nothing, mid-term. The price book is append-only: a change is a new row with its own start date, never an edit to the row you bought against. Your plan per-seat price is captured onto your subscription when the plan is granted, so a rise reaches new customers straight away, reaches you at your next renewal, and never reaches you retroactively or in the middle of a term you have already paid for. Changes are announced and dated on this page.

Not a self-serve one yet, and we are not going to call an order form a checkout. You request the upgrade from the Billing page inside the app, supplying what is needed to raise an invoice: legal entity, billing contact and email, billing address and tax id, plus a purchase-order reference if your finance team needs one. The request lands in a queue here and a person grants the plan and raises the invoice by hand. The whole module suite is switched on with the plan, so there is nothing further to enable or approve. Self-serve card checkout is built, but built is the whole of it: the request and response shapes come from our payment provider’s published documentation and have never run against a live account of theirs, and going live is gated on our own entity structure as well. We are not going to call that proven. When it opens, this answer changes. What will not change: no sales call, no quote, and no number on this page that depends on who you are.

There is nowhere in Capstan for a card number to live. No card field, no card form, no column that could hold one: the payment provider is the merchant of record and takes the payment on its own hosted page, and what we store is a reference and an amount, an event id, a payment id, a status, a figure and a currency. That is the entire footprint, and it is a property of the schema rather than a promise about our conduct. We also store no auto-debit mandate, so a renewal amount that has moved with your headcount is always shown to you before it is paid rather than pulled silently.

Nothing at all for thirty days. Your term ends, the renewal invoice is issued and the term enters a grace period: access is uninterrupted, a customer who is late is still a customer, and your admins see an honest in-grace banner rather than a locked door. We warn you sixty days out from renewal, thirty days out, on the day the invoice is issued, and again five days before the door closes, and the last of those notices cannot be muted. If the invoice is still unpaid thirty days after it was issued, which is the day it falls due, the workspace is suspended: people cannot sign in, and not one row of your data is touched or deleted. Your one-click export keeps working the whole time, because the export endpoints deliberately sit outside the suspension check. Reinstating is a person here recording that your payment arrived; a payment that lands on a suspended workspace is recorded and held for that decision rather than silently unlocking the door. Deletion happens only on your instruction or your configured retention schedule, never as a penalty. A workspace on the free plan has no subscription at all, so it can never be suspended for non-payment.

No. A term you have prepaid is not refunded. Moving off a paid plan cancels the term without paying back the remainder, and seats you drop come off at your next renewal rather than on the day. What you do not lose is money we were never owed: an overpayment is not absorbed. It becomes a credit on your workspace, recorded in an append-only ledger, and it is applied against your next renewal, so a credit-covered renewal settles with no money moving. The balance is visible on your billing page rather than something you have to ask about.

No. No setup fee, no implementation package, no onboarding fee, no platform fee and no mandatory professional services. The prices on this page are the whole commercial relationship. The only commitment you make is the prepaid cycle you pick, and the shortest of those is a quarter.

No. Capstan installs to a phone home screen on every plan, including the free one, and charging for the mobile app is the old world’s trick. It is a progressive web app rather than a store download, which means it updates when the product does and there is no review queue between a fix and your phone. On a touch device the product offers an install button; on iOS you use Safari’s own Add to Home Screen, because faking a prompt the browser does not provide would be worse than saying so.