Helping customers decide sooner

The situation

At RootQuotient, a typical enterprise sale took approximately 3 months. Some prospects had a detailed brief; others arrived with a compelling idea and no requirements document. If we moved straight to a proposal, we could spend weeks comparing features and prices without agreeing on the business problem, the people who would use the product or the scale of the investment.

The decision I made

Before a call, I researched the business, its industry and the people joining. I wanted a useful starting hypothesis, not a performance of knowing their company better than they did. If they had no written requirements, I shared a simple format to help them describe users, workflows and priorities. I asked how many stakeholders and platforms were involved and what the first useful version needed to do. From there I prepared a wide, early investment range, then validated the assumptions with technical colleagues before putting it in front of the customer.

Why the range mattered

An indicative number was not a shortcut around discovery or a disguised fixed quote. It made a difficult question discussable. If the investment and the customer’s budget did not meet, we could reconsider scope, suggest an existing product, or stop before both sides spent weeks producing a proposal that could not work. If they did align, we could use the next meetings to examine the business decision and develop an appropriate solution with the technical team.

What changed

Typical cycles moved from approximately 3 months to 4-6 weeks. Qualified opportunities reached meaningful commercial discussions in as few as 4 meetings. We also identified solution-fit problems earlier. These are typical and best-case observations from this process, not a claim about every prospect or a controlled attribution study.

What stayed with me

Speed is not the goal in itself. A useful sales conversation leaves a customer more able to choose—even if the choice is not to buy from us.

The sale I didn’t make