Playbook · Chapter 13
Service Discovery
Service discovery finds the services a client needs to make your SaaS work for them. Why it matters and what to cover.
The Service Discovery
Many clients need services before they can fully use a SaaS solution. Service Discovery finds out which ones. Done well, it gives you another reason to talk with the client. The client ends up more satisfied and gets more out of the product. The parts are below.
Why do we need it?
Service Discovery makes sure the solution fits the client's real needs and the way they operate. When you spot and plan extra services early, implementation and integration usually run smoothly. Clients are happier, and the partnership starts on solid ground. Planning ahead also sets clear expectations and avoids surprises during implementation. The client gets the full value from day one.
Purpose: Service Discovery finds the extra services, technical support or customisations a client needs to use a SaaS product well.
Scope: It is most common for complex solutions that need their own configuration or integration work. Run it for simpler SaaS offerings too, where it fits, so the client's needs are fully covered.
Key Activities
Integration Discussion: You talk with the client about how the SaaS solution connects to their existing systems, data flows and third-party services. That keeps operations running smoothly.
Configuration and Customization: You find the adjustments or custom features needed to fit the solution to the client's workflows and business needs.
Training Identification: You work out which training the client's team needs to use the solution well.
PreSales Perspective
Handover and Alignment: The presales team hands knowledge and context cleanly to the Professional Services department. That department delivers the extra services you identified.
Guidance on Service Requirements: You use what you learned in functional and technical discovery (opens in a new tab) to help the client understand which services they need. That can mean pointing out integrations, customisations or training that would raise the product's value for them.
Knowledge Support for Professional Services: You give the Professional Services team detailed insights, technical knowledge and the client's expectations. With that, they can document and prepare the implementation accurately. This includes documents like the Statement of Work (SOW). The SOW sets out the scope, timelines and expectations for the extra services.
From the blog
- Field play7 min read
Map the buying committee before the second meeting
One friendly champion is a single point of failure. Map the four functions that can veto a deal, name who sits in each and hold three relationships.
Read more - Field play6 min read
Ask about their process before you talk about your product
Open functional discovery with how the buyer works today, not with features. A 25-minute plan, the question order, exact phrasing and the warning signs.
Read more - 5 min read
The Power of Curiosity in PreSales: Why It’s Your Greatest Asset
Curiosity drives better discovery, stronger relationships, sharper demos and calmer objection handling. Why it is a core presales skill.
Read more
In the course
- Functional & Technical DiscoveryMembers only
- Functional & Technical Discovery Best PractisesMembers only
- The Discovery Summary / Opportunity Scoping Document (OSD)Members only