Process
Engagement process
Every engagement follows the same explicit path: discovery and audit, a written scope with exclusions, milestone delivery on staging, launch with a rollback plan, then optional ongoing engineering. You always know what is done, what is next, and what it costs.
Discover
A short intake call or a written brief. I audit what exists — hosting, stack, plugins, data — before quoting anything. You learn what is load-bearing and what the honest options are, including when the answer is simpler than you think.
- Input
- Brief or intake call
- Output
- Audit + honest read
Scope & proposal
A written proposal with explicit deliverables, exclusions, milestones and price. No vague strategy line items — you can hold every line of it against the delivery that follows.
- Input
- Agreed goals + constraints
- Output
- Written proposal, fixed price
Build
Work happens on staging with version control, in milestones you review before anything touches production. You watch progress in the client portal, not in email threads.
- Input
- Signed proposal
- Output
- Reviewed milestones on staging
Deliver & support
Documented handover, deployment with a rollback plan, and optional ongoing engineering when you need a specialist on call.
- Input
- Approved staging build
- Output
- Launch + handover docs
Operating rules
The way the practice runs.
These are standing commitments, not aspirations — they apply to every engagement, project or retainer.
- Response
- < 1 business day
- Delivery
- Staging → production
- Reporting
- Client portal
- Emergency
- Triage within 24h
Next step
Start at stage 01 — tell me what is broken, slow or missing.
The intake takes a few minutes and every field has a purpose. You will get a substantive reply within one business day.
Response within one business day