Renewal subscription

Technology renewal as a predictable monthly service.

One monthly fee for an agreed renewal scope. Your first workflow migration is included, renewed parts stay upgraded, and you see measurable progress every period.

Two-year term, price quoted after a short assessment
First workflow migration included in the subscription
Exceptional projects scoped separately, exit terms agreed up front

Fabrica is a proposed service in development. Scope, fees and terms are agreed after the first conversation and assessment.

Tell us about one priority

Four quick questions. We reply within one business day with times for a 30-minute call.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

We use your details only to arrange and prepare for the call. Privacy

What the subscription covers

Planned renewal, not an open-ended project.

Continuous observation and living documentation

The system's behavior, rules and reports stay documented as they change, so the knowledge no longer sits with a few people.

A renewal backlog you prioritize

Every candidate workflow sits on a visible backlog. You set the order, and Fabrica never reorders it for you.

Agreed capacity each period

A defined amount of renewal work per period, reported against the backlog, with spending caps that pause work rather than overrun.

Proof and shift for every workflow

Each renewed workflow is proven against the running system and shifted with acceptance criteria and rollback.

Upgrades on renewed parts

Framework and dependency upgrades for the parts already renewed, so they do not become the next legacy system.

Your code, your repository

Everything built lives in your repository and on infrastructure you choose. If you stop on the agreed exit terms, you keep what was delivered.

How the fee works

Priced from evidence about your system.

The monthly fee is set from what the assessment finds: how many workflows are in scope, how traffic is concentrated, and how complex the data and integrations are. It covers agreed scope rather than an open-ended promise. How the service is treated in your accounts is your finance team's decision.

Monthly payments for agreed renewal capacity
First workflow migration included
Upgrades on renewed parts included
Exceptional projects priced separately
A report each period on what moved and what it cost

Dashboard · todaycap $41.20 / $120.00

Token cost$41.20pipeline $36.10 · chat $5.10

Sandbox-hours3.4 hidle snapshots saved 2.1 h

Items done4avg $11.80 per item

Needs human3merge · config · plan review

RoleRunsCostShare

Dev6$15.80

Architect7$14.20

Business Analyst3$4.30

QA2$3.20

Spend and throughput are visible by day, item and role.

Is it right for you?

A subscription fits some systems better than others.

A good fit when

The system is central to revenue or operations
Every change is slow and expensive
You expect to keep renewing rather than run one big project
You want renewal to be a planned line of spend

Probably not when

The system is stable and rarely needs to change
A narrow upgrade would solve the problem
You need a one-off migration with a fixed end date

Questions

About the subscription

What does it cost?

The price is quoted after a short assessment of the system, because it depends on scope. We do not publish a list price while the service is in development.

Why a two-year term?

We expect a first migration plus a period of steady renewal to need that long to show clear value. Terms, including how to exit, are agreed before you commit.

Is the migration really included?

Your first agreed workflow migration is part of the subscription scope. Larger or additional migrations are scoped during the assessment and shown separately.

What if our priorities change?

You reorder the backlog. The agreed capacity moves to whatever you put at the top.