DISCOVERY PHASE STATEMENT OF WORK ================================= Disclaimer — not legal advice. This template is provided free of charge, as is and with no warranty of any kind, and using it creates no attorney-client relationship. It is jurisdiction-neutral: you are responsible for adapting it, for your own legal and tax compliance, and for having a qualified professional in your jurisdiction review it before you rely on it. Full terms: https://trycolo.co/terms-of-use SOW reference: [SOW-NUMBER] | Date: [DATE] Provider: [YOUR BUSINESS NAME] ("Provider") | Client: [CLIENT LEGAL NAME] ("Client") Governing agreement: [SERVICE CONTRACT / MSA AND DATE] Client sponsor: [NAME], [TITLE] — attends the readout and makes the go / no-go decision. 1. Purpose, fee and duration ---------------------------- The Client is considering [PROJECT, e.g. a customer portal replacing the current order-by-email process]. The scope cannot yet be priced reliably because [REASON, e.g. requirements differ between sales and operations, and the current system's integrations are undocumented]. This SOW covers a fixed-fee discovery phase only. It does not commit either party to the build. Field | Detail ----------------------- | ------------------------------------------ Fixed fee | [CURRENCY] [AMOUNT] Duration | [N] weeks, from [START DATE] to [END DATE] Readout meeting | [DATE], [60-90] minutes Build estimate validity | [30] days from readout 2. Questions discovery will answer ---------------------------------- 1. [e.g. Which user groups need access, and what can each do?] 2. [e.g. Which existing systems must the new tool connect to, and how?] 3. [e.g. What is the smallest first release that solves the core problem?] 4. [e.g. What data must be migrated, and in what state is it?] 5. [e.g. What are the main technical and business risks?] 3. Activities ------------- Activity | Included | Notes ------------------------------ | ----------------------------------------- | ----------------------------------------------------------- Kickoff call | 1 x [60] min | Confirm goals, stakeholders, access Stakeholder interviews | Up to [6] x [45] min | Scheduled by the Client within the first [10] business days Scoping workshop | [1] x half-day ([3-4] hrs) | Remote or on site at [LOCATION] Current system / site audit | Up to [N] systems | [SYSTEM NAMES] Competitor or reference review | Up to [N] products | [NOTES] User research (optional) | [ ] Not included [ ] [N] user interviews | [NOTES] Readout meeting | 1 x [90] min | Section 6 Additional sessions are quoted at [CURRENCY] [RATE] per session or hour. 4. Deliverables --------------- # | Deliverable | Description | Format -- | --------------------- | ------------------------------------------------------------------------------------------------- | ------------- D1 | Requirements document | Goals, user groups, prioritized feature list (must / should / could), non-functional requirements | [PDF / DOC] D2 | Scope map | [Sitemap / user flows / system diagram] for the recommended first release | [FORMAT] D3 | Technical notes | Recommended stack, integrations, data migration approach, hosting | [FORMAT] D4 | Risks and assumptions | Top [N] risks with mitigation and the assumptions behind the estimate | Section of D1 D5 | Priced build estimate | Cost and timeline per feature group, with a recommended first release and optional later phases | [PDF] D6 | Readout presentation | Summary of findings and options | [DECK] Low-fidelity sketches or wireframes may be produced to clarify scope. High-fidelity design and code are not part of discovery. 5. Client inputs and access --------------------------- Input | Due --------------------------------------------------------- | ------ List of stakeholders with roles and availability | [DATE] Existing documents (briefs, specs, process maps, reports) | [DATE] Read access to [SYSTEMS / ANALYTICS / CMS] | [DATE] Sample data or exports for migration review | [DATE] A named decision-maker at the readout | [DATE] If interviews or access are delayed by more than [5] business days, the end date moves accordingly. If delays exceed [15] business days, the Provider may invoice the remaining fee and deliver findings based on information received. 6. Decision gate ---------------- At the readout the Provider presents D1 to D6. Within [10] business days the Client chooses one of: - [ ] Proceed with the build as estimated, under a new SOW. - [ ] Proceed with a reduced first release, re-estimated within [5] business days. - [ ] Stop. No further obligation beyond payment of this SOW. 7. Ownership and fee credit --------------------------- 7.1 On payment in full, the Client owns deliverables D1 to D6 and may use them with any provider, including to request quotes from others. 7.2 The Provider keeps its general methods, templates and know-how. 7.3 Fee credit: [ ] None [ ] [100]% / [50]% of the discovery fee is credited against the build if the Client signs a build SOW with the Provider within [45] days of the readout. The credit expires after that date. 8. Payment ---------- Payment | Amount | Trigger | Due ----------------------- | ------------------- | ----------------- | -------------- [Full fee / first half] | [CURRENCY] [AMOUNT] | SOW signed | Before kickoff [Second half, if split] | [CURRENCY] [AMOUNT] | Readout delivered | Net [N] Expenses (travel for on-site workshop, research incentives): [NONE / AT COST, PRE-APPROVED]. Late payment terms follow the governing agreement. 9. Acceptance ------------- Provider | Client ------------------------------- | ------------------------------- Signature: ____________________ | Signature: ____________________ Name: [NAME] | Name: [NAME], [TITLE] Date: [DATE] | Date: [DATE] ------------------------------------------------------------ How to use this template 1. Write section 2 from the questions you could not answer on the sales call; they justify the fee. 2. Book the readout date before discovery starts. 3. Price D5 per feature group so the client can choose a smaller first release. 4. If you offer a fee credit, give the exact expiry date in section 7. Template provided by Colo (trycolo.co). Not legal advice — review with a qualified professional in your jurisdiction.