The Studio

After the build

What happens after version one ships, and why it is a subscription.

Handover is not the finish line. Software is never finished: your business moves, the platforms underneath it move, and the tool has to move with both.

So every build ships with its run. Maintenance keeps the software alive without you thinking about it; evolution keeps designing the next version as your operation changes.

It runs on the same rail as the build. Your feedback and the software's own signals land in one place, and there is always an agent ready to take the task.

A week after the build

Say it once in a mail. Get a verified change back.

The engagement does not change register when the build ends. It is the same rail, the same people, the same gate.

What you do

You say it once, in a mail.

No ticket to fill in, no form, no vocabulary to learn. Write it the way you would tell a colleague, in the thread you are already in. It reaches the rail, becomes a precise task with the code in view, and comes back as a finished change carrying the proof it works, waiting for your yes.
What happens without you

The software reports its own problems.

A system under subscription surfaces its errors on the same rail your feedback rides, anonymously. They become concrete tasks with the code already in view, and the straightforward ones get fixed practically as they happen, often before anyone writes to us about them. Not a support inbox: a loop that closes itself.

How the rail works

What the subscription covers

Four things, every month, whatever happens.

Hosting

It runs, and it stays up

We host it, patch it and keep it on supported versions, on infrastructure in accounts you own.
Watching

Somebody is looking

Errors and slowdowns surface on the rail. The small ones are fixed before they become your problem.
Changes

The work keeps going

A running allowance of change each month: the requests you send, built, verified and shipped on the same rail as the build.
A name

Someone answers

A named engineer who knows your system, and the record behind them so the knowledge does not walk out with a person.

Night shift in a computer room: one technician alone at an open panel with a lamp, rows of indicator lights on. — The archive The night shift, an open panel and a lamp. Someone keeps it running.

Two ways an engagement continues

Maintenance

We host it, watch it and keep it running: monitoring, updates and support under one subscription, so the software stays alive without you thinking about it.
Product evolution

Software is never finished. As your business changes we keep designing and shipping the next version, so the tool grows with the operation it serves.

The shape of it

One price at signature, then a subscription.

The build is agreed as one price before it starts, from the audit's plan, so you know what you are committing to. When it ships, the subscription begins: a percentage of the build, every year, for the hosting, the watching, the changes and the name behind them. A later phase is quoted the same way, and adds to the subscription rather than restarting it.

We do not publish figures here, because a number without your systems in front of us would be a guess. The audit is where it becomes real, and you keep the plan either way.