How We Work — Engagement Model

The engagement spine

Six stages. Each stage has a defined output and acceptance test. You only move forward when the current stage is verified — not assumed.

Stage 01

Diagnose

We walk the floor, read the data you already have, and surface the real bottleneck — not the one that makes the best slide. Output: a ranked diagnostic report with root-cause findings and a scoped implementation plan.

Stage 02

Survey

We map current state across people, process, and source systems — so the calibration is grounded in how the site actually runs. Output: a baseline maturity map with gaps, priorities, and data-flow diagram.

Stage 03

Calibrate

We tune the agentic stack to your environment — data shapes, shift patterns, existing tools, and what operators will actually use. Output: calibrated system config + acceptance criteria.

Stage 04

Deploy

We install the system, train the people who run it, and verify outcomes against acceptance tests — not assumptions. Output: live system, trained operators, and a documented handover pack.

Stage 05

Monitor

The system keeps running and improving — your team operates it, we're the backbone. Output: monthly performance snapshot, anomaly alerts, and continuous calibration adjustments.

Stage 06

Handover

Documentation, training, and ownership transfer included. We stay behind after the engagement ends. Output: full documentation pack, training records, and a 90-day post-handover check-in.

Typical engagement shapes

Most engagements start with a Diagnostic. From there, the scope is shaped around what we found — not a fixed package you have to buy.

Shape 01

Diagnostic-first

A standalone diagnostic engagement: floor walk, data review, root-cause findings, and a scoped implementation roadmap. Ideal when you need evidence before committing.

Typical duration: 2–4 weeks

Shape 02

Full deployment

Diagnose → Survey → Calibrate → Deploy → Handover. A complete engagement from bottleneck identification to a live system your team owns.

Typical duration: 8–16 weeks

Shape 03

Retainer / ongoing

Post-deployment monitoring and continuous calibration. We stay available for anomaly response, new feature tuning, and periodic performance reviews.

Typical cadence: Monthly retainer, minimum 3 months

What's included — and what isn't

We believe in setting expectations before proposals. Here's the honest boundary.

Included

Floor walk, operator interviews, and process observation
Data review and root-cause analysis
Agentic system design, calibration, and deployment
Operator training and documented handover
Post-deployment monitoring and anomaly response
90-day post-handover check-in
Role-based access and audit trail on all actions

Not included (by design)

ROI guarantees before a diagnostic is completed
Fixed percentage improvement promises
Client data used to train external models without consent
Unsigned or unverified claims, certifications, or partnerships presented as fact
Ongoing operational responsibility after handover
Hardware procurement or capital expenditure

Engagement commitment

“We don’t guarantee ROI or a fixed percentage improvement before a diagnostic. We do guarantee a measurable, documented diagnostic before any system is proposed, and a defined acceptance test before anything runs unsupervised. We won’t present unverified results, certifications or partnerships as fact.”

— Verdan Forge

A defined path from first conversation to system your team runs.