Over 20 years building and maintaining .NET systems for manufacturing, logistics, engineering and software teams. Enterprise systems, automation and high-reliability workflows.
Two ways to work together
Development subscription
- Monthly subscription: I work through your bug fixes, change requests and new features.
- Pause or cancel at any time.
- Money-back guarantee in your first 3 weeks.
Software project
- New systems and legacy modernisation, scoped and priced up front.
- Starts with a business requirements workshop.
- Findings and recommendations: you choose the option.
Simple monthly pricing. No hourly rates. No surprises.
£5,500/month
- Most requests delivered in days, not weeks
- Every change reviewed, tested and documented
- Pay by credit card or bank transfer; payments handled securely by Stripe
- Pause or cancel at any time
- No recruitment process or agency fees
What your place includes
Your place buys my ongoing capacity as a senior .NET developer, not a set number of hours or tickets. I work through your bug fixes, change requests and new features in priority order, on systems built with .NET, SQL Server and Azure. You can see progress in your task tracker as it happens.
It doesn't include out-of-hours or emergency support, or work outside the Microsoft stack.
Not sure yet? Talk it through first.
You want to move faster, so let's go.
Skip the recruiters, the rounds of interviews and the new-starter paperwork, and get straight to work.
-
Subscribe
Secure your place and get direct access to me as your senior developer.
-
Add your requests
Create tasks in GitHub, Azure DevOps, or your preferred tool. I pick them up in priority order.
-
I deliver fast
Most requests ship in days, not weeks. Each one is reviewed, tested and documented before it reaches you.
No contracts
Cancel at any time, with no recruitment process or agency fees.
Use a subscription to fill a gap in your team, or to bridge one until you hire.
No meetings
Communication happens in one place: GitHub, Azure DevOps or the tool you already use.
Everyone can see at a glance what I'm working on and what I've shipped.
You don't need to hold my hand.
Bringing on a new developer is usually slow. You explain how the code is organised, help them get it running on their machine, and answer a steady stream of questions.
I've worked with .NET for almost as long as it has existed, from .NET Framework through to modern .NET, and with classic ASP before that. I get up to speed on an unfamiliar codebase quickly, so you don't have to walk me through it. You can see my track record on LinkedIn.
My aim isn't just to close tickets. It's to leave your system a little better each time.
No compromises on quality.
AI has made code quick to write. These are the practices that make it safe to depend on.
Review and testing
AI can write code in seconds. Knowing whether that code is correct, secure and safe to ship is the part that still takes experience.
Every change I deliver, whether I wrote it myself or an AI tool drafted it, is reviewed by me and backed by automated tests before it reaches you. The tests prove each change does what it should, and keep proving it every time the code changes after that.
There is always a person accountable for what ships. If something I delivered goes wrong, it's mine to fix.
Documentation: you're never locked in
Your system should never depend on one person's memory, including mine.
Work starts from a written spec: a plain-English description of what the system should do. The code and tests are checked against it, and it stays up to date as things change. Alongside it, you get clear commit messages and pull request descriptions that explain what changed and why.
Any developer, or any AI tool, can pick up where I left off. If you pause or cancel, you keep everything: the code, the tests and the knowledge.
Architecture
Long-lived applications tend to build up technical debt over the years. I chip away at it with every feature I work on. It's simply part of how I work.
A clean, consistent structure is easier for your team to work in, and it gets far better results from AI tools too. After a few months, you'll see the difference in the overall quality of your application.
Why not just use AI yourself?
You can, and for plenty of things you should. AI tools are genuinely good at producing code quickly. I use them every day, and they're a big part of why I can deliver in days rather than weeks.
But typing the code was never the hard part. The hard part is:
- Knowing what to build, and what to leave out
- Spotting code that looks right but isn't: the missed edge case, the security gap, the query that slows to a crawl once real data arrives
- Fitting changes into an existing system without breaking what already works
- Keeping the codebase understandable as it grows, instead of piling generated code on top of generated code
- Owning the result when something goes wrong
AI gives you speed. I give you that speed with experience, judgement and accountability behind it.
Running on an older .NET system?
Many businesses depend on systems built years ago: .NET Framework, Web Forms, WCF services, VB.NET, and a SQL Server database that has grown along with the business. They still work, but every change feels risky, and fewer and fewer people know how they fit together.
I've spent over 20 years working on systems like these. Modern AI tools also make it much quicker to read, map and explain a large, older codebase than it used to be, and I check everything they tell me against the code itself.
My approach is steady and low-risk:
- Map what you have, and document how it really works
- Put tests around the behaviour your business relies on, so any change is caught
- Modernise piece by piece, with the system running throughout. No big‑bang rewrite
- Move to modern .NET and Azure at a pace that suits your business
Modernisation can run as part of a subscription, or as a fixed-price project.
Not ready to subscribe? Start with a free health check.
Send me read access to one of your .NET codebases, and I'll send back:
- A clear README explaining what your system does, how it fits together, how to get it running, and where the fragile areas are
- One or two issues worth fixing, explained in plain business terms, with a rough idea of the effort involved
- A short call to talk through what I found
I use AI tools to get through your code quickly (only with your agreement), then check everything myself, so what you get back is accurate.
It's free, with no obligation to subscribe. I take on a small number each month, and I'm happy to sign an NDA first.
Microsoft-stack (.NET / SQL Server) codebases only. Read-only access, removed afterwards. This is a documentation and code-quality review, not a security audit.
Need a new system, or a rebuild of an old one?
A dedicated project gets my full attention, with a clear scope and price agreed up front.
Every project begins with a business requirements workshop, gathering what's needed from across your organisation. That lets me scope and price a set of options, so you can choose the one that fits.
The same standards apply as for the subscription: every change reviewed and tested, and the system documented as it's built. You get the system you need, documented and ready for your own team to take over.
-
Workshop
A session with you and your team to understand what you need.
-
Findings and options
Recommendations with costed options. You decide which way to go.
-
Delivery
Regular updates on what's been delivered and what's in progress.
When am I not the right fit?
This service probably isn't for you if:
- You need daily stand‑ups, long meetings or constant check‑ins
- You need pixel‑perfect front‑end design or heavy UI/UX work
- You want a full‑time developer embedded in your team
- You expect instant responses outside agreed working hours
- You need work in technologies outside the Microsoft stack (.NET, SQL Server, Azure)
Your questions answered.
How many hours do I get each month?
I don't bill by the hour, and I don't track hours. Hourly billing is an inefficient and unpredictable way to work, for both of us.
It's tempting to compare on hourly rates, but that's comparing apples with oranges. More hours don't mean more value, and with AI tools, hours spent are a poorer measure of output than ever.
My focus is on delivering consistently high-quality results, with as little risk to you as possible. Without that high bar, more hours of work just means more code to fix later.
I know hourly billing is the norm in this industry, and this may be a leap you're not yet comfortable with. That's why I offer the money-back guarantee. Try it and see for yourself.
Well then, how many issues will you finish each month?
It's hard to say, because issues vary enormously in size. “Improve validation on our checkout page” is very different from “Build an integration with this third-party API”.
I can't tell you how many issues I'll finish (and it isn't a very useful measure anyway), but I can promise a steady stream of updates and progress from me. No more developers who “go dark” for weeks or months at a time.
Each week, I'll ship something of value to you. Larger pieces of work are split up and delivered in stages, so you see progress early and get consistent value from the subscription.
Can you join our daily stand-up or weekly check-in call?
No. I keep meetings to a minimum; it's a big part of why I can deliver as quickly as I do. My process is fully transparent, so routine check-ins aren't needed.
You'll always be able to see exactly what I'm working on. And if something genuinely needs a conversation, I'll arrange a short call.
I really need to explain something to you though.
That's fine. Context is always welcome, and the more I know about what you'd like built, the better. Write it up in the task, and if anything is still unclear, I'll arrange a brief call.
Can I call you if my site goes down?
I don't offer emergency support; that's best handled by someone on your team. Ideally, for security reasons, I wouldn't have access to your production environment at all.
Do you use AI to write the code?
Yes, where it helps: drafting code, writing tests and getting to grips with unfamiliar code. It's a big part of how I deliver quickly.
Nothing reaches your codebase without my review. I only use AI tools whose terms keep your code private, and if your business has its own AI policy, I'll follow it.
Why Dalriada?
Dalriada was a Gaelic kingdom that spanned the sea between the north-east of Ireland and the west of Scotland, more than 1,500 years ago. The Glens of Antrim, where I live and work, were part of it.
Its people treated the water as a link, not a barrier. I work the same way: your team and I can be hundreds of miles apart and still work closely together.
Want to talk with me first?
Learn more about how I work and how I can help you during a free call.