Four services for becoming an AI-first company.
Each Domain-Driven service addresses a specific operating constraint. The work produces a domain map, reconciled data, an AI engineering practice, or software delivered against business milestones.
You see the scope, price, and next step before you sign.
Start with the constraint causing problems today.
Our work starts with a defined operating problem. Before work begins, you receive the scope, deliverable, and route into the runtime.
Domain-Driven Process Modeling
1 week (five-day workshop), fixed.
Starts from €8k.
founders, COOs, and heads of operations who can name a process unique to their business but have never seen it documented.
a readable domain map with a glossary, event catalog, audit checklist, and scope recommendation.
the map becomes the business-readable contract used by the PNS Method.
AI-Ready Data Foundation
4-8 weeks.
Starts from €15k.
COOs, CIOs, and heads of data dealing with conflicting dashboards, mismatched customer records in the CRM and ERP, or AI pilots held back by unreliable data.
a domain data model, reconciled canonical sources, and the ingestion and ETL pipelines that keep the model current.
Shugyo runs on this data foundation, and the runtime queries it.
AI Engineering Practice
4-6 weeks plus optional retainer.
Starts from €10k.
CTOs and VPs of engineering whose teams already use Claude Code, Cursor, or agentic workflows and now need a consistent engineering practice.
an engineering practice your team can run, including agent workflows, review rituals, evaluation suites, and an internal playbook.
the practice uses the PNS Method, while EHOS provides governance and an audit trail for AI-generated work.
Forward Deployment Team
3-9 months, phased to milestones.
Priced against the milestones identified in the map, with billing tied to each milestone.
founders and COOs who have validated the process and want software delivered against business milestones.
working bespoke software delivered milestone by milestone. Each release includes decision records and an updated scope view. You own the codebase, data, and operating model.
the running system belongs to you. We assess each additional process on its own merits before starting another cycle.
The engagements build on one another. The map defines the process; the data foundation supports it; the engineering practice works against it; and the deployment team ships the software.
The same five rules apply to every engagement.
The constraint and deliverable change, but the way we work stays consistent.
-
R / 01
Fixed scope
You receive the scope and deliverable before signing. Any discovery work has a defined boundary and price.
-
R / 02
Domain-Driven
We use the same vocabulary across every engagement, drawn from the method . Your team builds the language once and reuses it.
-
R / 03
Owner-in-the-room
The founder, CEO, or COO attends the kickoff and close. The map records the decisions made in the room.
-
R / 04
Pre-priced
Starting prices are public, so you have a realistic cost range before booking a call.
-
R / 05
Graduation is explicit
Every service states whether it produces a PNS contract, governed software on EHOS, Shugyo intelligence, or a combination, with timing agreed in advance.
The real deliverable of an engagement is a map your team can read, and the software is generated from it.
When we decline an engagement.
We will say so during the fit call if any of these describe the work. Finding out early saves both sides time and money.
-
01
The process is generic enough for existing SaaS.
-
02
The process owner cannot stay involved while we build the map.
-
03
You only need a tool, while our work builds the practice around it.
-
04
You need a recommendation deck rather than a working contract. A strategy consultancy is a better fit.
Start with the constraint causing the most friction.
On a 30-minute fit call, we review your answers to three questions and recommend the right engagement. If none fits, we will tell you.