Every line on our pricing page came from a decision we argued about internally, and most of those decisions cost us something. This is the reasoning behind the DexVee pricing model: per module, per user, with GST already in the sticker price and nothing that renews on its own. We've also tried to be straight about who it doesn't suit.
The short version
Here is what the model is today, as listed on the pricing page:
- Free Starter: CRM + Helpdesk for up to 5 users, free with no time limit and no credit card.
- Paid modules (Books, Inventory, FSM, HR, Projects, Bids, Marketing, plus CRM and Helpdesk beyond the Starter) are each priced per user, per month.
- Every price includes 18% GST. Checkout charges exactly the listed number.
- Every module has a 14-day free trial, with no card needed.
- Annual billing costs 10× the monthly price, so you get two months free.
- Nothing renews automatically. Each month or year is a one-time payment.
- Shared modules are free for everyone: Accounts & Contacts, Documents, Reports & Dashboards, and Users, Roles & Settings.
The rest of this post explains why each of those looks the way it does.
Why per module, not one bundle
Most of the businesses we build for don't run every department through the same depth of software. A services firm might live in CRM, Helpdesk and Books and never touch Inventory. A distributor might need Inventory and Books on day one and add Field Service a year later, if ever. A single bundle priced for everything asks all of them to pay for the parts they don't use. In practice it also pushes them towards the most expensive tier, because that is the only one with the one feature they need.
Pricing each module separately lets a business pay for what it actually runs, and grow into the rest when there's a reason to. It also keeps us honest: if a module isn't pulling its weight, customers can drop it without leaving the platform.
The free shared modules are what make this work. Accounts & Contacts, Documents, Reports & Dashboards and Users, Roles & Settings are the backbone every product hangs off, so they're free for everyone in the workspace. A customer record, its documents and the reporting on top of it are never behind a paywall, whichever modules you subscribe to. If they weren't, per-module pricing would just be a bundle sliced into pieces.
Why per user, per module
A user only needs a seat in the modules they work in. Someone who handles support tickets all day needs a Helpdesk seat. They don't need a CRM seat, and we don't think they should cost you one.
The alternative, charging per user for the whole platform, sounds simpler but penalises exactly the teams we want to serve. Field technicians, support staff and accounts teams each touch one or two modules heavily and the rest barely at all. Charging each of them for everything makes adding a person to the system a budget decision, and then people get left out of the system. In our experience that's how shared logins and spreadsheets on the side start.
The trade-off is real: someone has to think about who needs which seat. We've accepted that admin overhead because it's a one-time decision per person, and the free shared modules mean nobody is locked out of the basics while you decide.
Why GST is in the sticker price
A lot of business software is priced excluding GST, with the 18% added at checkout. The headline number looks smaller that way. We decided against it for three reasons.
The number on the page should be the number you pay. The rupee figure on each module card is what checkout charges, with nothing added at payment. The page also breaks out the taxable value and the GST portion for every module, so you can see both. At the time of writing, CRM is ₹799 per user per month: ₹677 taxable plus ₹122 GST. The pricing page is always the source of truth, because it reads live from the same plan records checkout uses.
Approvals go smoother. Many of the people buying from us have to get a figure signed off by someone else. When the approved amount and the charged amount differ by 18%, that gap has to be explained after the fact, and it reflects badly on the person who raised the request.
GST-registered buyers still get their input credit. Every payment generates a GST tax invoice automatically. Add your GSTIN in Settings › Subscriptions and the invoice carries it, so you can claim input tax credit just as you would on an ex-GST price.
What it cost us: next to a price shown excluding GST, ours looks 18% more expensive at a glance, even when it isn't. We'd rather lose that comparison than win it by leaving something out.
Why nothing auto-renews
This is the decision we argued about longest. Auto-renewal is good for a software company's revenue, mainly because it relies on inertia. Some customers keep paying for a module they stopped using months ago, because cancelling takes effort and remembering to cancel takes more.
We didn't want any of our revenue to depend on that. So every month or year on DexVee is a one-time payment. There is nothing to cancel. If you don't renew, the module pauses at the end of the period you paid for, and your data stays where it is. If you renew while a paid period is still running, the new period starts when the current one ends, so renewing early doesn't cost you days.
The trade-offs land on both sides. For us, revenue is less predictable and every renewal has to be earned. For you, somebody has to actually renew, and a missed renewal means a paused module until it's paid.
Why annual is 10× monthly
Annual billing costs ten times the monthly price, so a year paid upfront gets two months free. We kept the ratio simple so nobody needs a spreadsheet to work out the discount. Annual is a one-time payment too and doesn't roll over on its own. It's the right choice once you're confident a module is staying. Monthly is the right choice while you're still finding out.
Why the trial is per module, and the Starter is free for good
Every module has its own 14-day free trial with no card required. A trial covering the whole platform makes you evaluate everything at once, and in two weeks most teams can really test one or two modules. Per-module trials let you try Books this month and Field Service next quarter, each with its full two weeks. When a trial ends, the module pauses until you subscribe, and your data stays in place.
The free Starter (CRM + Helpdesk for up to 5 users) is free with no end date. It's meant for a small team to run real sales and support on, not as a demo with a timer on it. If a team on paid CRM or Helpdesk lets the subscription lapse, it falls back to the Starter rather than losing those modules.
Who this model suits
- Small and mid-sized teams that need a few modules now and want to add more later.
- Teams where different people do different jobs: sales in CRM, support in Helpdesk, accounts in Books, each needing a seat only where they work.
- Buyers who need an exact figure approved and want the invoice to match the quote to the rupee.
- Anyone who wants to decide on renewal themselves rather than discover it on a card statement.
Who it may not suit
We'd rather say this plainly than have you work it out three months in.
- Very large teams using most modules. Per-user, per-module pricing grows in a straight line with headcount. Past a certain size, a custom agreement usually makes more sense, and that's what our Enterprise plan is for. It's priced to your requirements and covers multi-organisation workspaces, custom integrations and dedicated onboarding.
- Groups running several companies on one platform. Multi-organisation workspaces are an Enterprise arrangement, not a self-serve option.
- Teams that want billing to run on autopilot. If your finance process depends on a subscription renewing without anyone touching it, our model asks for one deliberate step each period. Some teams find that a feature. Others find it a chore.
The principle underneath
Each of these choices answers one question: what would we want if we were buying? To pay only for what we use, see the real price up front, and never be charged for something we didn't choose to buy again.
For the full module list and current prices, see the pricing page. For questions about implementation, security and support, the FAQ covers the rest.