How we run engagements

Our process — four clear phases, written down on day one.

You always know what we are doing this week, what is blocking it, and what the next decision needs to be. Below is the same operating doc every Rankrix client receives in week one — not marketing copy.

Phase 01

Audit.

Free, scoped, and yours to keep whether you hire us or not.

  • Analytics, search console and ad-account read-only access
  • Codebase walkthrough (or audit, if no codebase exists)
  • Funnel mapping with leak-points marked
  • Three explicit recommendations, ranked by expected impact
  • 30-minute presentation, recorded and shared back

The audit is the first thing we sell to ourselves: if it isn’t useful on its own, the engagement won’t be either. We refuse audits we can’t deliver value on inside a week.

Duration: 5–7 business days. Cost: £0. Output: a written report plus a 30-minute call.

Phase 02

Plan.

A scoped roadmap with phased deliverables, one accountable lead, and a fixed price.

  • Milestone-based deliverables (no monthly bill-without-output)
  • Fixed price up to and including launch
  • Named accountable lead for the entire engagement
  • Weekly demo cadence with a shared agenda
  • Defined success metrics — what “done” actually means

We do not bill for a three-month “strategy phase” before anything ships. Plan is a one-week, fixed-fee step whose only output is the document the build phase runs from.

Duration: 1 week. Cost: Fixed fee (typically £[STAT]–£[STAT]). Output: a scoped roadmap and contract.

Phase 03

Build.

Weekly demos, staging URL from day three, production push when something is actually done.

  • Staging URL live by day three, updated daily
  • Friday demo call with shared agenda
  • Slack channel for async questions (no project-management theatre)
  • Performance budget enforced from commit one
  • Production push when a milestone is genuinely done, not on a fake date

Build is when most agencies disappear and reappear with a Figma file. We refuse to. The staging URL is the contract — if it doesn’t update, the bill doesn’t run.

Duration: Typically 6–10 weeks for a full website + marketing rebuild. Cost: per the Plan-phase contract. Output: production push, handoff doc, postmortem.

Phase 04

Operate.

Optional monthly retainer for ongoing marketing, performance and iteration. Cancellable any month, no minimum term.

  • Monthly performance report with the metrics that actually matter
  • Retainer scope agreed monthly, not annually
  • Cancellable any month with one month notice
  • Hand-off to your in-house team when you’re ready, not when we are
  • Documented runbooks so the work survives our departure

Operate exists only when it is the cheapest place for the next pound of growth. If your in-house team can do it, we tell you to do that instead.

Duration: Open-ended, cancellable monthly. Cost: retainer (typically £[STAT]–£[STAT]/mo). Output: the metrics you cared about, moving.

FAQ

Common questions.

The audit slot is usually within 5 business days of first contact. The build phase starts 1–2 weeks after the audit, depending on contract turnaround on your side.

No. The audit is free, the deliverable is yours to keep, and we do not require a signed engagement to receive it. We refuse audits we can’t deliver real value on.

Common. We assess what you have, recommend keep / refactor / replace per surface, and integrate where it makes sense rather than insisting on a clean slate.

Yes — a mutual NDA before the audit on request. We don’t publish case studies without explicit, written approval, and we anonymise on request.

You see it on the staging URL, on the Friday demo and in the postmortem. Slips are surfaced inside 24 hours of being known. We do not pad timelines to disguise risk.

Yes — many engagements are single-discipline. We will not upsell you into an integrated programme that doesn’t pay back inside 12 months.

Next step

Want this scoped against your business?
Book the audit. 30 minutes, free, no follow-up sequence.

We will show you the version of this process tailored to your stack and your constraints, then you decide whether to proceed.