// work with us

We don’t hand you a login. We get you running.

Prove it first in our environment, on your real work. Then we bring Sage into yours — connected to your tools, running on the AI you choose — and stay with you until your team owns it.

Scope a pilot How pricing works

// 01 · the path

Three steps from first workflow to your own platform.

our environment

Pilot

One real workflow on your codebase, run in our environment alongside your current tools. You see the results before you commit to anything.

// [PILOT LENGTH] · scoped with you

your environment

Move Sage in-house

We host the platform in your cloud or on-premises, connect it to your repos, tickets and CI, and run it on the AI providers and models you prefer.

// annual licence + one-time setup

choose one

Studio or Resident

We build defined workflows and hand them over — or embed an engineer who builds with your team, sprint by sprint.

// see below for which fits

// 02 · the pilot

Low risk, on your real work.

No installation on your side. We run it in our environment so you can judge Sage on evidence, not slides.

// what we do

Pick one workflow with you — e.g. story breakdown or PR review
Configure it to your standards and definition of done
Build the knowledge store for the relevant part of your codebase
Run it on real tickets, alongside how you work today

// what we need from you

Access to the repository and tickets for that workflow [CONFIRM ACCESS LEVEL]
A handful of real tickets to run on
One engineer or lead to review outputs
A short weekly check-in

// what you get

A side-by-side comparison: quality, review effort, consistency and cost
Full traces of every run
A recommendation: go, adjust, or stop
No obligation to continue

// 03 · where sage runs

Pilot in ours. Production in yours.

After the pilot, Sage lives inside your boundary. Your code, prompts and accumulated knowledge never leave it.

// during the pilotOur environment

Hosted and run by us
Nothing to install or approve internally
Scoped access to one workflow’s repo and tickets

// in productionYour environment

Your cloud or on-premises [CONFIRM: AWS · Azure · GCP]
Connected to your repos, tickets and CI
Your AI choice: Anthropic, OpenAI, Google, Bedrock or self-hosted models
Your keys, held centrally — not on laptops

// 04 · after the pilot, choose one

Studio or Resident.

Both run on Sage in your environment. The difference is how we work with you.

project mode

sage.studio

We build defined workflows on a fixed scope, hand them over, and your team runs them.

Workflow design and build on your stack
Agents and skills configured to your standards
Integrations with your tools
Versioned prompts and documentation
Handover runbook and team walkthrough

Choose Studio when you know the outcome you want and need it scoped, built and handed over.

// fixed scope · milestone-based

people mode

sage.resident

An engineer embedded in your team, with architect-level oversight from us, who gets Sage working for you.

Sets up and tunes your workflows
Finishes the integrations with your tools
Customises agents and skills to how your team works
Sets up your initial projects
Builds alongside your engineers, so the know-how stays with you

Choose Resident when you have a roadmap and need people to execute it, sprint by sprint.

// monthly · minimum 3 months

// 05 · your first 30 days

What the pilot looks like, week by week.

// indicative · [CONFIRM TIMELINE]

week 1Kick-offPick the workflow, agree success measures, connect the repo and tickets.

week 2ConfigureEncode your standards, build the codebase knowledge store, first test runs.

week 3RunReal tickets through Sage alongside your normal process. Your reviewer approves at each gate.

week 4Compare & decideReview the results together: quality, review effort, consistency and cost. Go, adjust or stop.

// 06 · hire vs sage

The alternative is building an AI platform team.

Most teams your size can’t justify one. Here’s what it takes either way.

build it in-housewith sage

PeopleHire AI / platform engineers — scarce and slow to findOur team plus a resident if you want one

Time to first resultMonths to design and build the platformA working workflow in the pilot

GovernanceBuild cost tracking, audit and approvals yourselfBuilt in: Model Rail, Tool Gateway, traces, gates

Keeping up with toolsYour team evaluates every new model and toolWe do the R&D and publish verdicts on Sage Radar

Risk if it doesn’t workSunk salaries and build costA short pilot you can stop after

// interactive cost calculator planned for a later version

// 07 · how pricing works

Scoped to your engagement. No surprises.

Every engagement is priced after a short scoping call, based on the workflows, team size and environment.

platformAnnual licence + setupSage hosted in your environment, on your infrastructure.

sage.studioFixed scopeMilestone-based delivery. No retainer after handover.

sage.residentMonthlyMinimum 3 months. Includes architect oversight.

// AI model usage is billed by your chosen providers, on your own keys · [CONFIRM]

// 08 · questions buyers ask

FAQ

Can the pilot run in our environment instead?

Yes, if you prefer. Running it in ours is faster because nothing needs installing or approving on your side — but we can scope it either way. [CONFIRM]

What happens to our code during the pilot?

Access is scoped to the one workflow we’re piloting, and used only for that pilot. [CONFIRM DATA HANDLING TERMS]

Do we have to choose Studio or Resident straight away?

No. Decide after the pilot, once you’ve seen the results. Some teams start with Studio and add a Resident later.

Which AI models can we use?

Whichever you prefer. Sage is model-agnostic: in your environment it runs on the providers and models you approve, including self-hosted.

Will we depend on you forever?

No. Studio ends with a handover, and a Resident builds alongside your engineers so the know-how stays with your team.

// next step

Start with one workflow.

A 30-minute scoping call. We come prepared, and you leave with a clear pilot proposal.

Scope a pilot See how it works