Skip to content

SaaS

The product your customers subscribe to, built after you have clicked it.

Accounts, plans and billing, dashboards and the flows that decide whether people stay, for software you sell to many customers on a subscription.

See pricing

Why it matters.

A deck is not a product. We start with the journeys that make money: sign-up, first value, upgrade and cancel. The interface is designed for the empty first day as well as the busy hundredth, and the data model is built for real customers from the start.

A clickable prototype on the real stack where we can. Then accounts, payments and the database you own, once you have used the prototype and approved it.

What's included.

What the work usually covers. Your proposal sets out exactly what is included.

  • Core journeys first

    Sign-up, first value, upgrade and cancel, mapped and clickable before the build.

  • Accounts and teams

    Sign-in, organisations and roles on identity you control.

  • Billing

    Plans, payments and invoices with Stripe, on keys you hold.

  • Dashboards that work on day one

    Empty states, errors and a first run that gives people a job to do.

  • Your data, your database

    A schema built for real tenants, in an account you own.

  • Integrations

    Email, webhooks and the tools your customers already use.

What good looks like.

What every project like this aims for.

  1. 01

    A first run that is never blank

    New users land on one clear task, not an empty screen.

  2. 02

    Billing tested by using it

    Upgrade, failed payment and cancel work in the prototype before any webhook exists.

  3. 03

    A data model for real customers

    The schema is designed for the tenth customer, not just the first.

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

Tell us what needs to ship.

You use a working prototype before the production build goes ahead.