Scoping Sessions Guide
Scoping vs Discovery Call
- Discovery call: early qualification and high-level fit check.
- Scoping session: qualified opportunity with intent to define an executable pilot.
Use scoping only when mutual interest and sponsor access are present.
Who Should Be in the Room
- Smartflow: product lead and presales engineer.
- Bank: operations lead, IT/security representative, and executive sponsor where possible.
Session Type Matrix
| Session | Duration | Purpose | Primary output |
|---|---|---|---|
| Initial discovery | 2 hours | Understand bank context and qualify fit | Scoping report |
| Deep-dive ops | 2 hours | Map workflow, volumes, and exceptions | Requirements matrix |
| Pilot scoping workshop | 4 hours | Finalize pilot scope, success criteria, and plan | Pilot brief |
How to Capture Outputs
- Assign one facilitator and one note owner at start.
- Capture quantitative inputs (volume, cycle time, error rate) in-session.
- Record open questions with named owners before close.
- Publish draft output within 24 hours while context is fresh.
What Success Looks Like
A successful scoping sequence produces:
- One shared view of current workflow and pain points.
- A fit assessment with explicit strengths, gaps, and risks.
- A pilot recommendation with timeline, owners, and measurable success criteria.