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. 1 Scope engagement Engagement ManagerEngagement.Scope
  2. 2 Assign team Resource ManagerStaffingPlan.Assign
    • No staffing before signed scope
    • Allocation is resource managements
  3. 3 Produce deliverables Delivery LeadDeliverable.Submit
  4. 4 Approve time Engagement ManagerTimeEntry.Approve
    • Time approved by the engagement
  5. 5 Issue invoice Billing SpecialistInvoice.Issue
    • Only approved time is billed
    • Billing is separate from delivery
  6. 6 Close engagement Engagement ManagerEngagement.Close

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.

  1. 1
    Scope engagement
    Agree the work, the fee basis, and what acceptance means before anyone is staffed.
    Engagement ManagerEngagement.Scope
  2. 2
    Assign team
    Staff to the shape of the work, against real bench availability.
    Resource ManagerStaffingPlan.Assign
  3. 3
    Produce deliverables
    Draft, review internally, and submit each deliverable for client acceptance.
    Delivery LeadDeliverable.Submit
  4. 4
    Approve time
    Review booked hours against the plan; approve what is billable.
    Engagement ManagerTimeEntry.Approve
  5. 5
    Issue invoice
    Bill approved time or the reached milestone, and send it.
    Billing SpecialistInvoice.Issue
  6. 6
    Close engagement
    Confirm final acceptance, release the team, and close the code.
    Engagement ManagerEngagement.Close

Owned end to end by Managing Principal.

SOP / runbook

The same process as a numbered operating procedure.

PurposeScope through invoice — the loop a services firm repeats on every client.
OwnerManaging Principal
TriggerA signed statement of work arrives.
  1. 1. Scope engagement
    Agree the work, the fee basis, and what acceptance means before anyone is staffed.
    Performed by Engagement Manager
  2. 2. Assign team
    Staff to the shape of the work, against real bench availability.
    Performed by Resource Manager
  3. 3. Produce deliverables
    Draft, review internally, and submit each deliverable for client acceptance.
    Performed by Delivery Lead
  4. 4. Approve time
    Review booked hours against the plan; approve what is billable.
    Performed by Engagement Manager
  5. 5. Issue invoice
    Bill approved time or the reached milestone, and send it.
    Performed by Billing Specialist
  6. 6. Close engagement
    Confirm 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 Principal
    Accountable for the practice, its margin, and its client relationships.
    • Engagement Manager
      Runs one engagement day to day.
      Scope engagementApprove timeClose engagement
      • Delivery Lead
        Owns the deliverables and their quality.
        Produce deliverables
    • Resource Manager
      Owns the bench, allocations, and utilisation.
      Assign team
    • Billing Specialist
      Turns 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.

StepManaging PrincipalEngagement ManagerResource ManagerDelivery LeadBilling Specialist
Scope engagementAR
Assign teamACR
Produce deliverablesACR
Approve timeARC
Issue invoiceAR
Close engagementARC

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.

    StaffingPlan.Assign
  • Only approved time is billed condition

    An invoice can only carry hours an engagement manager has already approved.

    Invoice.Issue
  • Allocation is resource managements access

    One bench, one allocator — otherwise every engagement staffs itself and utilisation is fiction.

    StaffingPlan.Assign Resource ManagerManaging Principal
  • Time approved by the engagement access

    The person answerable for the budget approves the hours charged to it.

    TimeEntry.Approve Engagement ManagerManaging Principal
  • Billing is separate from delivery access

    The team doing the work does not raise its own invoices.

    Invoice.Issue Billing SpecialistManaging Principal

Product

What gets built on top of it — the data, the screens, the API.

Data model

The entities, their fields, and how they relate.

Engagement ScopeCloseList

One 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
Staffing Plan Assign

Who is on the engagement, in what role, at what allocation.

  • allocation number required
  • utilizationTarget number
  • startsOn date required
  • endsOn date
Deliverable SubmitList

A named output the client accepts or rejects.

  • title string required
  • dueOn date required
  • state enum required drafting · in-review · submitted · accepted · rework
Time Entry Approve

Hours booked against an engagement, by person and date.

  • hours number required
  • workedOn date required
  • billable boolean required
Invoice Issue

A 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
Engagement Portfolio 🔒
Engagement portfolio.
Engagement tablesummary
/staffing
Staffing Board 🔒
Staffing board.
Staffing Plan formactions
/deliverables
Deliverable Tracker 🔒
Deliverable tracker.
Deliverable table
/billing
Billing Run 🔒
Billing run.
Invoice actions

Example UI

A working admin table and detail form, built from the fields.

Engagement Portfolio ScopeClose
CodeClientFee basisManagerStatus
ARD-114Trellis Healthfixed-feeP. Nwosuactive
ARD-115Grantham Railtime-and-materialsL. Farrowstaffing
ARD-116Vela EnergyretainerP. Nwosuactive
ARD-109Bright Harbor Trustfixed-feeD. Satoclosing
Engagement detail

API surface

The endpoints, grouped by namespace, with their operations.

Delivery/api/delivery

Engagement, staffing, deliverable, and billing operations.

  • GET /api/delivery/engagements Engagement.List The portfolio by status.
  • POST /api/delivery/engagements Engagement.Scope Open and scope an engagement.
  • GET /api/delivery/engagements/{id}/staffing StaffingPlan.Read Current allocation.
  • POST /api/delivery/staffing StaffingPlan.Assign Commit people to an engagement.
  • GET /api/delivery/deliverables Deliverable.List Deliverables and their state.
  • POST /api/delivery/time/{id}/approve TimeEntry.Approve Approve booked time.
  • POST /api/delivery/invoices Invoice.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.

DeliveryWeb
nextjs 15
Portfolio, staffing, and deliverable surfaces.
ArdentConsulting.Product.Web
EngagementService
nestjs 10
Engagements, scope, and closure.
ArdentConsulting.Product.Api
StaffingService
nestjs 10
Bench, allocations, and utilisation.
ArdentConsulting.Product.Api
BillingWorker
express 4
Runs the approve-then-bill sequence at period end.
ArdentConsulting.Operational
DeliveryDb
postgres 16
Engagements, plans, deliverables, time, invoices.
ArdentConsulting.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.

dev
Sample engagements.
Providers
GoogleCloudcloudCloudSqldatabase
Cells
none
staging
Billing rehearsal before month end.
Providers
GoogleCloudcloudCloudSqldatabaseOneLoginauth
Cells
none
prod
Live delivery and billing.
Providers
GoogleCloudcloudCloudSqldatabaseOneLoginauthOpenAirother
Cells
DeliveryWebEngagementServiceStaffingServiceBillingWorkerDeliveryDb

Access-control matrix

Which role may perform which operation, derived not declared.

OperationManaging PrincipalEngagement ManagerResource ManagerDelivery LeadBilling Specialist
StaffingPlan.AssignAllocation is resource managements✓✓
TimeEntry.ApproveTime approved by the engagement✓✓
Invoice.IssueBilling is separate from delivery✓✓
No access rule governs
Engagement.ScopeEngagement.CloseEngagement.ListStaffingPlan.ReadDeliverable.SubmitDeliverable.List

Derived, 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. 1. Download the template

    The compiled genome as JSON: every role, step, rule, resource, screen and system on this page.

    Download Ardent Consulting as JSON
  2. 2. 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. 3. Join the waitlist

    The hosted product runs your model for your team and your agents.

Which of these sounds like you? Pick as many as apply.

The most useful box on this page. Rough is fine, and “nowhere, honestly” is a real answer and a common one.

We reply by hand, usually within a day. No sequence, no drip, no spam.