Every price we charge, on one public page.

Two come with it. Payroll and Time and Attendance are included in every paid plan at no extra charge, switched on when the plan starts, and they never appear on an invoice at any headcount. That is an inclusion rather than a discount: the product holds them at zero and skips them when it bills, so there is no arrangement to withdraw at renewal. Every other module is priced individually on this page and bought on its own. Both included modules still need a paid plan underneath them, so a free workspace gets neither, and 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 cannot do is switch on a paid module; modules need 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. Paid modules require a paid plan. A workspace on the free plan is refused when it tries to enable one, with an upgrade prompt rather than a subscription quietly starting underneath it, and the in-app catalogue shows those modules locked. The rule is enforced in the database function that grants an entitlement, not in the interface, so there is no path around it. A workspace that already had a module enabled before the rule changed keeps it. The practical consequence for you: the free core is genuinely free rather than a metered surface, and your first module purchase is also your first plan purchase.

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 ability to enable paid modules. 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, on the plan. The twenty seats that are free on the free plan are carried into the paid plans 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 that is paying only because it wants a module is charged nothing at all for the plan itself. Paid modules are separate add-ons and are not covered by those twenty: a per-employee module counts your whole roster from the first person, and a module metered on its own unit, such as active contractors, recruiter seats or learners, counts that unit. The twenty are the free core carried forward, not a discount applied to everything on the invoice.

Not yet, and the product will not let anyone here sell it to you by mistake either. Scale is announced and not released: the plan carries a released flag that is switched off, and the function that grants a paid plan refuses an unreleased tier outright, so a request for Scale cannot be approved. That is why this page shows no price for it and no way to buy it. The controls it is meant to carry, single sign-on with SAML, API access, deeper administration and priority support, are not built yet, and we would rather tell you that than take an order against them. Growth is the paid plan you can buy today, and it runs the same core Scale will.

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 your per-employee modules charge the roster itself. Modules metered per active unit, such as active contractors, recruiter seats and learners, are counted on their own unit rather than on headcount.

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.

Never monthly, because there is no monthly cycle. Prices are quoted per employee per month because the month is the unit the meter runs on, and you prepay one of three terms: quarterly, which is three months at the base price; half-yearly, which is six months with 5% off; or annual, which is twelve months with 10% off. The shortest commitment anyone can make here is a quarter. Those two discounts are data in the price book rather than something written into the software, which is why they are published on the pricing page beside the prices they apply to and can change without a release. Your plan and every module you enable sit on that one term with one renewal date, so you never juggle staggered per-module renewals. A cycle change applies at your next renewal, never mid-term: the term you have paid for is the term you get. The renewal invoice is issued at the end of the term and is due thirty days later.

New people are billed rather than riding free until renewal. 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 trued up on two seats rather than on four. Seats you lose mid-term are not refunded on the day; the count comes down at your next renewal. Enabling a module mid-term works the same way, prorated from the day you enable it to your current term end, so it lands on the renewal date you already have. Disabling stops billing at the end of the current period rather than the same day, and there is no partial refund of the period you are in.

One of the two books published on the pricing page: USD, which is the Tier 1 base, or INR, which is the Indian book. The selector at the top of that page switches between them, and every figure on the page moves with it. What you are invoiced in is your workspace’s own billing currency, chosen at the point you upgrade from the currencies we hold a published book for; if you choose none, your region’s default currency applies. A local book is the USD book at a multiplier we set and publish, not a live foreign-exchange feed, so an invoice never contains a conversion we would not honour. The Indian book is set at 25 to the dollar. If a currency has no book configured, invoicing is blocked rather than charging USD-sized numbers under a different currency code.

Because the same product costs a different fraction of payroll in Lagos, Bengaluru and New York. Capstan prices in tiers mapped to national purchasing power, and the commitment attached to that is that every book we set is published on this page rather than handed out as a private discount. Two are published today: the USD Tier 1 base, and the Indian book at 25 to the dollar. Twenty-five is a purchasing-power figure and not an exchange rate, which is the whole point of the exercise: at the market rate a dollar costs more than three times that, so the Indian book is an adjustment rather than a conversion. Books for the countries we have not set yet are not published, because they do not exist yet, and we would rather say so than show you a selector full of guesses. What you pay follows your billing country, verified at payment, not the country your browser appears to be in.

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 module entitlement holds a reference to the row that was in force on the day you enabled it, and your plan’s per-seat price is captured onto your subscription when the plan is granted. So a rise reaches new customers and new enablements 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. Once you are on a paid plan, enabling a module is one click and needs nobody’s approval. 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. Disabling a module stops its billing at the end of the current period rather than on the day, and moving off a paid plan cancels the term without paying back the remainder. 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.