Corevia / Services

What we do

Services that Earn Their Keep

Sold separately or as one retainer. Every engagement starts with a written scope and a fixed price.

However you start

What Every Engagement Includes

The same terms apply to a one-page site and a year-long build. None of it is an upsell.

A written scope, before anything starts

We scope during discovery, quote it, and hold that number unless you change what is in it. No estimate that quietly becomes a range.

One named owner

A single senior who knows your project, from the first call to the handover. Not a rotating pool and not an account manager relaying messages.

A staging URL from week one

You see the work as it goes up, in increments you can review. Nothing is revealed for the first time at launch.

Your code, your accounts

The repo lives in your organisation and the accounts are registered to you. Leaving is always an option, which is the point.

Documentation your team can run from

A runbook and a handover session with the people who will actually operate it, so the knowledge does not leave with us.

Thirty days of support after launch

Monitoring alerts and support included after go-live. After that we keep it running, or your team does with what we left behind.

How an engagement Runs

No discovery phase that eats the budget. Each stage ends with something you can hold.

  1. 1DiscoverWe map the stack, the owners and what actually has to change. You get a written scope with a fixed price.
  2. 2DesignFlows and screens reviewed against the scope. You get a clickable prototype.
  3. 3BuildWeekly builds on a staging URL. Your repo, your accounts, documented from day one.
  4. 4LaunchCutover, monitoring and a handover session with the people who will run it.
Not sure which one

Tell us what is Broken

One senior reads every message and replies with next steps and a rough range.