How it works

Start with the map. Then build the operating layer.

The engagement starts with a fixed diagnostic and moves into implementation only when the operating layer is clear. Every phase has concrete outputs, handover artifacts, and ownership boundaries.

10 · Engagement

Path · 4 phases · 12 weeks · then you operate it

How a Spark engagement actually runs.

Not a deck. Not a strategy. A working operating layer your team owns and runs. Four phases, twelve weeks, then we hand you the keys.

W 01 — 02Phase 01 · Map

P / 01

Audit your current operating layer.

We inventory every AI surface in play, locate where your decision logic actually lives, and score each workflow against the autonomy ladder. The map exists before anything is built.

What we do

Inventory copilots, agents, automations
Locate decision logic per workflow
Score current autonomy (L1 → L4)

What you leave with

A Spark Map — your operating layer, today
A ranked list of intervention targets

W 03 — 06Phase 02 · Instrument

P / 02

Install SparkOS primitives.

We stand up memory, schemas, and approvals in an environment you own. Tool connectors are wired as instruments — not destinations. Decision rules become versioned, inspectable artifacts.

What we do

Memory, schemas, approvals in your cloud
Tool connectors as governed adapters
Codify goals and decision rules

What you leave with

An owned intelligence layer
Logic your team can read, edit, version

W 07 — 10Phase 03 · Operationalize

P / 03

Move workflows to autopilot.

Two or three load-bearing workflows migrate to L3. Eval suites run in production. Approval boundaries are explicit — everything outside them runs unattended. This is where the operating layer starts paying for itself.

What we do

Migrate 2–3 workflows from L1/L2 → L3
Stand up production evals + drift detection
Define approval scopes and timeouts

What you leave with

Decisions executed by the system
Approvals as exceptions, not steps

W 11 — 12Phase 04 · Hand off

P / 04

Operate without us.

Runbooks, eval dashboards, and extension patterns transfer to your team. We hand over a 90-day plan to migrate further workflows from L3 → L4. Ongoing support is optional, quarterly, and on your terms.

What we do

Runbooks + eval dashboards transferred
L3 → L4 migration plan, 90 days
Team enablement on extension patterns

What you leave with

Full ownership. We're optional.
A path to self-driving, on your timeline

11 · Offering

Two tiers · one direction · priced

Two ways in. One direction.

A fixed-scope first step and a full implementation. Both are services — high-trust, hands-on, owned at handover. SparkOS isn’t a license you buy. It’s what we build into you.

Tier IThe diagnostic

Foundation Track

A short, fixed-scope engagement. We audit your current operating layer, score every surface against the autonomy ladder, and leave you with a Spark Map and a ranked list of intervention targets. Low risk. Self-contained. Concrete.

Investment€5,000· fixed

Duration1–2 wk· scheduled

You leave with

Your Spark Map — every AI surface, ranked
Decision-logic inventory
Ranked intervention targets, scoped
A clear next step, with or without us

Engagement coverage

P/01 MapP/02 InstrumentP/03 OperationalizeP/04 Hand off

Book an intro call →

Tier IIThe full build · Spark’s focus

Implementation

The end-to-end engagement. We install primitives, codify your decision logic, move two or three load-bearing workflows into autopilot, and hand you the runbooks and eval suites to keep extending. You leave with an operating layer your team can run for the next decade.

Investment€25k–€40k· scoped

Duration8–12 wk· embedded

You leave with

Owned memory, schemas, and an approvals model
2–3 workflows in production at L3 (autopilot)
Eval suites, drift detection, audit trail
Runbooks, extension patterns, an L3 → L4 plan

Engagement coverage

P/01 MapP/02 InstrumentP/03 OperationalizeP/04 Hand off

Book an intro call →

N / 01 · After delivery

Ongoing review, L3 → L4 migration, and extension work are available on retainer — but only when you ask. The point of handover is that you don’t need us. Optional. On your terms. Quoted case-by-case.

N / 02 · About SparkOS

SparkOS is the productization path — an accumulating open spec we extend with every engagement. It is not a license, a seat, or a subscription. You take it with you when we hand off.

12 · Intake

Stop renting your company's intelligence.

Your business is already a codebase. Spark makes it explicit, executable, and owned. Start with the €5,000 Foundation Track — a fixed-scope diagnostic that ends with your Spark Map and a clear next step. With or without us.

Book an intro call →Read the thesis