Product Discovery · Engagement Proposal · SwissDnaCode
A structured five-workshop engagement to define, validate, and document your product — fully ready for development.
Structure overview
Each workshop has a focused theme, contains a series of meetings, and closes with a deliverable you approve before the next begins. Nothing moves forward without your sign-off.
Understand you, your vision, your business, and the goals this product needs to achieve. We ground everything in what you actually know and care about.
Define who you are building for, what problems they face, what the product needs to do, and where the boundaries of the first version lie.
Define what the AI does, what it refuses, how it uses your data, and what guardrails apply — before any technical decisions are made.
Define the RAG data pipeline, chunking strategy, context model, compliance constraints, and AI behaviour rules — before infrastructure decisions are made.
Design the user experience, complete the technical plan, and produce the full documentation package your development team needs to start building.
In detail
The first workshop is about building a shared foundation. We establish the working relationship, explore your vision in depth, and map out the business context your product will operate in. Your existing prototype is used as an active reference throughout.
Meeting 01
Meeting 02
Deliverable
Sign-off gate
You receive and review the deliverable. Once you confirm alignment on goals and context, Workshop 2 is scheduled.
Unlocks Workshop 2Workshop 2 goes below the surface. We identify your target users, understand the problems they face, explore the features that will solve them, and define the boundaries of the first version.
Meeting 03
Meeting 04
Deliverable
Sign-off gate
You validate the personas, feature list, and scope definition. Confirmed alignment ensures Workshop 3 builds on solid ground.
Unlocks Workshop 3With users, problems, and scope confirmed, Workshop 3 defines the AI layer before any technical decisions are made. We establish what the AI does, what it refuses, how it uses your data, and what guardrails protect the user — producing a complete AI requirements document that directly informs the architecture.
Meeting 05
Meeting 06
Deliverable
Sign-off gate
You confirm the AI requirements, guardrails, and compliance constraints are complete. This document becomes the blueprint for the technical architecture in Workshop 4.
Unlocks Workshop 4With the AI requirements confirmed, Workshop 4 maps the full data and technical layer. We define what the AI actually sees per query, how documents are ingested and structured, and what compliance and behavioural constraints apply — producing an architecture-ready specification before any infrastructure decisions are made.
Meeting 07
Meeting 08
Deliverable
Sign-off gate
You confirm the data architecture and AI compliance requirements are complete. Combined with the AI requirements from Workshop 3, this forms the full specification your team needs to begin the technical build in Workshop 5.
Unlocks Workshop 5The final workshop brings everything together. We design the product experience, translate the full discovery into a development plan, and close with a live presentation of the complete package — everything needed to move confidently into development.
Meeting 09
Meeting 10
Meeting 11 · Final
Final deliverable package
Final sign-off
The full package is presented live in Meeting 11. Your approval closes the engagement. You leave with everything needed to begin development.
Engagement closedHow we work
01
Each meeting has a defined agenda, but the format is collaborative. You will never be handed a form to fill in — we have real conversations and we synthesise the outputs into structured documents.
02
The prototype you have already built is valuable. We use it in Meetings 1, 4, and 6 as a concrete reference point. It surfaces assumptions early and keeps discussions grounded in something tangible.
03
You receive a structured document at the close of each workshop. This gives you time to review, share internally, and come to the next workshop with informed input — not just first reactions.
04
Nothing advances until you approve the deliverable. This protects against scope drift, ensures every phase builds on confirmed understanding, and gives you a clear moment of ownership at each stage.
What you walk away with
Goals, users, problem framing, and solution summary — your single source of truth.
2–4 validated personas with goals, pain points, and jobs-to-be-done.
Prioritised feature list with MoSCoW mapping and acceptance criteria for priority items.
Key screens and user flows, validated against your users' needs and your business goals.
Architecture approach, integrations, infrastructure requirements, and identified risks.
Phased milestones, effort estimates by feature cluster, and team composition guidance.