CASE STUDY · BUILT WITH KEEL · PUBLIC SOURCE

DynoInvoice

A multi-tenant invoicing and e-invoicing system, built by AI agents under Keel's governance — and published on GitHub so anyone can study how it was built. Non-commercial use only.

View on GitHub Trace any commit on dynokore.dev

[N]requirements

[N]acceptance criteria

[N]tasks completed

[N]%criteria with named passing tests

[N]review rounds per task, average

$[N]model cost per task

All figures pulled from Keel's records on [DATE]. Definitions on dynokore.dev.

THE BRIEF

A regulated system, not a demo.

[Two or three sentences on scope: who uses DynoInvoice, which invoicing and e-invoicing obligations it covers, and what makes it enterprise-grade — multi-tenancy, audit trail, compliance rules.]

We chose a system where mistakes are expensive on purpose. DynoInvoice is our first Dyno system; the same method will carry the CRM, HRMS and other systems on our roadmap.

WHO DID WHAT

Stated plainly, counted from the record.

People

Set direction and priorities — [N] decisions
Approved expected test values — [N] approvals
Approved rules and architecture decisions — [N]

Agents

Drafted and evaluated requirements — [N]
Designed test scenarios and cases — [N]
Wrote, reviewed and merged code — [N] merge requests

WHAT THE GATES CAUGHT

The honest part.

Governance earns its keep when it stops something. A few real examples from the record:

[ID][What was attempted, which gate stopped it, and how it was resolved.]

DynoInvoice is still being built.

It goes on sale when it's finished. Leave your email and we'll tell you when it's available.

Want a system built this way — or to build this way yourself?

Dyno systems for your business, or Keel and our advisory for your team.

Talk to us Keel early access