What I ask before I quote an SME systems rebuild

1. What is broken in the current flow, in one concrete path?

I do not need a wishlist. I need one path: enquiry comes in → who sees it → where it is logged → how the follow-up happens → what the customer gets next.

Walk me through a real lead from last week. Who replied first? Where did the phone number sit at 9pm? What happened when that person was on a site visit? If that path lives across a site form, a personal WhatsApp, an Excel sheet, and someone's memory, that is the rebuild. If the site is fine and only assignment is broken, that is a different job.

We wrote about the Excel-and-WhatsApp pattern in Stop running the pipeline in Excel and WhatsApp. The quote changes depending on which step is failing first. Continuity problems and design problems are not the same spend.

2. Who uses the system every day, and who decides when something is "done"?

A systems rebuild fails when the owner buys it and the team never opens it. I ask who will enter enquiries, who will update stages, and who can approve a change when the first version feels incomplete.

If sales owns the phone and accounts owns the sheet, phase one has to respect that split. If only the founder will use the new screen, we design for one power user, not a full team rollout. The answer here shapes logins, roles, training, and how much process change we should attempt in the first release.

I also ask who signs off on "this is good enough to live with." Without that name, phase one never ends. Every review meeting adds another field.

3. Where does the truth live today?

Screenshots beat adjectives. I want to see the live form, the inbox, the sheet columns, the labels in WhatsApp, and any tool you already pay for.

Sometimes the right move is a custom lead record that sits next to what you already have. Sometimes a packaged CRM is enough and a custom build is the wrong spend. We compared those paths in Custom CRM vs Zoho for Indian SMEs. I will not quote a "full custom CRM" until I know whether you need ownership of the workflow, or just better discipline inside a tool you already run.

Bring the messy version. The sheet with empty stage columns and the chat export with three people named "Sir" tell me more than a clean process diagram.

4. What is phase one, and what are we deliberately leaving out?

Every rebuild request arrives with "and also". And also GST invoices. And also a dealer portal. And also a mobile app. And also reports for the board.

I ask for a phase-one list that a team can ship and use. Typical shape for many SMEs: one enquiry capture path, one owner assignment, one follow-up trail, and a simple status view. Everything else goes on a later list with a date, not into the same fee.

If you want ballpark ranges for product-style builds in India, we covered that separately in SaaS MVP cost in India (2026). A website-plus-ops rebuild is not the same as an MVP, but the same rule applies: quote the first usable slice, not the dream architecture. Phase two is allowed. Phase two inside a phase-one fee is how trust breaks.

5. What must integrate on day one?

Integrations are where quiet cost hides. Email notifications, WhatsApp Business API, payment links, GST billing, accounting export, Google Ads lead forms, existing domain and hosting.

I ask which of these are mandatory for launch, and which can wait 30 days. "Connect everything" is not a scope. Two named connections with named owners is a scope. If WhatsApp must stay human for pricing and site visits, we automate acknowledgement and logging, not the negotiation.

Also tell me what you will not change: the domain, the email provider, the accountant's export format. Constraints shrink the quote in a good way. They stop us rebuilding systems that already work.

6. What does success look like in 90 days, in one sentence?

I am looking for something testable. Examples that work: "Any teammate can open today's open leads and see the last message without calling the person on leave." Or: "Every site enquiry gets an owner within working hours, with a logged first reply."

Vague goals like "look more premium" or "be more automated" do not help me price. A single operational sentence does. That sentence becomes the acceptance check for phase one. If we cannot agree on it in a call, we are not ready to quote a fixed fee.

What we refuse to quote until we know

We will not put a firm number on:

• "Make us a CRM" with no enquiry path and no users named
• A rebuild when we have never seen the current site, sheet, or chat flow
• Unlimited phase one that includes every future module
• Automation of pricing or negotiation before the human process is clear
• A fixed fee when the decision-maker is not in the room and cannot confirm scope

A soft range after a short call is fine. A fixed fee without the checks above is how projects go sideways for both sides. I would rather delay the quote by a week than invent certainty.