Engagement model

How a pilot becomes a practice.

One workflow, then more. Scope, proof, expansion — each phase confirmed before the next begins.

Entry pointOne bounded pilot
PricingSales-assisted, no price list
ExpansionEarned by pilot close state

Three phases, each confirmed before the next begins.

There is no automatic expansion. Each phase is a deliberate decision. The pilot closes with a clear view of what worked, what changed, and whether a broader engagement is warranted.

01

Scope

You and unikode agree on one workflow to run first. You name the reviewer, define the source set, and set the decision window. No work begins until the scope is confirmed in writing.

02

Proof

The pilot runs. The system executes the scoped workflow. The named reviewer reviews and approves. You receive the finished artifact, the evidence record, and a scope review at the close.

03

Expansion

If the pilot produces value and the engagement is confirmed to continue, additional workflows are added. Each addition is scoped the same way the pilot was — one workflow at a time, with a defined reviewer and a bounded source set.

No automatic expansion. Each phase is a deliberate decision confirmed in writing before the next phase begins.

Sales-assisted. No public price list.

unikode does not publish a price list. All 2026 engagements are confirmed through a direct scoping conversation. Pricing is set based on the scope of the workflow, the source set size, and the review cadence.

There is no self-serve tier. There is no trial. The pilot is a real engagement with a real fee, scoped and confirmed before it begins.

If you want to understand what a pilot would cost for your specific workflow, that conversation starts with a scoping call.

One conversation, one confirmed scope.

A scoping call covers the key questions before the pilot begins. At the end of the call, you have a confirmed scope or a clear reason why the pilot is not the right fit yet.

A scoping call covers
  • The workflow you want to run first
  • The source set you will bring to the pilot
  • The named reviewer and their approval cadence
  • The timeline and the decision window
  • What you will receive at the close

Pilot

Start with one workflow. Decide from evidence.

The cleanest evaluation still starts the same way: scope one workflow, keep the reviewer visible, and make the next decision from evidence.

Scope

One workflow, one named reviewer, and one bounded source set.

Return

A readable decision packet with draft, evidence, blockers, and next step.

Decision

Expand, hold, or stop after the first run proves out in the current stack.

Start a pilot