$2.1M
Big-4 quote the client's team built in-house after a 6-month Effektiv adoption engagement
4
engineers certified at exit — each signed off three independent agent ships
90 days
to independent AI shipping — the exit gate is written into the contract from day one
0
recurring vendor dependency at exit — the eval rig, runbooks, and prompt rules are yours forever
Why this is different
An ASX-100 manufacturer spent $480K on six months of Effektiv embedded pairs. The following AI build was quoted by the Big-4 at $2.1M. The team built it in-house using the eval rig and playbook they built during the engagement. Four engineers were certified at exit.
Skill is not transferred by observation, workshops, or documentation handover. It is built by doing real work under someone who has done it before. When your engineers pair with ours, they are working on production code with real eval rigs and real architectural calls — not model exercises.
Big-4 sells delivery. We sell capability.
| Dimension | Effektiv adoption | Big-4 advisory | Generalist agency |
|---|---|---|---|
| Skill transfer mechanism | Daily code review pair on real work | Workshop deck + observers | Documentation handover |
| Exit gate clarity | Your team ships AI without us on the call | Milestone sign-off | Course completion certificate |
| Eval rig ownership | Your repo, your control | Vendor framework retained | Generic templates |
| Cost outcome (year 2) | Internal-cost builds, no recurring vendor fee | Next engagement at vendor day-rate | External re-engagement |
| Certification basis | 3 independent agent ships, signed off | Hours-attended attestation | Test-passed badge |
How we deliver
Two weeks of listening before a line of code. The price is fixed at the end of Design — not at kick-off.
Phase 1 · Months 1–2
Your engineer and ours share one work stream. Daily code review and eval review together. AI agents draft the code; the pair decides what passes the eval rig. Weekly sessions cover tool choice, prompt design, and eval design on actual work — not model exercises.
Phase 2 · Month 3
By month three your team ships an AI feature with our engineers off the call. That moment is the exit gate written into the contract. We do not declare done until it happens.
Phase 3 · Months 4–6
The AI playbook is written and tuned during the work, not handed over as a document at exit. The engineer who built the eval rig alongside ours is training the next hire by month six.
Quality gates
Every output passes a multi-gate evaluation before it merges or ships. Outputs that fail do not proceed. The eval rig and all gate code are yours at exit.
Eval rig · sample run
Eval rig source code shipped to your repo at exit.
Sample engagement
An ASX-100 manufacturer wanted an in-house AI capability rather than a recurring vendor contract. Effektiv pairs embedded for six months at $80k a month — $480K total. Four engineers certified at exit. The following AI build was quoted by the Big-4 at $2.1M. The team built it in-house, using the eval rig and playbook they built during the engagement.
Read the full case →
Compliance posture
ISO 27001 in progress (Q3 2026) ISO 42001 aligned NIST AI RMF mapped IRAP path Q4 2026 Full governance posture →Other services
Service
AI archaeology decodes what the documentation missed. 11 weeks median.
Read more →Service
RPA and ESB out, agent mesh in. Run cost down 50–70%.
Read more →Service
Custom products and greenfield software, shipped in 8–14 weeks.
Read more →Service
AI in the alert path. 50–70% drop in human-paged incidents.
Read more →Service
AI helpers that draft for human review. Brand-voice eval gated.
Read more →Common questions
With-you mode only
Pair with our engineers on real production work. Your team ships an AI feature without us on the call in 90 days. That is the deliverable the contract is written against.