# Statement of work: Fieldnote MVP

Prepared for Fieldnote

## Purpose

This statement of work (SOW) sets out what we will build for Fieldnote, how each part will be accepted, what it costs, and how changes are handled. It sits under the services agreement between us; if the two disagree, the agreement wins.

The goal: a web app where field teams record site visits with notes and photos, work offline on a phone, and share reports with their clients, live within **8 weeks** of kickoff.

## Deliverables

### Discovery and design

- Kickoff workshop and a written product brief
- Clickable wireframes for every screen
- A small design system (type, colour, components) in Figma

### Product

- Accounts: email sign-in, password reset, team invitations and roles (owner, member)
- Site visits: create, edit and archive visits with notes, photos and a location
- Offline drafts on mobile browsers, synced when the connection returns
- Search across visits by site, date and keyword
- Shareable visit reports (read-only link and PDF)

### Billing

- Stripe subscriptions with a 14-day trial, upgrades, cancellations and invoices

### Launch

- Admin dashboard: teams, usage and subscriptions
- Production deployment with monitoring and error alerts
- Handover documentation and a recorded walkthrough

## Acceptance criteria

Each milestone is accepted when its criteria are met on the staging site. You have **3 business days** to accept or list what's missing; silence after that counts as acceptance.

1. **Design approval:** wireframes cover every screen in the deliverables, and the design system is applied to three key screens.
2. **Staging sign-off:** every product and billing deliverable works on staging, on the latest Chrome, Safari and Firefox and on a phone, with test data you can try.
3. **Launch:** production is live on your domain, payments run in live mode, error alerts reach your inbox, and the handover documents are delivered.

## Estimate

Billed against the lines below. A 15% contingency covers the unknowns of a first version and is only invoiced if it's used.

| Task | Hours | Rate | Amount |
|---|---:|---:|---:|
| Kickoff workshop and product brief | 6 | $110.00 | $660.00 |
| Wireframes for every screen | 14 | $110.00 | $1,540.00 |
| Design system and key screens | 16 | $110.00 | $1,760.00 |
| Accounts, teams and roles | 18 | $110.00 | $1,980.00 |
| Site visits with notes and photos | 30 | $110.00 | $3,300.00 |
| Offline drafts and sync | 20 | $110.00 | $2,200.00 |
| Search | 10 | $110.00 | $1,100.00 |
| Shareable reports (link and PDF) | 14 | $110.00 | $1,540.00 |
| Stripe subscriptions and trial | 18 | $110.00 | $1,980.00 |
| Admin dashboard | 16 | $110.00 | $1,760.00 |
| Automated tests and accessibility pass | 16 | $110.00 | $1,760.00 |
| Production setup, monitoring and alerts | 8 | $110.00 | $880.00 |
| Handover documents and walkthrough | 6 | $110.00 | $660.00 |
| Subtotal | | | $21,120.00 |
| Contingency (15%) | | | $3,168.00 |
| **Total** | | | **$24,288.00** |

## Timeline

- Weeks 1–2: discovery and design, ending in design approval
- Weeks 3–6: build, with a staging demo every Friday
- Week 7: testing and acceptance
- Week 8: launch and handover

The dates assume the client dependencies below are met on time.

## Payment schedule

Invoices are due within 14 days. Work on the next milestone starts when the previous invoice is paid.

- Deposit (On signing): 30%, $7,286.40
- Design approval (End of week 2): 20%, $4,857.60
- Staging sign-off (End of week 7): 30%, $7,286.40
- Launch and handover (Week 8): 20%, $4,857.60

## Client dependencies and assumptions

- Access to your domain's DNS, a Stripe account and the app's email sender by the end of week 1
- Copy and example data for the demo screens by week 3
- One person who can approve each milestone, and feedback within 2 business days
- Hosting and third-party services (estimated at $40–80 a month at launch) are billed to your accounts
- Up to 20 test users during the build

## Out of scope

- Native iOS or Android apps (the web app works on phones; native apps can be quoted separately)
- Single sign-on (SAML/SSO) and custom roles beyond owner and member
- Moving data from an existing system
- Copywriting, illustration and marketing pages
- Support after the warranty period (available as a monthly retainer)

## Environments and handover

The code lives in a repository in **your** GitHub organisation from the first day. There are two environments: staging (for demos and acceptance) and production. After the final payment we hand over all credentials, remove our own access on request, and walk your team through the code, deployment and monitoring.

## Change control

Anything not listed above is a change. Send it in writing; within 2 business days you get its effect on cost and dates. Approved changes are added as a new version of this statement of work for you to approve, so there is always one current, signed scope.

## Ownership, warranty and terms

- **Ownership:** the code, designs and documents become yours on final payment. Open-source libraries keep their own licences.
- **Warranty:** for 30 days after launch, we fix defects against the acceptance criteria at no charge.
- **Late payment:** invoices unpaid 14 days after the due date pause the work.
- **Ending early:** either side can end this SOW with 10 days' notice. You pay for work done to that date plus 20% of the current milestone, and receive everything built so far.
- **Confidentiality:** we keep your business information private and use the project in our portfolio only with your permission.

## Approval

Approving this statement of work confirms the deliverables, acceptance criteria, price and terms above. Work starts on the first Monday after the deposit clears.
