Client Discovery
Capture what the client needs before you propose, so the engagement starts on solid footing.
#Purpose
Understand the client's goals and requirements and record them where the team can see them.
#Business goal
Proposals and projects that match what the client actually wants.
#At a glance
| Detail | Value |
|---|---|
| Estimated time | 1–2 hours |
| Departments involved | Sales |
| Business modules used | CRM |
| AI departments used | Sales Agent (assists follow-up) |
| Required permissions | Internal staff with CRM access |
| Prerequisites | A lead or prospective client record. |
#Workflow at a glance
1
Meet the client
Discuss goals.
2
Record requirements
Log to the record.
3
Confirm scope
Align expectations.
4
Ready to propose
Move to proposal.
#Step by step
1
Meet the client
Discuss their goals, audience, and requirements for the site.
2
Record what you learn
Log the requirements and interactions on the lead or client record.
3
Confirm the scope
Align on what is in and out before proposing.
4
Move to a proposal
Proceed to the website proposal.
#Approval points
No formal approval gate
This workflow does not require a sign-off step, but you can still review before acting.
#Expected result
What you should see
The client's requirements are captured and you are ready to propose.
#Common mistakes
- Proposing before understanding the real scope.
- Keeping discovery notes outside the CRM.
#Troubleshooting
| If this happens | Try this |
|---|---|
| Requirements are unclear later | Log discovery notes on the record so nothing is lost. |
#FAQ
Is there a dedicated discovery form?
Discovery is captured as activity and details on the CRM record; there is no separate builder.
#Keep exploring
#Related workflows
#Knowledge base
#Business modules
CRM Module
Client records.
Getting Started
Set up your workspace.
Platform Overview
How the OS fits together.
#AI departments
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?