§ 00 — HOW I WORK

Five rooms. I leave the doors open.

Same five steps for web and community work.

01
§ 01Figure out what's actually broken

Diagnostic

Two weeks. I look at what you have — site, server, tools, data. I write up what's working, what isn't, and what I'd build next.

Outcome: You get a plan you can give to anyone — me, a hire, or nobody.

Sold on its own, this step is what /web-solutions calls the Audit tier.

02
§ 02Agree on the shape before I touch it

Blueprint

One document. Scope, deliverables, timeline, price. Signed off before the first commit. No surprise line items later.

Outcome: You know exactly what you're paying for and when it arrives.
03
§ 03I work in staging. You watch in public

Build

I work in staging. You watch in public. Weekly demos, screen recordings, live links. Nothing goes live without you pressing the button.

Outcome: No "big reveal." No launch-day surprises. You've already seen it.
04
§ 04We go live, and I stick around

Launch

Deploy. Write the docs. Train whoever runs it after me. 30 days of post-launch support — bugs, questions, tweaks — included.

Outcome: The thing works, and the people who need to use it know how.
05
§ 05I keep running it, or I hand it off clean

Operate

Month-to-month retainer, or a clean handoff. Both are real options. The right one depends on who's doing the work in month three.

Outcome: No vendor lock-in. You stay in control of the decision, always.

§ 06 — START

Fifteen minutes. I'll tell you honestly if I can help. If I can't, I'll tell you who might.

Fifteen minutes. I'll tell you honestly if I can help. If I can't, I'll tell you who might.

NOW BOOKING · TAKING ONE AT A TIME