About
Fifteen years building engineering teams. Now I build the systems that run them.
I'm Piers Rollinson — DoorDash, Square, and Mudflap, then DomeWorks. I work with engineering leaders whose teams are using coding agents but still struggle to get changes through testing, review, and release. My work connects the pieces around those agents: clear requirements, codebase context, verification, and a workflow the team can use and maintain.
Why DomeWorks exists
At Mudflap, the last stop before DomeWorks, I built the agent coding harness our engineering team used to ship faster, built the voice AI in the product, and redesigned how the org used AI day to day. That wasn't a pilot program — it was the workflow a team of engineers actually ran on, and I was the one who built and kept it running.
I watched the same pattern play out at DoorDash and Square before that, just with different tools: leadership buys the licenses, announces them in Slack, maybe runs a lunch-and-learn. Three months later adoption has stalled and nobody can say why.
The tools were never the problem. Nothing connected them to how the team actually worked — no shared context feeding into them, no workflow built around them, no one accountable for making the adoption real. DomeWorks is that missing layer, built by someone who's actually built it before, not sold it.
How I work
You work directly with me
I scope the engagement and work directly with your engineers on the build and its adoption. That includes deciding what to build first, what context agents need, how changes will be tested and reviewed, and how your team will maintain the workflow afterward.
Runs on what it builds
DomeWorks operates as an agent organization: a coordinator triages and routes incoming work, specialists handle the first pass on research and drafting, and a review step gates every output before it reaches me. A one-person studio has a company's worth of coordination, and running it this way is the same pattern I build into client systems — less time relaying and gathering, more time on the work that needs judgment.
Designed to end
Every engagement ships a handoff: documented systems, runbooks, and a session where your team takes over what I built. You own it and can run it without me. If you want ongoing support after that, that's what the AI Ops Partner tier is for — but you're never locked in.
Where this shows up
Proof
The Work collection includes the system I use to run DomeWorks: incoming work is triaged, specialists make a first pass, and a review gate checks the output. It shows our own operations in practice; it is not a client engineering-team result.
If your team is using coding agents but delivery still gets stuck, explore the Eng OS Audit. We trace the delivery constraint, establish a baseline, and choose the first workflow worth improving. You leave with a prioritized roadmap and a priced implementation scope. The audit stands on its own; implementation is a separate decision.