Timeline & process
What actually happens, week by week.
No mystery, no "we'll be in touch in a month". Here's exactly how a Velocity X build runs — what happens each phase, and precisely what's expected from you.
-
Week 0
Brief & brand deep-dive
Before anything is designed, we get deep on your brand, your taste, the sites you love and hate, and exactly what the build needs to do. Everything downstream is built from this — nothing is guessed.
Your part: Share your brand, examples, and goals (a call + a short questionnaire).
-
Weeks 1–2
Design — 10+ approval rounds
You see real, working design and sign off as we go. A minimum of ten approval rounds means no "big reveal" surprises — the thing we build is the thing you already said yes to.
Your part: Review each round and give direct feedback. Use the rounds — they exist for it.
-
Weeks 2–4
Personalised development
Not a template drop. The site and operations are built around how your business actually runs — your services, workflows and edge cases — developed one-on-one, never offshored.
Your part: Answer the occasional detail question. Otherwise, this part is on me.
-
Week 4
Integrations & wiring
Bookings, CRM sync, lead routing, payments — the operations layer gets connected and tested against your real tools, not bolted on as a "phase two".
Your part: Grant access to the tools you want connected (CRM, calendar, etc.).
-
Launch week
Go live & onboarding
We launch with hands-on, expert support — no ticket queue. Staff are onboarded on the booking/operations dashboard, leadership on the admin panel, all by the person who built it.
Your part: Bring your team to a short onboarding session. Then you're live.
-
After launch
You own it — and iterate with AI
The repo is transferred to you. We train you and your team to keep iterating on your own codebase with AI. The whole stack is AI-readable, so your business is unlocked for rapid self-improvement.
Your part: Keep shipping — with us on hand, or on your own. Your call, your code.
Roughly 4–5 weeks, start to live.
Timelines flex with scope — but you'll always know what phase you're in and what's next. Tell me about your project and I'll map it to a real schedule.
Timeline & process — common questions
Roughly four to five weeks, though timelines flex with scope. Week 0 is the brand and brief deep-dive, weeks 1–2 are ten-plus rounds of design approval, weeks 2–4 are development, week 4 is integrations and wiring, and launch week is go-live and onboarding.
Reviewing each of the ten-plus approval rounds and giving direct feedback. The rounds exist to be used, not rushed past, and production development does not start until you have signed off on the design.
In week four, alongside development. Bookings, CRM sync, lead routing and payments are connected and tested against your real tools at that point, not bolted on afterward as a separate phase.
Bring your team to a short onboarding session — staff are trained on the booking and operations dashboard and leadership on the admin panel, by the person who built it.
Yes. That figure assumes a scope close to what was agreed at the brief; a larger scope, slow feedback on design rounds, or late access to the third-party tools you want integrated will extend it, which is why the exact schedule is mapped per project rather than fixed.