About
Fifteen years building engineering teams. Now I build the systems that run them.
I'm Piers Rollinson — DoorDash, Square, and Mudflap, then DomeWorks. The problem was always the same: how a team actually ships, not how busy it looks. These days that problem runs through AI, and I build DomeWorks the way I build for clients — on agents, not headcount.
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
Senior attention, not a hand-off
I scope the engagement, build the system, and I'm the one debugging it when something breaks. Most AI consulting sells you a partner and staffs the actual build to a team of juniors you'll never meet. There's no team to hand off to here — you get direct access to the person who's done this before, not a template someone junior is running for the first time.
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
This page is the background. The fuller, more concrete version — what an engagement actually builds, for a client or for DomeWorks itself — is written up at /work/.