Service: Domain-Driven Process Modeling
ONE WEEK · FIXED SCOPE

Domain-Driven Design, domain modeling, process modeling.

Map the one process that is genuinely yours, in the language your team already uses.

One week. Fixed scope. A five-day workshop that produces a domain map your operators, your engineers, and AI can all read, plus a clear recommendation on what to do next.

Book a fit call
Get a process audit sample

One PDF, no follow-up sequence. We send it once.

Starts from EUR 8k. Single fixed-price engagement; five days, no separate discovery phase.

01
WHO THIS IS FOR

You feel a specific kind of pain.

  • 01 One process in your company is genuinely yours. It does not look like anyone else's.
  • 02 The SaaS you bought does not respect it. Your team works around the tool, not with it.
  • 03 The team knows where it breaks, but nobody has written it down.
  • 04 The founder, CEO, or COO can stay in the room for the engagement.

If three of four ring true, this is the right starting point.

02
WHAT YOU GET

A working contract, not a deck.

Part 01

The domain map

A structured artifact your team can read. Objects, rules, events, actors, constraints; named in your language, not ours.

Part 02

The glossary

Every term your business uses, defined once. Ubiquitous language is the difference between a map your team trusts and a map they argue with.

Part 03

The event catalog

Every state change in the process, with timing, triggers, and side effects. The basis for any automation we (or you) build later.

Part 04

The audit checklist

A reviewable record of the constraints that govern the process: compliance, policy, separation of duties. Reusable when the process changes.

03
HOW THE ENGAGEMENT RUNS

Five days, one map.

One focused week, run as a five-day workshop. We use Domain-Driven Design and EventStorming to map the events, the actors, the decisions, and the boundaries in your language, not in the language of software. Days 1, 3, and 5 are with your team; days 2 and 4 are our synthesis. The process you map is decided in the fit call, so day one starts on real work.

  1. Day 1

    Current process.

    With your team

    The people who do the work walk us through how it actually happens: actors, steps, decisions, tools, exceptions, the workarounds nobody documented, and the costs everyone tolerates. We record and transcribe so the evidence outlives the room. The EventStorming surface fills with the real process, not the official one.

  2. Day 2

    Synthesis.

    With your team

    A working day without you. Transcripts become a verified process list and a first domain model. Screens are extracted; low-fidelity wireframes are drafted as questions for Day 3. AI accelerates this, but every artifact is reviewed by hand before anyone trusts it.

  3. Day 3

    Validation.

    With your team

    The wireframes are a question, not an answer. We test happy paths, edge cases, permissions, data needs, roles, and integrations, and we watch for where the model is wrong. When a wireframe reveals a misunderstanding, it changes live. Where it matters, compliance is in the room and the rules nobody had named get surfaced.

  4. Day 4

    Scope shaping.

    With your team

    Internal again. The validated model becomes a scope view, milestone candidates, a draft roadmap, and a first estimate. A second team challenges scope, feasibility, and assumptions before anything reaches you.

  5. Day 5

    Recommendation.

    With your team

    The owner walks through must-have scope, later scope, explicit non-scope, milestones, trade-offs, and the recommendation: build, partially build, defer, use SaaS, or investigate further. All five are real outcomes. The artifact is yours, with the option to continue onto Process Native Software.

04
THE GRADUATION PATH

What happens when the engagement ends.

You leave with the map, the glossary, the event catalog, and the audit checklist. They are yours; if you never work with us again, they are still load-bearing.

If we do continue, the map becomes the contract Process Native Software is generated from. The same artifact that lived as a PDF for a week is now the source of truth for the software your company runs on. No translation step. No 'now let us build the spec.' The map is the spec.

05
THE MAP
The map is the contract. The software is what the contract generates.

EmpoweredHouse · Domain-Driven Process Modeling

06
PRICING

Starts from EUR 8k.

Single fixed-price engagement for the five-day workshop. No separate discovery phase, no scope creep, no time-and-materials line item. The price is set in the fit call, before you sign.

Process size

People involved, systems touched.

Regulatory weight

Whether a compliance review is needed.

What changes the number: the size of the process (people involved, systems touched) and the regulatory weight (whether a compliance review is needed). The week itself is fixed.

07
THE FIT CALL · 30 MIN

Find out if the map is the right place to start.

A fit call is thirty minutes. If your process is generic, we will say so. If it is not, we will tell you what mapping it would look like.

Book a fit call Get a process audit sample