Across our site you’ll keep meeting one example: a five-module operations suite — HRMS, facility management, visitor management, inventory management, workplace management — built in 8 days, live within a month, for about ₹80,000 one-time, then a per-active-user licence.

Numbers that specific invite two suspicions: it’s marketing fiction, or corners get cut. This post answers both by dissecting the build, day by day and rupee by rupee.

Where the eight days go

Day 0 (before the clock starts): discovery. A focused session — the modules, the workflows inside each, the user roles, the integrations, the deployment choice. Output: a written plan with scope, timeline and price.

Days 1–2: structure. Your organisation modeled in the base product — departments, locations, shifts, roles, permissions. The five modules instantiated with your terminology and fields. Because login, dashboards, notifications, mobile shell and reporting already exist in the base product, day one starts at what would be month three of a blank-page project.

Days 3–6: workflows. The real customisation: your leave policies and approval chains in HRMS; your complaint categories and escalation rules in facility; your gate process in visitor; your item categories, stores and reorder levels in inventory; your rooms and booking rules in workplace. AI accelerates the assembly; engineers make the judgment calls and review everything.

Days 7–8: integration and hardening. Biometric device connected and tested with real punches. Reports verified against sample data. Edge cases — the night shift crossing midnight, the contractor who works at two sites — exercised deliberately.

Then the build hands over to the go-live phase — data migration, pilot users, training, cutover — which is why built in 8 days becomes live within a month. (We’ve written a separate playbook on those 30 days.)

Where the ₹80,000 goes

The fee prices only the genuinely custom work — the workflow shaping in days 3–6 and the specifics of your integrations. What you’re not paying for is the point:

• Not the base product — amortised across every client who runs on it.
• Not bench time, sales overhead or office rent recovered through your project.
• Not padded estimates protecting the vendor from their own process.
• Not documented integrations — free by rule when the other side is documented, viable and credentialed.

A traditional house quoting ₹6–12 lakh for the same scope isn’t necessarily dishonest — their process genuinely costs that. That’s the difference between pricing a process and pricing an outcome.

Where the catch isn’t — and where the limits are

No, the licence isn’t where the money sneaks back: it’s a modest per-active-user monthly fee covering hosting, servers, updates and SLA support — with no separate AMC. And it’s active users, so a 200-person company where 35 people use the system pays for 35.

The honest limits: eight days holds for a focused five-or-six module suite on managed cloud. Heavy bespoke logic, undocumented legacy integrations, or ten-plus modules move the estimate — and we say so in the written plan, before you commit, not in an invoice after. On-premise deployments carry the full development cost, stated upfront.

The offer behind the anatomy

The reason we publish the anatomy is the same reason we publish the price: a customer who can see where the days and rupees go doesn’t have to trust adjectives. Fairness that can’t be inspected is just branding.

Your five modules might be a different five. The anatomy holds. Tell us your list and we’ll return a plan with your numbers in it — in days, not weeks: [email protected] · +91 95000 93600.