Operations 2026
Working together.
This is the page enterprise procurement asks for and small founders skim before booking the intro call. It tells you exactly what hiring me feels like, day by day, so there are no surprises.
The 48-hour kickoff.
Once the contract is signed, you get this in your inbox within 48 hours:
- One-page spec, refined. Your scope, rewritten the way I'll work from it. Reply with red-lines.
- A shared GitHub repo (yours, in your org or mine handed over on launch). First commit lands within the week.
- A Slack channel (your workspace) or a dedicated email thread. You pick the channel.
- A weekly Loom slot — 5-minute video Friday with the week's progress, blockers, and next-week plan. Replaces standups.
- A calendar invite for the live mid-project check-in (typically week 2 of a 4-week engagement).
A typical week.
- Monday. Plan the week's chunks. I publish a short Loom of "what I'm shipping this week" — you watch it on your commute.
- Tuesday–Thursday. Heads-down build time. Daily commits. PR descriptions in plain English. You can check in any time on the repo.
- Friday. Ship what's ready. Weekly Loom + written summary in Slack: "Shipped X, Y, Z. Blocked on (your decision). Next week: A, B."
- Weekend. I don't work weekends unless you have a launch deadline. If you do, you'll know in advance and it's billed at the same rate, not a premium.
Communication norms.
<24h
Response time on Slack / email. Usually same day during 10:00–18:00 BST.
0
Status meetings. You read the Friday Loom + summary instead.
- Async by default. Loom > meeting. Long-form > chat. I'll write a doc before I'll book a call.
- One channel per concern. Spec questions in PR comments. Blockers in Slack. Process / scope changes in email so we have a paper trail.
- I tell you when I'm stuck within 24 hours. No surprise blockers two weeks before launch.
- I'll push back. If you ask for something I think is a bad call, I'll say so. Then I'll build what you decide. Once.
What I use.
- Repo: GitHub (yours or mine).
- Async video: Loom (free tier is plenty).
- Issues / tickets: Whatever you already use — Linear, GitHub Issues, Jira, Trello. I'm not precious.
- Docs: Markdown in the repo. Notion or Google Docs if you require it.
- Design handoff: Figma, or just a screenshot — I can read both.
- Time tracking: Toggl on retainer engagements, with a weekly report in Slack.
Hand-off, when we're done.
- A README that's actually readable — by your next engineer, your designer, or your CEO.
- A 30-min handover call with whoever takes over. Recorded.
- 30 days of bug-fix support after launch, free. Bugs only — new features go to a retainer.
- Your repo, your domain, your hosting account, your invoices. Everything in your name. No vendor lock-in to me.
Ready to start?
A 15-minute call to see if I'm the right fit. Or send a one-line scope and I'll quote within 24h.