Big consultancies sell methodology as a sales slide. We publish ours: five phases, each with a clear goal, named deliverables, a decision gate — and what we need from you. No project enters a phase before the previous gate is passed.
Phase 1 — Discovery (week 1)
Goal: understand where automation actually creates value — before anyone talks technology.
- Deliverables: process inventory with time-cost scoring · prioritized automation roadmap · ROI projection per initiative
- Gate: a joint go/no-go decision based on the numbers — a "no-go" is a clean outcome too
- Your contribution: 2–3 hours of interviews with the people affected, read access to the relevant systems
Phase 2 — Design (week 2)
Goal: design the solution completely before anything is built.
- Deliverables: solution blueprint (Skills, MCP connectors, data flows, review gates) · written acceptance criteria · security and data-protection concept per our standards
- Gate: your sign-off on the blueprint — development starts only after that
- Your contribution: one review meeting, decisions on open design questions
Phase 3 — Development (weeks 3–5)
Goal: build and test with your real data — not demo data.
- Deliverables: the Skills and connectors themselves · test protocol against the phase-2 acceptance criteria · technical documentation
- Gate: acceptance test passed — measured against the pre-agreed criteria, not our impression
- Your contribution: test data, feedback in two short review rounds
Phase 4 — Deployment (week 6)
Goal: production operation with a team that understands the system.
- Deliverables: team training · operations runbook (usage, edge cases, escalation) · supervised go-live
- Gate: productive operation without our daily involvement
- Your contribution: team time for the training (typically half a day)
Phase 5 — Optimization (ongoing)
Goal: measure whether the promised results materialize — and refine.
- Deliverables: metrics report (time saved, error rates, usage) · prioritized improvement backlog
- Your contribution: one short review per month
How we run projects
Every project gets, regardless of size:
- Weekly written status report — done, planned, risks. No guessing where the project stands.
- Decision log — every relevant decision recorded with date and reasoning.
- Acceptance criteria before the build — agreed in phase 2, measured in phase 3.
- Clear escalation path — you know whom to reach and how fast.
- No lock-in — full documentation and training are part of the handover. You can operate without us at any time.
The principles behind it
- Fixed price, not day rates: you know the cost before we start — transparent packages.
- Human-in-the-loop: AI proposes, humans decide — in our work and in the systems we build for you.
- Everything documented: what isn't written down doesn't exist.
Questions about the approach? Book a free 30-minute call — we'll walk the method through your specific case.