For consulting partners

01

You know more than you can sell

Your team has done it before. The payments domain, the claims process, the order lifecycle — you know where the edge cases hide. Your architects have a service blueprint they trust, and a way of structuring code they’ve refined over years.

And yet every new engagement starts the same way: a discovery workshop, a whiteboard, a blank repository. The knowledge is real, but it lives in senior people’s heads, in slide decks and in old projects. AI assistants don’t change that — they don’t know your way of doing things, so they invent their own.

Knowledge in heads

Your best domain and architecture know-how leaves the project when your seniors do.

Re-discovered every time

The same domain gets modelled again, and the same patterns get rebuilt again, for every client.

Revenue tied to hours

What you know can only be sold as more of your people’s time.

02

Two kinds of knowledge, both packaged

Patterns as code

Your blueprints, run — not reinterpreted

A design pattern written in English is something an AI has to guess at, differently each time. In M1Spec your architects express a pattern as an Nx generator, in your own pattern repository. The agent runs your generator for the structure and spends its reasoning on the client’s business logic.

Example: your service blueprint as a generator

nx g @yourfirm/service-blueprint:command \
  --name=SubmitClaim \
  --service=claims

03

How an engagement changes

Package once. Capture a domain you know and a pattern set you trust — the domain language, key stories, and your generators.
Start from your packages. The client project begins with a working domain model and your blueprints, not a blank page.
Tailor with the client. Their people tell their stories in their own words; M1Spec turns them into an event model, an API contract, a backlog and tests.
Build with your patterns. The M1Spec agent builds in the client’s repository with their coding assistant — using your generators — and opens a pull request for each plan.
Leave a living model behind. The client keeps a model of their system that stays in step with their code. You keep packages that are better for the next client.

04

What you gain

Faster engagements

Every project starts from what you already know, so your team spends its time on what is new for this client.

A product of your own

Packaged domains and patterns can be reused and offered again and again — a revenue stream beyond hours. Commercial packaging and distribution are on our roadmap, shaped with our design partners.

A sharper pitch

“We arrive with a working domain model and executable patterns on day one” wins against “we’ll start with discovery”.

Proof in numbers

Built-in time and cost tracking per engagement is on our roadmap, so you can show clients exactly how much faster you deliver.

Open by design: our own example packages live in the open OpenBusinessSpec repository, so you can see exactly what a packaged domain looks like.