Question 1

How do we start a project with you?

Accepted Answer

It starts with a short call, or a paid discovery engagement if the process is genuinely tangled. Discovery ends in a process map, a data audit and a fixed-cost estimate you keep. Only after you approve the scope does any build begin — nothing is committed on a verbal brief.

Question 2

How long before our CRM is live?

Accepted Answer

Four to six weeks for most builds, from the discovery workshop to a live system with your data migrated. You see a clickable prototype in week two and a working staging build every Friday after that. Complex multi-company or ERP-connected builds run longer, and we tell you during scoping rather than halfway through.

Question 3

What do you need from us to begin?

Accepted Answer

Time with the people who will actually use the system, access to how leads and data flow today, and a decision-maker who can sign off scope. The discovery workshop needs roughly forty-five minutes per role interviewed and a couple of hours of review — nobody needs to block a week.

Question 4

Can we change things once we see the prototype?

Accepted Answer

That is exactly what the prototype is for. You click through your actual screens before we build them, and feedback happens on real screens rather than slide decks. Changes within the agreed scope are part of the build; genuinely new modules are quoted before we build them.

Question 5

What if we need a feature no product has?

Accepted Answer

We build it. The module that matters most to a business is often the one off-the-shelf tools do not have — a token booking desk, a BOQ tracker, an 80G receipt engine. Those are built from scratch as first-class parts of your system, not squeezed into a custom field.

Question 6

Do we own the code?

Accepted Answer

Yes. Full source-code handover is part of every engagement, along with the schema, documentation and deployment guide. If you ever stop working with us, you keep the system and any competent team can maintain it.

Question 7

Can each role see only what it should?

Accepted Answer

Yes — access is role-based down to individual fields, not a single admin switch. Reception might see a customer's name and phone but not the deal value; finance sees the payment details but not the discount workflow. You define the matrix and it is enforced on screens, exports and the API alike.

Question 8

How do we add or remove users later?

Accepted Answer

From an admin screen your team controls — adding a user is a configuration, not a support ticket, and there is no per-seat licence, so growth does not add to a monthly bill. Roles and permissions are managed the same way.

Question 9

Which tools can it connect to?

Accepted Answer

WhatsApp Business API, Meta and Google lead ads, Razorpay and other gateways, Tally and ERP systems, Google Calendar, Zoom, Slack and more — over official APIs and webhooks rather than nightly exports. If a tool has an API or a database we can read, it almost certainly connects.

Question 10

Who fixes an integration if the other tool changes?

Accepted Answer

We do, under your support agreement. A third-party API change is not something you could have prevented, so connector maintenance is part of support rather than a separate charge — and syncs halt safely on a breaking change rather than writing bad data.

Question 11

Where is our data hosted?

Accepted Answer

By default in an Indian cloud region with encryption at rest and in transit, daily backups and monitoring. If your policy requires a specific region or on-premise deployment, the whole system runs on infrastructure you control. Data residency is decided with you at the start.

Question 12

Is there a record of who changed what?

Accepted Answer

Every change is written to an immutable audit log — the actor, the action, the before and after, and the time — kept next to the record. Exports, deletions and permission changes are logged too, so a question always has an answer.

Question 13

How does pricing work?

Accepted Answer

It is a one-time build you own, not a per-seat subscription. The number depends on scope — team size, modules, integrations and any custom work — and you get a fixed quote after discovery, not a range that grows. Third-party charges like WhatsApp fees are billed at actuals through your own accounts.

Question 14

What does support include after go-live?

Accepted Answer

A named engineer who knows your build, an agreed response time by severity, automatic escalation, monthly patching, tested backups and a monthly review. An initial period is included with every build — three months on Starter, six on Business, twelve on Enterprise — and continues as an annual agreement after that.

Question 15

What if we want to leave?

Accepted Answer

You keep everything — source code, database, documentation and infrastructure access, handed over in a working state, with a transition call for whoever takes over. There is no lock-in mechanism, because a support relationship that depends on one is not worth having.

Still stuck? Talk to a person.

On a live system? Support responds by severity

How can we help?