§ 05.00 — Engagement ledger

From intro call to handover, in seven steps. Published.

Most freelance horror stories are about steps 04 — 07. This page exists so you know exactly what they look like before you sign. No surprises is the entire product.

§ 05.01

Seven · Steps

Each step has its own deliverable
Step 01 / 07 · Introduction 15-minute call
Cost · $0 · a scheduled call · UTC+1

We talk about the problem, the timeline, and the budget. If we're not a fit, I say so on the call and recommend two other people. You leave with a written follow-up within 24 hours either way.

Step 02 / 07 · Discovery Audit Sprint · 7 days
Fixed price · $1,500 · non-refundable

I run a full audit against the live site and a written brief. You get a 32-page report and a 60-minute walk-through call. Roughly 40 % of clients stop here and use the report on their own. That is fine. That is also a feature.

Step 03 / 07 · Proposal & SOW 3 business days after audit
Written SOW · 14 days to sign

Written SOW with deliverables, milestones, exclusions, and a 40 / 40 / 20 payment schedule. You have 14 days to sign. No hard sell. No "valid for 48 hours" fakery.

Step 04 / 07 · Kickoff 90-minute call
Week 1 · staging access day 1

We confirm build calendar, communication channels, decision-makers, and the escalation path. Staging site is set up and access granted on day 1.

Step 05 / 07 · Build Weeks 2 — N
Written update every Friday · 17:00 UTC

You receive a written status email every Friday by 17:00 UTC. Loom walk-throughs when something is worth seeing. I cap concurrent projects at 3. If I miss a Friday update, the next milestone is free.

Step 06 / 07 · Handover 3 artifacts
Final week · contract reaches zero

You receive: (a) production codebase + repo access, (b) written runbook in plain English, (c) 60-minute admin training session recorded as Loom for your team.

Step 07 / 07 · Post-launch 30 days · included
Bug fixes only · scope frozen

30 days of bug fixes for anything I shipped, included. After that, the Care Plan retainer is available, or we close the engagement clean. Either way you keep everything.

§ 05.02

Working · Agreements

Non-negotiable · public
01CommunicationEmail + shared Slack (or Teams · your choice). No DMs across personal accounts.
02Friday updateEvery Friday by 17:00 UTC. Without exception. Past updates available on request.
03Response SLAOne business day on weekdays. No weekends. Out-of-office is announced 14 days in advance.
04ConcurrencyMax 3 active projects. Current count: 2 of 3. Updated weekly.
05SubcontractingNever without naming the subcontractor in the SOW, separately priced.
06Holidays 20264 weeks total. Dates posted in every SOW. No surprise OOO. Next: 11 — 25 Aug 2026.
07EmergencyA real outage on a site I built: response within 4 hours, 7 days a week. Defined in the runbook.
§ 05.03

What I refuse

Agreement-level

These come up. Every time. They are not negotiable. Listing them publicly saves us both a call.

  • ×I won't ship a launch the day before a major holiday.
  • ×I won't bypass accessibility for speed of launch.
  • ×I won't bill hourly under any circumstance.
  • ×I won't take projects that begin before the SOW is signed.
  • ×I won't store admin credentials in a shared Notion.
§ 05.04

Sample · Documents

Marketing without a contact form
PDF · 12 pp

SOW template

Anonymized. Used on every engagement. Includes payment, IP, scope, exclusions, milestones.

Download ↗
PDF · 32 pp

Audit report

From a real Audit Sprint, anonymized. P0 / P1 / P2 findings with fix estimates.

Download ↗
PDF · 1 pp

Friday update

One real week of one real project. Sets expectation for what every Friday looks like.

Download ↗

Step 01 starts here. 15 minutes. Zero cost.

Start a project