PlaygroundProfessional services
Ardent Consulting
Fictional companyProfessional services
A professional services firm running scoping, staffing, delivery, and billing across concurrent client engagements.
Modeled on
- PMBOK: Work breakdown structure, scope baseline, and change control.
- Statement of Work conventions: Fee basis, acceptance criteria, change orders.
- Services performance metrics: Utilisation, realisation, and work in progress.
The genome map
Roles in their reporting line, the process step by step with the role on each step, the rules on the steps they govern, and the resources the work acts on. Select a role to see what it reaches.
Roles Select a role to see its reach.
Engagement Delivery Operated by Managing Principal
Scope through invoice — the loop a services firm repeats on every client.
- 1 Scope engagement
- 2 Assign team
- No staffing before signed scope
- Allocation is resource managements
- 3 Produce deliverables
- 4 Approve time
- Time approved by the engagement
- 5 Issue invoice
- Only approved time is billed
- Billing is separate from delivery
- 6 Close engagement
Resources
- Engagement
- Staffing Plan
- Deliverable
- Time Entry
- Invoice
Three questions this genome answers
Each answer comes from the compiled genome alone. Pick another subject and the answer changes in place.
Managing Principal, Billing Specialist may perform Invoice.Issue. The rule: Only approved time is billed; Billing is separate from delivery.
These steps wait for Engagement Manager:
- Scope engagement Engagement Delivery
- Approve time Engagement Delivery
- Close engagement Engagement Delivery
Engagement Manager act on Engagement, by a process step or under an access rule.
Every artifact from one genome
The same derivations and renderers the Playground runs, here for Ardent Consulting at build time. Open it in the Playground to pick your own set.
Operations
How the work actually runs — who owns what, in what order, under which rules.
Process flow
The end-to-end sequence, each step with its owner.
Scope through invoice — the loop a services firm repeats on every client.
- 1Scope engagementAgree the work, the fee basis, and what acceptance means before anyone is staffed.
- 2Assign teamStaff to the shape of the work, against real bench availability.
- 3Produce deliverablesDraft, review internally, and submit each deliverable for client acceptance.
- 4Approve timeReview booked hours against the plan; approve what is billable.
- 5Issue invoiceBill approved time or the reached milestone, and send it.
- 6Close engagementConfirm final acceptance, release the team, and close the code.
Owned end to end by Managing Principal.
SOP / runbook
The same process as a numbered operating procedure.
- 1. Scope engagementAgree the work, the fee basis, and what acceptance means before anyone is staffed.Performed by Engagement Manager
- 2. Assign teamStaff to the shape of the work, against real bench availability.Performed by Resource Manager
- 3. Produce deliverablesDraft, review internally, and submit each deliverable for client acceptance.Performed by Delivery Lead
- 4. Approve timeReview booked hours against the plan; approve what is billable.Performed by Engagement Manager
- 5. Issue invoiceBill approved time or the reached milestone, and send it.Performed by Billing Specialist
- 6. Close engagementConfirm final acceptance, release the team, and close the code.Performed by Engagement Manager
Key positions
The roles this operation needs and who reports to whom.
Delivery Team
- Managing PrincipalAccountable for the practice, its margin, and its client relationships.
- Engagement ManagerRuns one engagement day to day.Scope engagementApprove timeClose engagement
- Delivery LeadOwns the deliverables and their quality.Produce deliverables
- Resource ManagerOwns the bench, allocations, and utilisation.Assign team
- Billing SpecialistTurns approved time into issued invoices.Issue invoice
Each chip is a step of the process that role owns.
RACI matrix
Every step against every role — responsible, accountable, consulted.
| Step | Managing Principal | Engagement Manager | Resource Manager | Delivery Lead | Billing Specialist |
|---|---|---|---|---|---|
| Scope engagement | A | R | |||
| Assign team | A | C | R | ||
| Produce deliverables | A | C | R | ||
| Approve time | A | R | C | ||
| Issue invoice | A | R | |||
| Close engagement | A | R | C |
R responsible · A accountable · C consulted — derived from step owners, the process operator, and access rules.
Policies & rules
The constraints that govern each operation, stated as rules.
- No staffing before signed scope condition
Nobody is allocated until the scope and fee basis are agreed — the cause of most write-offs.
- Only approved time is billed condition
An invoice can only carry hours an engagement manager has already approved.
- Allocation is resource managements access
One bench, one allocator — otherwise every engagement staffs itself and utilisation is fiction.
- Time approved by the engagement access
The person answerable for the budget approves the hours charged to it.
- Billing is separate from delivery access
The team doing the work does not raise its own invoices.
Product
What gets built on top of it — the data, the screens, the API.
Data model
The entities, their fields, and how they relate.
ScopeCloseListOne contracted piece of client work, with its scope, fee basis, and dates.
- code string required
- client string required
- feeBasis enum required fixed-fee · time-and-materials · retainer
- wbsCode string
- realizationRate number
- status enum required scoping · staffing · active · closing · closed
AssignWho is on the engagement, in what role, at what allocation.
- allocation number required
- utilizationTarget number
- startsOn date required
- endsOn date
SubmitListA named output the client accepts or rejects.
- title string required
- dueOn date required
- state enum required drafting · in-review · submitted · accepted · rework
ApproveHours booked against an engagement, by person and date.
- hours number required
- workedOn date required
- billable boolean required
IssueA billing document raised against approved time or a fixed-fee milestone.
- amount number required
- period string required
- state enum required draft · issued · paid · disputed
Screen map
Every route and the page it resolves to.
Shell: DeliveryShell
/engagements/staffing/deliverables/billingExample UI
A working admin table and detail form, built from the fields.
| Code | Client | Fee basis | Manager | Status |
|---|---|---|---|---|
| ARD-114 | Trellis Health | fixed-fee | P. Nwosu | active |
| ARD-115 | Grantham Rail | time-and-materials | L. Farrow | staffing |
| ARD-116 | Vela Energy | retainer | P. Nwosu | active |
| ARD-109 | Bright Harbor Trust | fixed-fee | D. Sato | closing |
API surface
The endpoints, grouped by namespace, with their operations.
/api/deliveryEngagement, staffing, deliverable, and billing operations.
- GET
/api/delivery/engagementsEngagement.List The portfolio by status. - POST
/api/delivery/engagementsEngagement.Scope Open and scope an engagement. - GET
/api/delivery/engagements/{id}/staffingStaffingPlan.Read Current allocation. - POST
/api/delivery/staffingStaffingPlan.Assign Commit people to an engagement. - GET
/api/delivery/deliverablesDeliverable.List Deliverables and their state. - POST
/api/delivery/time/{id}/approveTimeEntry.Approve Approve booked time. - POST
/api/delivery/invoicesInvoice.Issue Issue an invoice.
Technology
Where it runs and who can reach it.
Architecture diagram
The cells this runs on and what talks to what.
ArdentConsulting.Product.WebArdentConsulting.Product.ApiArdentConsulting.Product.ApiArdentConsulting.OperationalArdentConsulting.Product.Core- DeliveryWeb → EngagementService portfolio
- DeliveryWeb → StaffingService allocations
- EngagementService → StaffingService scope agreed
- EngagementService → BillingWorker time.approved
- BillingWorker → DeliveryDb depends-on
- EngagementService → DeliveryDb depends-on
Environment topology
Dev, staging, and production, with the providers behind each.
Access-control matrix
Which role may perform which operation, derived not declared.
| Operation | Managing Principal | Engagement Manager | Resource Manager | Delivery Lead | Billing Specialist |
|---|---|---|---|---|---|
StaffingPlan.AssignAllocation is resource managements | ✓ | ✓ | |||
TimeEntry.ApproveTime approved by the engagement | ✓ | ✓ | |||
Invoice.IssueBilling is separate from delivery | ✓ | ✓ |
Engagement.ScopeEngagement.CloseEngagement.ListStaffingPlan.ReadDeliverable.SubmitDeliverable.ListDerived, not declared — this is the list an audit asks about.
Make yours
Start from Ardent Consulting and change what differs, or pick another company as your template. Three ways in:
1. Download the template
The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.
Download Ardent Consulting as JSON2. Start an agent from it
Paste this into an agent that has the DNA MCP server connected. It drafts your model in the conversation and saves only when you ask.
Use the DNA MCP server (https://agents.dna.codes) to help me model how my company works. Start from the Ardent Consulting genome at https://dna.codes/genome/professional.json. It is an example company, not mine. Read its roles, process steps, rules and resources, then ask me how my company differs. Draft my company's operating model in this conversation, as structure/v1 and behaviour/v1 documents, and use `validate` on each draft. Do not save anything: call `apply` only when I ask you to save.
3. Join the waitlist
The hosted product runs your model for your team and your agents.