What ClickMasters Technical Discovery Produces
Without a Technical Discovery, any software development cost estimate is a guess. With one, ClickMasters can give you a fixed price — and commit to it. This guide explains what the ClickMasters Technical Discovery covers and why it is the essential first step for any UK software project above £15,000.
| Deliverable | Description | How It Is Used |
|---|---|---|
| Product Specification | Detailed functional requirements — every user story, every screen, every workflow. UK GDPR considerations identified per feature. | The "what" — defines exactly what is in scope for the fixed-price build. Every requirement in the spec is a cost item. |
| UI Wireframes | Low-fidelity wireframes for key screens and user journeys. WCAG 2.1 AA considerations noted. | The visual reference — shows how the product will work before any code is written. Reduces misalignment. |
| Technical Architecture | Cloud architecture diagram, technology stack selection, database design, API design, integration architecture. | The "how" — defines the technical approach. Allows senior review before commitment. |
| Integration Map | Every third-party API: authentication method, key endpoints, data flow, compliance implications (UK GDPR, FCA, NHS). | Identifies hidden complexity — API integrations are frequently the largest source of cost surprises. |
| Compliance Assessment | UK GDPR, ICO, FCA, NHS DTAC, GDS — which standards apply, which requirements must be built from Sprint 1. | Prevents compliance retrofitting (expensive) — designs compliance in from the start. |
| Risk Register | Project risks identified, rated, and mitigated — technical, compliance, timeline, and dependency risks. | Honest assessment of where the project could go wrong — allows informed go/no-go decision. |
| Fixed-Price Proposal | Total delivery cost, payment milestones, sprint plan, team composition, and delivery timeline. | The commercial commitment — client signs on fixed price, not a range. |
Technical Discovery Process — Week by Week
| Week | Activity | ClickMasters Role | Client Time Required |
|---|---|---|---|
| Week 1, Days 1–2 | Requirements workshops | Facilitated sessions — user stories, workflows, priorities | 4–6 hours (stakeholders + technical lead) |
| Week 1, Days 3–5 | Architecture design + wireframing | CTO designs architecture, designer creates wireframes | Review session (2 hours) |
| Week 2, Days 1–2 | Integration research + compliance assessment | API research, regulatory review, DPIA scoping | Review integration map (1 hour) |
| Week 2, Days 3–4 | Specification writing + risk register | Full specification document written | Review draft spec (2–3 hours) |
| Week 2, Day 5 | Proposal presentation | Fixed-price proposal presented, questions answered | 1.5-hour proposal presentation |
Who Should Attend a Technical Discovery?
Product owner or founder: the person who knows what the product needs to do and why.
Technical lead (if you have one): existing technical context, constraints, and preferences.
End-user representative (if accessible): the person who will use the software — their workflow is what the spec must match.
The most effective Technical Discoveries involve the right people from the client side. Required:
Optional but valuable: compliance officer or legal counsel (for regulated projects — FCA, NHS, GDS).