DomeWorks · Eng OS Audit
Find the first workflow worth building.
Start building your software factory with a clear plan. We find what is slowing delivery, choose the first workflow worth improving, and scope the work to build it into your codebase and your team's day-to-day delivery—with quality and model costs in view.
$5–15k · fixed scope
01 · Where delivery gets stuck
Find what needs to change around the agents
Your team may already be writing code faster with agents. Getting that work into production depends on clear requirements, the right context, working test environments, and review that catches what matters.
The audit traces real work through that whole process. It is for engineering leaders at product and SaaS teams of about 10–50 engineers, and services companies scaling agent-assisted delivery. We identify the constraint and decide what is worth building first.
- Small product changes wait weeks to reach production
- Agents miss requirements or decisions buried in the codebase
- Reviews and manual testing absorb the time saved writing code
- The setup works for one engineer but has not spread across the team
- Model usage is growing, but the cost of accepted work is unclear
02 · How the audit works
Trace the work. Choose a workflow. Scope the build.
01 · Diagnose
Follow real tasks through delivery
Review recent work with the people who plan, build, review, and release it. Look at where context goes missing, work waits, tests fall short, or retries add cost.
02 · Prioritize
Choose a useful first workflow
Select a bounded piece of delivery work where a software factory could help. Define what success looks like and identify prerequisites, such as a reliable local environment or better tests, that need to come first.
03 · Scope
Plan the build and adoption
Specify the context, agent workflow, model choices, and review gates. Agree who will own the system, how engineers will learn to use it, and the scope and price of a sprint.
03 · What you leave with
A plan your team can act on
Delivery diagnosis and baseline
A map of how work moves today, the constraint to address, and a baseline to compare against. Gaps in the available data are made explicit.
First workflow and acceptance criteria
A recommendation for where to start, why it comes first, and how you will judge whether it works. The roadmap includes the foundations needed before agents can use it reliably.
Technical and team adoption plan
The proposed context, tools, model choices, testing, and review boundaries, alongside team responsibilities and the working sessions needed to put the workflow into use.
Priced build scope
A Software Factory Sprint scope with deliverables, timeline, team involvement, and a fixed price. You can commission the sprint or take the plan forward with your own team.
04 · Establish the baseline
Know what to compare after the changes
We baseline these measures from your GitHub/Linear data, reviewing available model usage and retries alongside them. We rerun the measures 30 days after the initial audit baseline. This is one shared checkpoint for the audit and any sprint work underway. The follow-up is included in the audit, whether or not you commission a sprint.
The numbers sit alongside examples of accepted work, rework, and the checks used before release. Together, they help you decide whether the changes are making delivery faster without creating more review work or avoidable cost.
05 · From audit to implementation
Build the workflow. Help the team adopt it.
The Software Factory Sprint turns the agreed plan into a working system in your repo and CI. We connect agent implementation, testing, and review, then work alongside your engineers on real tasks so the workflow becomes part of everyday delivery.
You work directly with Piers Rollinson, drawing on 15 years building and leading engineering teams at DoorDash, Square, and Mudflap. That experience informs both the audit and the build: what to tackle first, what agents need, and where human judgment belongs.
Explore the Software Factory Sprint →
The audit stands on its own. You keep the findings, roadmap, and build scope whether or not you choose DomeWorks for implementation.
FAQ
Before you book
Who is the Eng OS Audit for?
Engineering leaders at product and SaaS teams of about 10–50 engineers, and services companies scaling agent-assisted delivery.
What do we leave with?
A map of the delivery constraint, a baseline of delivery and cost measures, a recommended first workflow, and a priced Software Factory Sprint scope. The plan covers context, environments, testing, review, model choices, and what your team needs to adopt and own the workflow.
How much does it cost?
The Eng OS Audit is $5–15k, fixed scope. We agree the questions, evidence, timeline, and team involvement before starting. Any build work is scoped and priced separately.
What do we need to provide?
Relevant GitHub/Linear data, examples of recent work, and time with the people who plan, build, review, and release it. We also review the agreed codebase context, development and test setup, and available model-usage data. Access and time commitments are agreed in the scope.
Does the audit include building the software factory?
The audit defines what to build and how to put it into use. Implementation and team adoption happen in a separately scoped Software Factory Sprint. You can also take the audit findings and proceed with your own team; there is no obligation to commission the sprint.
We already use coding agents. Is this still useful?
Yes. We examine how work moves around the agents: requirements, context, development environments, testing, review, and release. The audit identifies which missing connections or team practices are holding delivery back and which are worth addressing first.
How do you assess quality and model costs?
We review accepted changes, rework, testing and review practices, and available model usage and retry data. We establish the delivery baseline and identify gaps in the evidence. Model recommendations account for the work each stage needs to do and the review effort it creates.
What happens at 30 days?
We rerun the measures 30 days after the initial audit baseline. This is one shared checkpoint for the audit and any sprint work underway, included in the audit whether or not you commission a sprint. We review progress at that point; it is not a separate review 30 days after the sprint ends.
Does the plan require Patina?
No. Patina is an optional context product, priced separately at $149/month per workspace. We plan around your codebase and tools; your software factory can run without a Patina subscription.
Eng OS Audit · $5–15k
Bring the work your team is struggling to ship.
In a 30-minute call, we will talk through where delivery gets stuck and whether the Eng OS Audit is the right starting point for your software factory.