Which of these sounds like you?
The work underneath is the same. What changes is how you buy it, who I answer to, and how much of the technical picture I own. Each page covers the situations I get called for, how engagements are structured, and how pricing works.
For Agencies
You have won Umbraco work and you are a senior developer short. I plug into your delivery team, your process and your client's codebase — as extra capacity, as the specialist on the parts nobody else wants, or owning a workstream outright. White-label where that is how you sell.
For Businesses
You own a website or platform, and internally nobody owns the technical side of it. I take that on: requirements, build, integrations, releases and the judgment calls in between — one accountable person instead of a ticket queue.
For Product Teams
You have engineers, just not the Umbraco or .NET depth this particular piece needs. I join the team, work in your stack and your rituals, and own an initiative from discovery through release — not only the tickets handed to me.
Running Umbraco 13? Support ends in 2026.
When support ends, security patches stop. A planned upgrade to Umbraco 17 LTS costs less — and hurts less — than an emergency one. See what your timeline should look like.
Where the difference shows
The quality layer most builds skip: accessibility to WCAG 2.2 AA, Core Web Vitals in the green, semantic markup that survives an audit, and technical SEO built in rather than bolted on afterwards. I deliver the whole stack — Umbraco, .NET, integrations — but this is the part you can see, measure and get sued over.
Umbraco development
New builds, version upgrades, migrations off other systems, and taking over sites someone else built and walked away from. Umbraco since 2013, currently shipping on v17.
Full-stack .NET development
The parts that are not the CMS: APIs, integrations, background jobs, data models and the architecture holding it together. .NET since 2008 — longer than the Umbraco work, and it shows in how the systems are put together.
Maintenance & retainers
Reserved senior hours every month: upgrades, security patches, smaller features, and someone who already knows the codebase at the moment something breaks. My longest engagements started as a project and stayed as a retainer.
Two things most developers hand off
I do not. Both decide whether the build earns anything, and both are technical problems before they are marketing ones.
Technical SEO & performance
Crawl health, Core Web Vitals, structured data, multilingual setup and migration redirects. Most of what damages a site's search performance is a build decision — which is why I would rather own it than audit someone else's.
Email marketing & retention
Segmentation, lifecycle automation, tracking and the integrations feeding them. This started at an email marketing SaaS and turned into campaign operations and data work for clients including eBay and CDON. The technical half of retention, not the copywriting.
The platform underneath the work
Rather than rebuild the same foundation on every project, I maintain one: an Umbraco platform with SEO, accessibility and performance defaults already in place, built against WCAG 2.2 AA principles. My own client work runs on it, and it is licensed separately for agencies and developers who want the same starting point.
Not sure which of these you need?
Describe what is actually happening — the deadline you are going to miss, the site nobody can safely touch, the developer you cannot hire in time — and I will tell you whether it is something I should take on. If it is not, I usually know who should.