Insight
Do not send a feature list copied from a SaaS homepage
A quote built from someone else’s menu is a guess. Send who captures the order, who checks stock, who collects payment.
Sumit Phule · · Updated
The short answer
Send the process. Do not send a list of dashboards, AI, mobile apps and integrations copied from a product you saw online. We cannot price a menu. We can price: who captures the work, who checks it, who records the next action.
The problem we see
Owners arrive with twenty features. Half are screens they saw in a demo. None describe what happens on Tuesday when a dispatch is late. The quote then becomes a negotiation over modules. Six months later the unused screens are still unused, and the notebook is still the system of record.
Technology consulting here means walking that process before anyone writes software. It is not a strategy workshop with a slide deck. Ashirvad Solar is an example of treating the working model as the specification — customer, installation and follow-up in one picture — rather than starting from a generic CRM template.
What we need on one page
- Who takes the first request, and where it lives today
- The five steps to “done”
- Who gets stuck, and what they do instead of the official step
- What you are willing to change, and what the floor will not change
If two departments disagree on what “completed” means, say so. That disagreement is the project. Hiding it in a feature list does not remove it.
What to do next
Write those four points in a short note and send them through Get Quote. If we cannot tell product from custom yet, the quote should say discovery first. That is cheaper than building the wrong first release.