Process
How we work
The full version of the four steps — what happens when, in which tool, and what you can hold us to. Burned buyers trust process more than promises, so here it is in writing.
The four steps, in detail
01
Send your project
Use the form — rough scope, links, a Loom, whatever you have. Messy is fine.
- Scoped reply within 24 hours, every working day — written by the person who’ll do the work
- The reply is a real read on your project: what we understood, what we’d ask, what it roughly takes
- If it’s outside what we do well, we say so and point you somewhere good
02
Scope & agree
Nothing starts on a handshake. Everything that matters goes in writing first.
- Fixed retainer or fixed quote — no hourly meters, no creeping invoices
- What’s in, what’s out, and how revisions work — agreed before work starts
- Onboarding within 48 hours of agreement: access, tools, first tasks scheduled
03
Build with visibility
You should never have to ask “is anything happening?” That question is our failure condition.
- Your PM tool or ours — Asana, Slack, GitHub, or plain email
- Weekly written updates minimum: done, next, blocked
- Same-day responses on working days, with a live US-morning overlap window
04
Ship & stay
Launch isn’t the end of the engagement — it’s the start of the part where most vendors disappear.
- Structured handover: access, documentation, anything your team needs to own it
- Maintenance and iteration on the same retainer, with the same person
- Next month, you work with the same person again. That’s the point.
When something slips
Sometimes an estimate is wrong — anyone who claims otherwise is selling. When that happens, you hear it from us first, in writing, with a revised date and what changed. Proactive flagging is the rule: you should never discover a delay by noticing silence.
How revisions work
Revision rounds are agreed at scoping, so “one more tweak” has a shared definition. Inside scope, revisions just happen. Outside scope, you get a written note and a number before any extra work starts — never a surprise line item after.
Tooling
Asana or Trello for tasks, Slack or email for conversation, GitHub for code, staging links for review. Yours by default; ours if you’d rather not host the process. Either way, everything important ends up written down where you can find it.
See it for yourself.
The first 24 hours are a working sample of the process — send a project and judge the reply.
Prefer to talk? Book a discovery call.