“We spent money last time and nothing changed.”
Answer: the baseline is recorded before work starts, and the comparison is delivered at the end. If nothing changed, the record will say so.
Aroc BuildFix one thing properly.
Fix one thing properly.
Then prove it worked.
Build implements the highest-priority improvement your assessment identified — and ends by verifying it produced the outcome it was meant to. Not a redesign because a redesign was the thing on offer.
Why this is worth reading carefully
Everyone who has paid for a website before is right to be sceptical.
These are the four things people actually say when the subject of building comes up. Each is reasonable. Each is answered below by a commitment rather than by reassurance.
“We'll get something we can't edit or measure.”
Answer: analytics and Search Console are set up in accounts you own, and you leave with the domain, the content and the access.
“They'll disappear at launch.”
Answer: launch is where measurement begins. What happens next is a decision you make with evidence, not a retainer you are signed into.
“We won't be able to tell if it worked.”
Answer: contact tracking is installed and verified firing on launch day. If it isn't verified, the Build isn't finished.
Build exists to resist unnecessary work. If the diagnosis says one thing needs fixing, we fix one thing — not ten.
Where Build sits
Build is a step in a loop, not the destination.
Assess produces a roadmap. Build implements the first priority on it and measures the result. That measurement decides the second priority — and most second and third priorities are small enough to live inside Grow rather than needing a project at all.
- 01
Assess
- 02
Roadmap
- 03
Priority One
- 04
Measure
- 05
Priority Two
- 06
Measure
- 07
Continuous
Build should get smaller over time, and that is the point. A mature relationship has one Build and many measured improvements. A business that needs a new Build every year does not have a delivery problem — it has a diagnosis problem.
Two shapesMost engagements When the surface itself is the problem
Sized by the constraint, not by a page count.
Focused Build
from $5,000
One constraint, implemented properly. Standard structure, content you supply and we shape.
- Up to six pages
- Two rounds of design feedback
- The full launch standard
- Not necessarily a website — if the constraint is your profile, your listings and your contact path, that is the Build
System Build
Always quoted
The surface rebuilt around the constraint. New structure, new content, or something a focused build does not cover.
- Seven pages and beyond
- Copy written to brief
- Migration, booking integration, multi-language
- Quoted against the diagnosis — never assumed
Assess is credited in full against a Build started within 60 days. Do both and the diagnosis effectively cost nothing.
The launch standard
Ten things included in every Build, because without them nobody can prove it worked.
These are the items most commonly skipped in this industry — not out of malice, but because nobody checks and the client cannot tell. They are not upgrades here.
- 01A page per service, structured so a search engine can tell them apart
- 02Titles and descriptions written per page, not generated
- 03Accurate structured data
- 04Sitemap submitted and indexation verified after launch
- 05Analytics and Search Console, in accounts you own
- 06Contact tracking installed and verified firing on launch day
- 07A canonical record of your name, address, phone and website
- 08Mobile-first, tested on a real device
- 09A measurement baseline recorded before launch
- 10Handover: you own the domain, accounts and content
How it runs
Five stages, and what each one needs from you.
- 01
Define
Confirm the constraint, the surface, the content source, and how success will be measured.
Your partApprove the scope in writing.
- 02
Design
Structure and key screens, against the Aroc design system.
Your partTwo rounds of feedback.
- 03
Produce
Build, content, structured data, metadata, analytics, tracking.
Your partSupply content and access.
- 04
Validate
Mobile, speed, forms end to end, tracking verified, metadata, crawl.
Your partOne round of pre-launch feedback.
- 05
Launch
Cutover, sitemap, indexation confirmed, baseline recorded, handover.
Your partApprove go-live.
If content, access or approvals are delayed beyond ten working days we pause rather than compress. Compression is how quality is lost, and you would pay for it twice.
What Build proves✓ ✓ ✓ ✓
Every Build ends with a written record, not a handshake.
This is the difference between a project that finished and a project that worked. It is also what makes the next step obvious — or makes it obvious there isn’t one.
The agreed constraint was addressed
Stated against the original finding, in the same words.
Implementation completed
What was built — and what we deliberately did not build.
Baseline vs launch
The numbers as they stood before, and at go-live.
The next constraint identified
Which stage is now the earliest weak one.
And then we tell you the truth
Sometimes the honest answer is that you don’t need us next month.
At handover one of two things is true, and we say which. Either the next constraint is named and there is real work attached to it — or nothing needs monthly attention and you should keep your money.
Build has to be sellable without a retainer attached.If it isn’t, it is a subscription trap wearing a project’s clothes — and anyone who has been burned before can smell that from a distance.
Build the one thing that matters.
Every Build starts with an assessment, because the alternative is guessing expensively. The diagnosis is credited in full against the work.
Start with Assess · $950