Process Discovery + scoping

Two-week discovery before every project over on request.

Discovery is the part most agencies skip. We do it on every project. Two weeks, fixed price, documented scope and fixed-price implementation quote at the end.

Discovery output is yours to keep, whether or not you proceed

Most fixed-price project failures happen because the scope was guessed, not measured. Discovery is how we measure. Two weeks of structured work with the engineers who would do the project, ending in a scope document and a fixed-price quote you can take to procurement.

The six steps

What discovery actually does.

Each step has a defined deliverable and a defined timebox. The whole engagement runs two weeks calendar time, often less if your team is responsive.

01

Kickoff call

Sixty-minute call with the engineers who would do the work, not just sales. We map your goals, your existing infrastructure, your constraints, and your decision timeline. Notes go into the shared discovery doc the same day.

Engineers and stakeholders aligned by end of day one.

02

Stakeholder interviews

Up to four 30-minute interviews with stakeholders we identify in the kickoff. Engineering lead, product owner, marketing, support. Each interview surfaces requirements that did not come up in the kickoff.

No surprise requirements discovered mid-build.

03

Technical audit

For projects touching existing systems, we audit the codebase, hosting, integrations, and data model. Documented findings on what works, what is brittle, what blocks the proposed work.

Hidden technical debt visible before contract.

04

Scope document

Written scope covering the work in detail. Phases, deliverables, acceptance criteria, dependencies, assumptions, exclusions. Reviewed with you in a working session before finalization.

A scope your procurement team can audit.

05

Fixed-price quote

A single number for the implementation, with phases priced separately so you can sequence the work over multiple budgets if needed. Quote is valid for 30 days.

A price you can sign without surprises.

06

Decision

You decide whether to move forward with implementation. If you do, contract signs in the same week and implementation starts. If you do not, you keep the discovery output and we part on good terms.

No pressure, no fine print, no follow-on commitment.

What discovery costs

Discovery is a fixed-price engagement, typically on request depending on scope. Cost is credited toward implementation if you proceed. If you do not proceed, you keep the scope document and the audit findings.

What discovery delivers

A written scope document covering goals, phases, deliverables, acceptance criteria, dependencies, assumptions, and exclusions. A technical audit of existing systems if the project touches them. A fixed-price quote for implementation, with phases priced separately so you can sequence the work across multiple budgets if needed.

What discovery does not deliver

Discovery is not implementation. We do not write production code during discovery. We do not commit to design choices that should be part of implementation. We do not run user research that requires a separate research engagement.

Why two weeks

Two weeks is the smallest window that fits the kickoff, stakeholder interviews, technical audit, scope drafting, review session, and quote generation without compressing any of them. Faster discoveries miss requirements. Slower discoveries lose momentum.

Common questions

Frequently asked

  1. What does discovery cost?

    Discovery is a fixed-price two-week engagement. Cost varies by scope of the discovery, typically on request. Cost is credited toward implementation if you proceed.

  2. What if discovery uncovers a different project than we thought we needed?

    It happens. Discovery often reveals that the right project is different from the one you came in with. We document the finding and present the right scope, even if it is smaller, larger, or different from what you originally asked for. Your call on whether to proceed.

  3. Can we skip discovery?

    For projects above on request no. Discovery is how we both protect against the failure modes of fixed-price work. For smaller projects (audits, single-feature builds, retainer top-ups), discovery is rolled into the kickoff call.

  4. What if our team has already done a discovery internally?

    Great. We review your existing discovery in a kickoff call and either accept it as the scope basis (with no additional discovery cost) or identify the gaps that need to be closed. Most internal discoveries leave at least a few gaps that we surface.

Ready to start?

Discovery is the first step.

Tell us about your project. We schedule the kickoff call within two business days of contract sign.