Purpose
Discovery starts at the first customer interaction and turns early project context into a clear starting point for Design.
- Discovery is what Pigment already knows before the ink is dry.
- Onboarding is what the customer prepares before Design should start.
Together they answer: Why is the customer implementing Pigment? What was learned during Sales, Presales, scoping, and prototype work? What assumptions, risks, constraints, and open questions need to carry forward? Who owns business, data, technical, and decision-making responsibilities? What needs to be ready before Design? How will agent-assisted delivery be governed?
Use the Stencil agent
Ask the Stencil agent to turn everything Sales, Presales and PS scoping already know, plus what the customer may have provided already and still may need to prepare, into one clear starting point for Design. See the Stencil Agent Guide for an example prompt for this stage.
Key activities, ownership, and customer actions
| Activity | Owner | Purpose | Customer action |
| Capture and review pre-signature context | Sales / Presales / PS Scoping / Project Lead | Preserve goals, scope assumptions, prototype learnings, risks and open questions | Confirm business goals and success criteria |
| Complete Sales-to-Services Handover | Sales / Presales / Project Lead | Transfer context into delivery | |
| Confirm Implementation Readiness | Project Lead / Customer Project Owner | Align roles, prep tasks, training needs, data readiness and Design inputs | Identify business, data, technical and decision-making owners |
| Review SOW, scope, and assumptions | Project Lead / Solution Architect | Confirm what is in scope, out of scope, assumed or unresolved | Review Sales, Presales, scoping and prototype context |
| Confirm compliance requirements | Project Lead / Solution Architect / Customer Owner | Identify any regulatory, contractual or data-handling requirements that affect delivery | Review compliance and expectations where relevant |
| Set up project governance and tooling | Project Lead | Establish weekly PM syncs, status process, RAID log, communication channels and Pigment PM app where applicable | |
| Prepare for Design | Solution Architect / Customer Business Leads | Gather process flows, requirements, data extracts, access needs and open questions | Prepare process, data, access and training inputs for Design; participate in Implementation Readiness and kick-off |
Required outputs and definition of done
| Required output | Done when |
| Sales-to-Services Handover | Delivery team understands goals, scope assumptions, risks, compliance considerations and open questions |
| Customer context summary | Goals, success criteria, business pain, assumptions and known risks are documented |
| Prototype input summary | Prototype learnings are documented and positioned as input, not production, if applicable |
| Implementation Readiness outputs | Roles, preparation tasks, decision owners, data needs and Design inputs are confirmed |
| Compliance notes | Relevant regulatory, contractual or data-handling requirements are documented |
| Project governance setup | Weekly PM cadence, communication channels, status process, RAID log and Pigment PM app are established where applicable |
| Open questions for Design | Open questions are documented and ready to carry into Design |
Recommended practices
- Treat Discovery + Onboarding as the bridge from sales context to delivery execution.
- Set clear expectations that the prototype is an input, not the production solution.
- Confirm Implementation Readiness before Design begins.
- Make assumptions and open questions visible.
- Set up weekly PM activities and RAID tracking from the start.