The domain map
A readable structure of the objects, rules, events, actors, and constraints, all named in your team's language.
Domain-Driven Design, domain modeling, process modeling.
In a fixed five-day workshop, we create a domain map for the people who run the process and the engineers or AI systems that support it. You also get our recommendation on whether to build, defer, use SaaS, or investigate further.
Starts from EUR 8k for a fixed five-day engagement. Discovery is included in the price.
When three apply, process mapping is the right starting point.
A readable structure of the objects, rules, events, actors, and constraints, all named in your team's language.
A single definition for every business term, so the team can use and trust the same language.
A record of each state change, including its timing, triggers, and side effects. It is the basis for later automation, whether we build it or your team does.
A record your team can review when the process changes. It covers the compliance requirements, policies, and separation of duties that govern the work.
The workshop runs over five days. We use Domain-Driven Design and EventStorming to map your process in the language of the business. Your team joins us on days 1, 3, and 5. We spend days 2 and 4 analyzing the work and preparing the next session. We agree on the process during the fit call, which lets us begin with real work on day one.
The people who do the work show us what happens, including the decisions, exceptions, tools, and undocumented workarounds. We also identify costs the business has learned to tolerate. We record and transcribe the session, then use EventStorming to capture the process as it operates today.
While your team returns to work, we turn the transcripts into a verified process list and first domain model. We extract screens and draft low-fidelity wireframes for your team to test on Day 3. AI speeds up this work. A person reviews every artifact before it reaches you.
Your team uses the wireframes to test the model against routine work, edge cases, permissions, data, roles, and integrations. We revise any misunderstanding during the session. When compliance affects the process, the relevant people join us to name the governing rules.
We turn the validated model into a scope view with candidate milestones, a draft roadmap, and an initial estimate. A second team reviews the scope, feasibility, and assumptions before we present it.
The owner reviews the must-have and later scope, excluded work, milestones, trade-offs, and our recommendation. We may recommend building all or part of the process, deferring it, using SaaS, or investigating further. You keep every artifact and can choose whether to continue with the PNS Method and EHOS.
At the end of the week, you own the map, glossary, event catalog, and audit checklist. You can use them without any further work from us.
If you continue, the PNS Method turns the map into a business-readable implementation contract. EHOS governs execution and evidence for the software your company owns.
The map is the contract. The software is what the contract generates.
EmpoweredHouse / Domain-Driven Process Modeling
The five-day workshop is one fixed-price engagement. Discovery is included, and the work stays within the scope agreed during the fit call. We set the price before you sign.
People involved, systems touched.
Whether a compliance review is needed.
We set the final number from the process size and regulatory weight. The workshop remains one week.
We assess whether it is distinctive enough to map and explain how we would run the workshop.