A senior leader at a large Indian brand invites your team in for a “consultation.” You map their systems, sketch an architecture and share a roadmap. Three weeks later they thank you, and nothing is signed. The free work was real. The commitment was not.
The short answer: scale-ups that convert consultations into annual contracts stop selling hours and start selling a packaged implementation: a fixed discovery phase, a defined first deployment, and a subscription that begins on a stated date. The package gives the buyer a decision to make, not a favour to accept.
Here is the step-by-step structure that works.
Why do free consultations rarely turn into signed contracts?
Free advice has no deadline, no owner and no price, so it sits in the buyer’s inbox. Three patterns repeat:
- No commercial next step. The consultation ends with insights, not a proposal.
- Scope creep by default. Each meeting adds one more requirement because it costs the buyer nothing.
- No internal sponsor accountability. The executive who invited you has no budget line to defend.
How do you package a technical implementation into a sellable offer?
Phase 1: A paid discovery sprint
Replace open-ended consultation with a time-boxed sprint of two to four weeks. Define deliverables up front: a current-state assessment, an integration map, a prioritised use-case list and a costed implementation plan. Price it modestly and credit it against the annual contract if the buyer proceeds.
Phase 2: A defined first deployment
Scope one business unit, one workflow or one integration with measurable success criteria. Name the owner on the buyer’s side, the data you need and the date you go live.
Phase 3: The annual subscription
Make the annual term the natural continuation, not a separate negotiation. State the subscription start date, the user or usage tiers, the support level and the expansion path in the same document.
| Stage | Buyer gets | Commercial structure | Exit signal to convert |
|---|---|---|---|
| Discovery sprint | Assessment, architecture, costed plan | Fixed fee, credited later | Sponsor reviews plan with finance |
| First deployment | Live use case with agreed metrics | Implementation fee plus subscription start date | Success criteria met |
| Annual contract | Full platform, support, roadmap input | 12-month term, tiered expansion | Business case signed by budget owner |
How do you make the offer easy for a CXO to approve?
- Write a one-page business case in the buyer’s language: cost today, cost after, payback period.
- Show a fixed price and a fixed timeline, with named change-request rules.
- Let the sponsor choose between two packages, not one, so the decision becomes which, not whether.
- Attach the standard legal and security documents at the proposal stage so procurement can start in parallel.
- Agree a review date for the subscription decision before the sprint begins.
What implementation pitfalls should scale-ups avoid?
- Quoting open-ended time-and-material work that makes the buyer feel they are hiring an agency.
- Giving away integrations that the product team will then have to maintain.
- Skipping the finance conversation until the deal is already verbal.
- Failing to document what the free phase delivered, which weakens the case for charging next time.
Industry analysts such as Gartner and McKinsey regularly point out that enterprise software value is realised in adoption, not licence signature. Packaging implementation around adoption milestones aligns your contract with that reality.
Frequently Asked Questions
Should enterprise SaaS companies charge for discovery in India?
Yes, in most cases. A modest, credited discovery fee filters out casual enquiries and gives the buyer’s sponsor a budget item to defend. Where a free pilot is unavoidable, limit its scope and set a written conversion date.
How long should an implementation package take before the annual contract starts?
Most scale-ups aim for a discovery sprint of two to four weeks and a first deployment within one to three months. The right length depends on integration complexity, but the subscription start date should always be written down early.
How do I stop a consultation from turning into free custom work?
Define deliverables and a change-request process in writing, and tie extra work to a priced change order. Keep roadmap requests separate from implementation scope.
Conclusion
A free consultation earns attention; a packaged implementation earns a signature. Give the buyer a paid discovery sprint, a defined first deployment and an annual subscription with a stated start date, and the conversation moves from advice to approval. Treat every phase as a commercial step with an owner, a price and a date.
Next step: Building enterprise relationships in India? Connect with founders and CXOs who have done it at thebuildersclub.me.





