Services
Umbraco work, done by the person who does it.
Five ways teams typically bring me in, from a brand-new build to a few days a month keeping an existing site healthy.
New builds & integrations
Custom Umbraco sites and headless builds on ASP.NET Core, wired up to whatever the business actually runs on: payment gateways, CRM, ERP, search (Examine or external), marketing automation. I work from Figma or a rough brief equally well, and I'll tell you early if something's better solved outside Umbraco than bent to fit inside it. Includes Umbraco ecommerce and Umbraco Forms work specifically.
Version upgrades & migrations
Umbraco 7 and 8 are long past end of life, and Umbraco 13 follows them in December 2026, which is the single biggest reason teams call me. I plan and run migrations onto Umbraco 17, the current LTS release, preserving content, media, member data and URL structure. I'll say upfront if a rebuild genuinely is the better route for your case, rather than defaulting to the bigger invoice. See the upgrade guide for how this actually works.
Performance & Core Web Vitals
Audits covering server response time, database and Examine index tuning, image delivery, caching, and front-end bloat, with a prioritised list of fixes, not just a Lighthouse score and a shrug. Useful before a marketing push, after a slow migration, or if editors are complaining the backoffice itself has gotten sluggish. See Umbraco SEO for the search-visibility side of this.
Support & Umbraco hosting
A monthly support contract for bug fixes, small enhancements, security patching and editor questions. Priced per engagement, not a fixed package, since a five-page brochure site and a commerce platform need very different amounts of attention. Managed Umbraco hosting is available alongside it for teams that would rather not run their own infrastructure. See pricing for how this is quoted.
Agency overflow & white-label work
A good chunk of my work is subcontracted through other agencies, brought in as extra senior Umbraco capacity for a specific project or a busy quarter, working under your process and, where wanted, under your name to the end client. Most of this work is for Umbraco Platinum Partner agencies specifically. See the clients page for what that involves, or this comparison if you're weighing an agency against an independent developer. If you've got Umbraco work and not enough Umbraco developers, this is usually the fastest path to more capacity without a hiring process. Onboarding your team afterwards is covered by Umbraco training.
How an engagement works
From first email to handover
-
A quick call or email thread
Tell me what you've got and what's not working. I'll ask the boring-but-important questions: current Umbraco version, hosting, rough timeline, budget shape.
-
Scoping & a day-based estimate
For anything beyond a small fix, you get a written scope and an estimate in days, so you know roughly what you're committing to before work starts.
-
Work in the open
Code goes through git with a normal commit history, not a zip file at the end. For anything longer than a few days, you get regular async progress updates.
-
Handover & documentation
Every engagement ends with proper documentation of what changed and why, so your team (or the next developer) isn't reverse-engineering my decisions later.
Not sure which of these fits?
That's normal. Most projects are a mix. Describe what you're dealing with and I'll point you at the right one.