How we launch
no surprisesPeople buy confidence. So here's what working with Lancio is actually like: how a project starts, how we communicate, how the money works, and what we'll need from you. The step-by-step shape of each service lives on its own page; this is everything that stays true either way.
It starts with one job
one job. not ten.Every project gets one job: the single outcome the work has to deliver, agreed in plain words before anything is designed.
- “Turn local service enquiries into qualified consultation bookings.”
- “Let schools book CPD sessions without manual admin holding the process together.”
- “Make sure Google can understand and trust the important pages before more money goes on marketing.”
We call it The One Job. It's pinned down in discovery, written into the proposal, and every design and build decision gets checked against it. Before launch it becomes the final question: does the thing we built actually do the job we agreed? It keeps projects out of opinion territory and pointed at the outcome you're paying for.
How a project starts
- 01
Get in touch
Tell us the problem. You don't need to know the solution: we'll come back with a few practical questions about what's driving this, whether there's a deadline, and whether budget and timeline are realistic. If we're not the right fit, we'll say so instead of wasting your time.
- 02
A discovery call
We dig into the business, the audience and The One Job. Usually by video; in person can work locally. For straightforward projects, this and a written scope is all the discovery anyone needs.
- 03
A written proposal
Not a deck, a plain document: the objective, recommended scope, what's included and what deliberately isn't, timeline, price and payment schedule, what we'll need from you, and the next step. For websites, often a rough page plan; for web apps, milestones and risks.
- 04
Booked in
A deposit books the project into the schedule. We take on a small number of projects at a time so each one gets proper attention. Availability changes month to month, so if there's a fixed deadline, it's worth getting in touch early.
One honest exception: for larger or less-defined projects (web apps especially) we may recommend a paid discovery and roadmap first, from £500–£1,500 depending on complexity. It's a focused review over an agreed window, not a full-day workshop, and it turns guesswork into a scoped plan you own. If we move into the full project, part of that fee may be credited.
While we work
- One channel, decisions in writing
- Email is the record. Calls for discussion and the big decisions, short video walkthroughs when showing beats telling. Approvals, scope and deadlines always get captured somewhere you can find them again, not buried in a chat thread.
- Updates you don't have to chase
- At least weekly on an active project, and always at the moments that matter: structure, design direction, staging, testing, launch. No going dark until a big reveal.
- Real work, not decks
- You review the actual thing: one strong design direction first, then the real site or app on a staging link once there's something worth reacting to. Two rounds of refinement are included on the agreed direction.
- Scope stays honest
- Small, helpful changes get judgement, not paperwork. Anything that genuinely changes scope gets flagged before the work happens: we swap it, phase it, or quote it. No surprise invoices, no silent scope creep.
- Your side of the deal
- Timely feedback, within two or three working days at review points, plus content, assets and access by the dates we agree. If inputs slip, the timeline moves with them; we'll be straight about that rather than quietly absorbing delays.
How money works
A fixed price, agreed before we start. Most projects run half up front to book the work in, half before launch or handover. Larger builds are split into milestone payments tied to real progress: scope approval, working builds, testing, launch.
Scope changes are flagged when they come up and agreed before the work happens. Final payment is due before public launch or the transfer of final files. It's a deliberately boring structure, and that's what keeps everyone comfortable.
After launch
Every project ends with a proper handover: a post-launch window (usually 14 to 30 days) for launch-related fixes and questions, practical training with a walkthrough, short videos and checklist-style notes rather than a manual nobody reads, and documentation for the parts you'll actually touch.
Ownership is simple: the domain, the content and the finished code are yours once the project is paid for. If you'd like it looked after, monthly care plans start from around £250 for websites and more for business-critical platforms, scoped to risk rather than padded.
What to expect either way
- You work directly with the people who own the work, every step.
- A fixed, clear price agreed before we start. No meters running.
- Decisions in a message, not a fortnight of meetings.
- Honest advice, including when the answer is "you need less than you think".
- If something isn't working, you'll hear it from us first, with a plan, not an excuse.
The shape, per service
The relationship is the same everywhere; the sequence and timescale aren't. Each service page shows its own launch path, timeline and pricing.
- WebsitesDiscovery, structure, one strong design direction, build, careful launch, care.
- Web appsMVP scoped first, built in milestones, launched useful, improved on real use.
- Search readinessAudit, prioritise, fix what access allows, hand over a plan you own.
- Marketing foundationsThe MOT: offer, messaging, tracking and site reviewed, gaps prioritised, plan delivered.
- Digital marketingSetup first; monthly support only when there's a clear, continuing job for it.
- Brand identityPositioning, one recommended direction, refinement, a system you can actually use.
Ready when you are
Tell us what you're building. You'll hear back from a real person as soon as possible.