Design systems
Tokens, components and docs that are faster than a blank file.
A system is only useful if people use it. We ship components with states, accessibility notes and live examples in the same place as the site.
Why it matters.
When a team ships more than one surface, buttons quietly multiply. We start with tokens, then components, then documentation written beside both. The test is adoption.
Figma and code stay in step. You click the live library. The rest of the build goes ahead once the system is faster than starting again.
What's included.
What the work usually covers. Your proposal sets out exactly what is included.
Tokens
Type, colour, space and motion as named values, shared by design and code.
Components with states
Hover, focus, error, empty and loading, designed and built, not guessed.
Accessibility notes
Contrast, keyboard and screen-reader behaviour written beside each component.
Figma and code in step
One source for designers and developers, kept in sync as it grows.
Live documentation
Guidance next to working examples, in the same repository as the site.
A plan for adoption
Migration notes and a rollout your teams can follow, page by page.
What good looks like.
What every project like this aims for.
- 01
No new buttons on page ten
The library already has what the next page needs, so the brand never forks.
- 02
One scale for site and product
Marketing pages and the app share the same type and spacing.
- 03
Docs that are the components
Guidance lives beside live code, so nobody maintains a second file.
Pricing.
SaaS, web apps, business tools and other larger builds are quoted from the brief. Your proposal fixes the price before work starts.
Quoted from the brief
For products, stores and business tools
Fixed price
agreed in writing before work starts
What your proposal fixes
- The scope: features, pages and integrations
- One fixed price, with no hourly billing
- The timeline and payment milestones
- Revision rounds and what is not included
- A working prototype before the production build
Aevion Care
Hosting and support after launch
£500
a month, separate from the website fee
What's included
- Managed hosting for your website
- SSL and standard security set-up
- Routine maintenance and technical updates
- Backups and recovery support, where your platform allows
- Uptime and performance monitoring
- Aevion View, your own dashboard of traffic, enquiries, speed and uptime
- Conversion and lead tracking, where it is set up
- A set allowance of minor website updates
- Technical support
How it works.
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.
Questions.
Do we actually own it?
Yes. The code lives on your repository, the content in a CMS on your account, the domain and hosting in your name. Nothing is rented back to you, and nothing is held to keep you here.
How long does it take?
A typical marketing site runs four to eight weeks from first call to launch. A SaaS product or internal tool takes longer because the product itself is the work. Waiting on copy, access, and decisions is usually the bottleneck, so we agree that schedule up front.
What happens after launch?
We launch the agreed work and walk you through editing it yourselves. Aevion Care then looks after hosting, maintenance, monitoring and minor updates for £500 a month, starting on the date your payment option sets.
Do you only build marketing sites?
No. We build websites, SaaS products, web apps, ecommerce stores, business tools for teams, and the design systems that keep them consistent. If it is a product people use in a browser, we can ship it.
Do we get a written contract?
Yes. Every project starts with a written proposal that sets out the scope, price, timeline, payment milestones and what is not included. It works alongside our terms of business, and if the two ever differ, your proposal wins.
More services.
- WebsitesPositioning, structure and a fast, accessible Next.js site on a repository you own, with a CMS your team can publish from.
- SaaSAccounts, plans and billing, dashboards and the flows that decide whether people stay, for software you sell to many customers on a subscription.
- Web appsBooking systems, member areas, marketplaces, quote builders and the tools your customers use on your site, built as fast web applications that work on any device.
- EcommerceCatalogue, product pages, checkout and the pages paid traffic lands on.
- Business toolsDashboards, client portals and the tools your team runs the business on, built around how the work actually moves.
- Aevion CareAevion Care looks after your website once it is live, and gives you Aevion View to see how it is doing.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.