One senior engineer, accountable end to end. Modern AI tooling does the heavy lifting; fifteen years of shipping by hand - for Johnson & Johnson, GSK, Babbel, Carwow, Citizens Advice - supply the judgment. You get working software at a fixed price, not a burn rate.
Step 1
One week: your idea becomes a spec, an architecture, and a fixed quote.
Step 2
Fixed-scope build
I build the agreed product with visible progress at every milestone, no surprises.
Step 3
Launch & support
Deployed, documented, and supported after it goes live.
Not a build? I also take contract engagements and fractional support. More on the services page.
When we hand Wagner a build with a hard deadline - a congress opening, a live event - it ships. Complete, working, on the floor when the doors open.
Wagner was enjoyable to work with. He was able to quickly get up to speed, immediately wrapping his brain around problems and shipping clear code to fix them.
Wagner handled our blog migration end to end including migrating all content, URLs and redirects for SEO, and a custom Cloudflare Worker. All documented and deployed with zero drama.
Hospital networks that allow nothing in, devices in the field you cannot brick, conformance requirements you cannot negotiate, and stakeholders who need it in plain English. What engineering discipline looks like when the environment sets the rules. From a clinical alerting platform used by NHS trusts and a fielded detection product.
If you run production at an event agency, you know the shape of this problem. The client has bought an interactive idea for their stand. A touchscreen, a photo experience, some kind of engagement measurement. You have sold it, you have a date, and...
"Fixed scope, fixed price" sounds like a line from a brochure until you watch one run from start to finish. So here is one. Last September I built EventScope for Johnson & Johnson Medical: an engagement analytics platform that ran across their...
Most writing about LLMs in Rails apps stops at architecture: RAG, MCP, "AI as a multiplier." The part that actually bites is smaller and more concrete: a model takes eight seconds to answer, and HTTP gives you one response. You either stare at a s...
Get notified when I publish something new, and unsubscribe at any time.
