Seven steps. One of them exists to reject us.
Pick and scope
Choose from the menu. The price on the card is the final price. The order form asks four questions about your site, then takes your card. About 60 seconds. No call required, ever.
Production starts on payment
Because you scoped it at checkout, nothing waits on an email. The form asks only for what production actually needs, never a 40-field onboarding questionnaire. Audits usually need nothing but your URL.
Production
A senior specialist runs the task on our evidence-first system: every claim in your deliverable traces back to something we measured, crawled or captured. If we could not measure something, the report says so instead of guessing.
The QA gate
Before you ever see a draft, an internal reviewer whose only job is to find reasons to reject it goes through every number, every recommendation and every sentence.
Your review
The deliverable lands in your dashboard. Approve it, or request changes. Up to three revision rounds are included on everything.
Delivery
You get the final branded deliverable: scored, prioritized, and written so your developer or writer can act on it Monday morning without a translation meeting.
What comes next
If the work surfaced an obvious next step, we name it and its price. If it did not, we say that too. No pipeline of manufactured urgency.
About that fourth step
The reviewer is paid to say no
Most agency QA is a colleague skimming a PDF before lunch. Ours is structural: the reviewer recomputes the scores from the raw evidence, re-checks claims against the live site, and fails anything that does not reproduce. A false pass costs us a client. A false fail costs us an hour. We bias accordingly.
When a deliverable does not pass, you never know. It goes back to production and you simply receive the version that survived.
Where the humans and the machines are
We are open about this because pretending is a losing strategy: software does the collecting, crawling and measuring, and accelerates drafting. Senior humans own scope, judgment, review and everything you read. You are paying for the judgment and the gate, and the gate is the part most of the industry skips.
The seven states of an order
Every order moves through the same visible sequence: received, scoping, production, QA review, your review, approved, delivered. Received confirms payment and creates your order room. Scoping is where we pull live evidence from your site and confirm the brief, and it is where we come back to you if anything is ambiguous, once, in writing, not as a meeting. Production is the senior specialist doing the work. QA review is our adversarial reviewer trying to reject it. Your review is the step most agencies skip: nothing counts as done until you say so. Approved triggers the final deliverable and working files. Delivered means it is in your order room permanently, with everything downloadable.
Revisions, plainly
Up to three revision rounds are included in every task. A revision means you give direction and we redo the work to match it, not a polite pass over typos. Most orders never need one, because the QA gate exists to catch weak work before you see it, but the rounds are there and the number is public because "unlimited revisions" always turns out to mean "until we get tired".
Common questions
How fast does an order actually start?
Scoping begins within one business day of payment. If we need something from you, access, confirmation of the target, a missing detail, you hear about it in that first day, not in week two.
Do I need a call to buy or approve?
No. The entire lifecycle runs without a meeting: brief in writing, progress in your dashboard, deliverable in your order room. If you work inside an AI assistant, our MCP server exposes the same menu and order status there. Calls exist on request, because sometimes talking is faster, but they are never a gate.
What arrives at delivery?
The report itself, visual and readable, plus working files: spreadsheets, specs and checklists your team can execute without interpretation. If a deliverable needs a meeting to be understood, we consider it failed.
See it from the other side
Pick a task, and watch this pipeline run on your own site.