Step 2: Pilot

One workflow. Shipped. Measurable.

The Pilot proves AI leverage inside your actual environment — bounded, with clear rules and a signal you can measure.

€2,000 3–6 weeks Remote, sync + async

Start qualification See details

Deliverables

What you end up with

One installed workflow/operator system (bounded, one objective)

Initial integrations and operating rules

Proof artifacts (redacted/anonymized as needed)

Handoff and adoption notes

Measurable signal: baseline vs. post-install

Evaluation pack with real results

Decision filter

Is Pilot right for you?

Yes, if…

Blueprint or qualification shows one clearly bounded first workflow
You want proof in your real environment before scaling
You want a shipped implementation, not a concept
You can assign an internal owner for the workflow

No, if…

You want a broad rollout across many teams at once
You have no stable workflow to anchor on yet
You expect AI to replace ownership rather than support it
You are looking for a "mini-Foundation" — this is proof, not infrastructure

Investment

€2,000

3–6 weeks
Remote, sync + async

Start qualification ← See Blueprint first

FAQ

Key questions

Everything you need to know before starting. Clear, concrete, no surprises.

Start qualification

What exactly do I receive at the end of the Pilot?

You get something usable inside your tools, not just advice.

1 running workflow in your environment (or agreed staging)
Runbook + roles (owner, backup, escalation)
Operating rules (what can run automatically, what requires approval)
Proof pack: before/after metric, logs, short walkthrough
Clean handoff, you own code, configuration, and documentation
Recommendation for the safest next install (one sentence)

What are typical Pilot workflows (examples)?

We pick 1 use case that removes real weekly pain. Examples:

Key constraint: one workflow, one owner role, one system context, one measurable goal.

Leads: inquiry comes in, gets qualified, reply is prepared, owner gets notified
Support: ticket is categorized, priority suggested, next step drafted, escalation triggered
Ops: weekly report (numbers + anomalies) is generated and posted to Slack/Teams
Sales: meeting notes become structured follow-ups, CRM update is prepared

What access and systems do you need from us?

Only access to what the one workflow needs. Default is least-privilege and sandbox-first.

Production write access only with explicit written approval, otherwise human-in-the-loop.

Communication: Slack or Teams
Source system: e.g. HubSpot, Notion, Google Sheets, email
Target system: e.g. email draft, CRM draft, internal log
Execution layer: n8n or a secured agent setup

How is our data handled — what leaves our environment?

We minimize data access and document everything.

No model training on your data
Clear data flow (what goes where, why)
Credentials stay in your accounts
Redaction available for proof assets
GDPR-aligned, least-privilege by default

What happens if we decide not to continue after the Pilot?

You are not locked in. There are three clear outcomes.

In all cases: you keep the workflow, runbook, proof pack, and ownership.

Proceed to Foundation (wider install surface)
Extend via change order (if scope expansion is truly worth it)
Stop, with clean decommissioning

What if I don’t have a Blueprint yet?

The Blueprint is included in the Pilot price. We start with the Blueprint phase to find the right first workflow and define success criteria. You only proceed to the installation (Pilot) phase if you explicitly say GO after the Blueprint review. There is no additional cost for the Blueprint phase.

Still not sure?

Start with the free qualification. We will check fit and set the starting point.

Start qualification