The studio
We exist so you stop buying a promise.
One team from first sketch to launch. Nothing goes into production until you have used a working prototype.
- 1
- team, from the brief to launch.
- 6
- steps from the brief to launch and care.
- 3
- ways to work with us: prototype, build, and care.
- 100%
- of the code, content and accounts in your name.
One studio. One brief.
We plan, design, and ship the product you can put in front of customers or your team. Company websites, ecommerce, SaaS, and tools built for how you actually work. One studio in Manchester. You use it in the browser before the production build goes ahead.
Most tech projects fail at the handoff: strategy in one room, design in another, engineering somewhere else. We keep one team on the brief from first sketch to launch, and nothing goes into production until you have used a working prototype.
The people who scope the work are the people who design it and write the code.
Handoffs are where products go wrong. We removed them.
- 01
Prototype first
You use the system before the production build goes ahead.
- 02
One team
Strategy, design, and engineering stay in the same room.
- 03
You own it
Code, CMS, domain, and hosting sit in your name.
Why teams build with us.
See it before it is built.
A working prototype comes first. The production build goes ahead once you have used it and approved it.
Talk to the people building it.
No account managers. The people who scope the work design it and write the code.
Own everything.
Code on your repository, content in a CMS you control, domain and hosting in your name.
A fixed price.
Websites are £2,500, or £3,000 over three months. Larger builds are quoted from the brief. No hourly billing.
Honest about fit.
If the budget is not enough, or another team would serve you better, we say so.
Care after launch.
Keep us on for changes, or take the code and run it yourselves. No lock-in.
The process.
Six steps. You use the prototype before the build goes ahead.
- 01
Discuss the brief
Your business, audience, goals and what it must do.
We talk through the business, who it is for, what they need to do, and the functionality it needs. Settled before anyone opens a design file.
- 02
Agree the scope
Deliverables, price, timeline, milestones and exclusions.
The proposal sets out what is included, the price, the timeline, the payment milestones and what is not included. Work starts once it is agreed.
- 03
Prototype
Something real to click through and judge.
You click through a working prototype in your browser. If the direction or the journey is wrong, you find out before the production build.
- 04
Review and approve
Your feedback, and any scope changes agreed.
We collect your feedback and agree any changes to the scope. The production build goes ahead once you approve it.
- 05
Build and test
The approved work, built and checked.
The same team builds the approved solution, checks the key journeys and prepares it for launch. It lives on a repository you own.
- 06
Launch and care
Live, then Aevion Care on the agreed date.
We launch the agreed work and start Aevion Care on the date your payment option sets.
From our research.
What the evidence says about websites, the market and software, written up by the studio.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.