Building AI that
answers to you.
EBD Connect Ltd is the team behind Model My Context. We are consultants, engineers and event-modeling practitioners — building the governance layer we kept wishing our clients had.
We have seen this
problem before.
EBD Connect spent years helping organisations turn tangled business processes into event-driven systems. The pattern never changed: the people doing the work understood the rules; the systems executing the work did not.
When large language models arrived, the gap got worse — not better. AI was being asked to guess at policy, procedure and intent, without ever being told what success looked like. Teams wanted governance, not another prompt library.
Model My Context is the answer we built for ourselves first. It takes the event-modeling and CQRS practices we had been teaching for a decade and compiles them into something an AI agent can execute — deterministically, auditably, and inside the customer's own repository.
Who's behind
this work.
Model My Context is led by its founder — who also wrote the methodology it compiles.
Arjan's work bridges the gap between complex data and high-value business results through Outcome-Driven Context Modeling — architecting systems that don't just process information, but transform it into precise, high-fidelity context designed to trigger specific, successful actions.
Model My Context is the product expression of that method: a workbench that maps business environments directly to the outcomes they need to achieve, so AI agents operate with the grounded context required for professional-grade utility — not generic assistance.
- Outcome-Driven Context Modeling — Mapping data structures to specific business goals.
- Context Engineering — Bridging the "context gap" to make AI implementations actionable.
- Event-Driven Architecture — Event modeling, CQRS and event sourcing as the foundation for precise context.
The focus: moving beyond generic AI implementations toward precision-engineered systems defined by the results they produce.
How we think about
AI governance.
These are not marketing slogans — they are the constraints we write code against. If a product decision contradicts one of them, the decision gets reworked.
We model outcomes, not instructions. Describe the result a process should reach and who owns it — the execution layer follows. This is the difference between governing AI and scripting it.
The MCP execution engine is open source. The SKILL.md format is a plain standard. The only thing we keep proprietary is the Workbench — and you can walk away from it without losing your logic.
Human-in-the-loop is not a slogan. Every skill is reviewed, committed and versioned by a person. AI executes within those boundaries — it does not set them.
There is no MMC database holding your business information. Your context models live in your own repository. Procurement already trusts GitHub — we see no reason to ask them to trust us too.
One discipline,
three ways to work with us.
Whether you adopt the product, bring us in to model a process, or commission a bespoke build — the underlying method is the same.
A visual context-modeling Workbench and an open-source MCP execution engine. Turn your existing SOPs, policies and process docs into governed, auditable AI skills — without coding.
See how it works →We help teams translate messy business processes into event-driven context models. Workshops, discovery, and hands-on facilitation rooted in event modeling, CQRS and domain-driven design.
Talk to us →When off-the-shelf does not fit, we build. Event-sourced systems, MCP integrations, and governance platforms — delivered by the same team that wrote the methodology behind them.
Start a conversation →The short version.
Bring us your
hardest process.
Try the Workbench, read the open-source engine, or book a conversation with the team directly — whichever is least friction for you.
© 2026 EBD Connect Ltd · sales@ebdconnect.com