No mystery weeks, no radio silence
The worst part of hiring an agency is the middle — you sign, you pay, and then nothing visible happens for a month. Our fix is boring and it works: a preview URL from day one, and a named stage you can always point at.
Typical build
Six to ten weeks, start to launch
Your time
Six to eight hours across the whole project
After launch
Thirty days of fixes, included
Stage by stage
What happens, in order
Each stage ends with something you can look at and sign off. Nothing moves forward on a verbal maybe.
- 01
Call and scope
Forty-five minutes on what the site needs to do and what's currently stopping it. We come out of it with either a written scope or an honest no.
- Who buys from you, and what they need to know before they will
- What the current site does badly, with analytics if you have them
- Hard constraints: launch date, budget ceiling, systems we have to talk to
- Whether we're the right studio for it — sometimes we're not
- 02
Structure and copy
Sitemap, page-by-page outline, and the first draft of the words. This is the stage that decides whether the site works, and it happens before anyone opens a design tool.
- Sitemap with URL structure locked, so nothing needs redirecting later
- Keyword and intent mapping per page
- Copy drafted in a shared doc where you can comment line by line
- Wireframes at two breakpoints once the copy is roughly settled
- 03
Design
Two directions for the key page, then one gets developed out across every template. Real copy, real image ratios, mobile and desktop together.
- Type scale, colour system, and component states defined once
- Every template designed, not just the homepage
- Mobile designed alongside desktop rather than squashed afterwards
- One round of revisions per template is built into the price
- 04
Build
Front end, CMS, integrations, and the performance budget enforced as we go. You get a preview URL from day one and it updates on every commit.
- Preview deploy per branch, so you review real pages not screenshots
- Accessibility checked as components are built — contrast, focus, keyboard order
- Page-weight and LCP budgets fail the build if broken
- CMS modelled so your team can edit without breaking layouts
- 05
Test and launch
Cross-browser and cross-device passes, redirect map, analytics verification, then the DNS switch — usually on a Tuesday morning, never on a Friday.
- Redirect map for every old URL, tested before the switch
- Real-device testing on iOS and Android, not just emulators
- Analytics and conversion events verified firing, with the numbers to prove it
- Search Console, sitemap submission, and indexing checked the same week
- 06
Thirty days, then your call
A month of included fixes and a written handover. After that you either run it yourself or we stay on maintenance — both are fine.
- Anything broken in the first thirty days is fixed free
- Loom walkthrough of the CMS, plus a written doc
- Full credential and repository handover
- Optional retainer for updates, monitoring, and content
Week by week, and what we need from you
This is the marketing-site shape. A landing page compresses to three weeks; a store stretches to sixteen. The rhythm stays the same.
Add three to five weeks at the front for us to have a slot free. We run two builds at a time and don't take a deposit for a start date we can't hold. Ask what's free.
What makes a project late, and what makes it early
Almost none of it is build speed. It's decisions and assets.
Copy feedback sitting for two weeks
The most common cause of a late launch, by a wide margin. Nothing after stage two can start without it.
Photography that doesn't exist yet
A shoot takes three weeks to organise. If you need one, we say so in week one so it runs in parallel.
Five people with sign-off
Two rounds of revisions turn into six. Name one decision-maker before we start and the whole thing moves faster.
Content ready on day one
Even rough. A messy Google Doc of real copy beats a tidy placeholder every time.
Analytics access early
Knowing which pages already earn traffic changes what we build and what we quietly retire.
The stack, and when each one earns its place
We don't have a house platform we push onto everyone. The choice happens after the scope call, based on who's editing the site next year.
Figma
Design, prototypes, and the handoff spec
Next.js
Most custom builds, App Router
WordPress
When your team publishes daily
Shopify
Stores, unless the catalogue demands headless
Vercel
Preview deploys per branch
Screaming Frog
Crawls, audits, redirect maps
Search Console
Indexing checks in launch week
Loom
Walkthroughs at handover
The part most agencies skip
Thirty days of included fixes starts the day the DNS switches, not the day we said we'd be finished. Anything broken in that window gets fixed at no cost — bugs, layout breaks on a device we missed, a form that stopped firing.
Handover is a Loom walkthrough of the CMS, a written doc, every credential, and the repository. It's deliberately complete enough that you could hire someone else tomorrow. Clients who can leave easily tend not to, which is the point.
After the thirty days, a maintenance retainer is optional and monthly. Roughly half our clients take one. The other half run it themselves and email us when they want something built.
- Loom video walkthrough of your CMS, recorded on your actual site
- Written doc covering the edits you'll make most
- Every credential, in a shared vault you own
- The repository, with commit history intact
- Redirect map and the launch-day checklist we ran
- Analytics and Search Console access under your account
What clients said after launch
Every one of these is tied to a case study you can open and check the numbers on.
The menu was the thing. It used to be a PDF that took forever to open and I had to email someone every time we changed a price. Now my manager edits it from her phone between services. Bookings are up about a third, and I get fewer calls asking what time we open.
We'd been told our store needed a redesign. Quesiono looked at it and said the design was fine, the problem was eleven apps and a five-step checkout. That was a cheaper answer than the one we expected and it worked — conversion is up 25% on the same traffic.
They spent the first week sitting with our analysts instead of with me, which I'll admit I questioned at the time. It's where they found a timezone bug that was causing half the manual work. The dashboard saves us about nine hours a week and our clients log in themselves now.
What people ask before signing
A forty-five minute call, then a written scope within three working days. The scope lists every page, every template, what's included, and what isn't. You sign it and pay 40% to hold a start date. Nothing begins before that document exists, because that's how projects grow sideways.
Ready for the forty-five minute version?
No deck, no discovery fee. We ask what the site has to do, you ask whatever you want, and you get a written scope three days later.
Rather write first?hello@quesiono.com— we reply within one business day.