You don't need a specification or a budget to start. A description of the process that's costing you time is enough for a useful first conversation.
What happens next
What happens after you write: We read it properly, then We reply in one business day, then A 30-minute call.
We read it properly
We reply in one business day
A 30-minute call
No proposal until we understand the process. Three steps, and you can stop after any of them.
01
We read it properly
A person reads your brief, not a routing rule. If it's outside what we do, we'll say so and point you somewhere better.
02
We reply in one business day
Usually with questions rather than a proposal — the first answer is rarely enough to scope anything honestly.
03
A 30-minute call
We walk through the process together. You'll leave with an opinion on it whether or not you work with us.
Tell us about your project
The more you tell us about how things work today, the more useful our first reply will be.
Brief received.
We'll read it properly and reply within one business day — usually with questions before proposals.
Questions we get before the first call
If yours isn't here, ask it in the form — the answer usually helps the next person too.
How do you price a project?
We scope after discovery, not before it. The first conversation is free, and a short discovery engagement produces a phased plan with effort and dependency per step — which is what a fixed price can then be quoted against. We would rather give you a number we can hold to than a number that moves once we understand the process.
How long does a typical engagement take?
A consulting and process-mapping engagement usually runs two to four weeks, depending on how many departments are in scope. Implementation work is phased, so something usable ships at each checkpoint rather than everything landing at the end. We will give you a realistic sequence before you commit to it.
We don't know what we need yet. Is that a problem?
No — it is the normal starting point, and "not sure yet" is a valid answer on our contact form. Most people arrive knowing something is slow or manual, not knowing which software fixes it. Describing the process that is costing you time is enough for a useful first conversation.
Do we have to use Zoho?
No. We configure Zoho where configuration is genuinely the right answer, and write custom software where it is not. Because we do both, we have no commercial reason to steer you toward the more expensive option. Sometimes the honest recommendation is a smaller change than you expected.
Do you work with businesses outside Karnataka?
Yes. Our teams are based in Dakshina Kannada and Bengaluru, and we work with businesses across India in your timezone and business hours. Discovery is often faster in person for the first session, but the rest of an engagement runs perfectly well remotely.
What happens after launch?
Go-live is when adoption problems actually appear, so support, tuning and iteration are part of the engagement rather than an upsell. You get the people who built the system, not an account manager relaying questions to someone else.
Can you work with the software we already have?
Usually, yes. We build integrations into the systems already running — Tally, payment gateways, logistics partners, government portals — and we would rather stabilise and extend an application you already own than insist on a rewrite.
How quickly will you reply?
Within one business day, and usually with questions rather than a proposal. A first brief is rarely enough to scope anything honestly, so the reply is normally an attempt to understand the process properly before anyone talks about cost.