Paul HJ Logan

Hire a top-class

full-stack Microsoft.NET developer

without the hassle of going through the recruitment process.

Development Subscription

Monthly subscription.

I get to work on your issues, change requests and new features.

Pause or Cancel your subscription at any time.

Money-back guarantee.

You want to move faster, so let's go!

Skip the recruiters, rounds of interviews, new employee paperwork and get right to the fun part: shipping.

Set up a Subscribption and invite me to your GitHub or Azure DevOps organisation

Create a project and start lining up issues for me

I get to work and submit a PR in hours/days (not weeks/months)

I keep it simple

No contracts

Payments made with Stripe, the global payment processing platform.

Cancel at any time.

No recruitment process or agency fees.

No tough redundancy decisions.

No meetings

Communication is streamlined and centralized in GitHub / Azure.

Everyone can see at a glance what I'm working on and what I've shipped.

Have a slow month, or going on holiday?

Pause the subscription, use the rest of your paused month when you return.

I'll even send you a reminder 5 days before renewal to make sure you really want to renew.

You don't need to hold my hands.

Bringing on a new dev can be a pretty slow process. Explain how the code is organized. Make sure they can get it running on their machine. Answer a bunch of questions.

I've been working with .Net for almost as long as it has been around - Classic, Framework and Core. I know the technology side of things inside and out.

Take a look at my LinkedIn profile here.

My aim isn't just to close tickets, but to improve the overall project each time.

No compromises on quality.

I've built up practices over the years that help me ship higher quality code.

Testing

Tests are one of the ultimate quality tools.

They give the confidence to make changes and refactor code without fear of breaking the system.

They are also one of the best ways to document how the code works and how to use it.

My code will come with tests.

And I'll add in the pieces that make testing easier, like factories and other test helpers. Your team might just pick up on what I'm doing and start writing tests for their code too.

Documentation

A project without a README is like a ship without a compass.

I'll create an onboarding README if none exists, which future devs who join your team will benefit from.

Anything new I build will be internally documented, and higher level docs will be created as needed.

Commit messages will be descriptive and pull requests will have detailed descriptions.

Architecture

It's common for teams to build up technical debt over the years in a long-lived application.

I chip away at that technical debt with every feature I work on. It's just part of how I work.

I believe in “leaving something a little better than how I found it”.

After a few months of working with me, this will really pay off in the overall quality of your application.

Hiring an expert costs less than you might think.

£5,500/month

Turnaround time in days, not weeks
Pay by credit card or bank transfer
Pause or cancel anytime in less than a minute

Subscribe Now

Want to talk with me first?

Learn more about how I work and how I can help you during a free call.

Unsure? Let's remove all risk for you.

Within the first 3 weeks of your initial month, if you're not completely satisfied for any reason, just let me know, and I will refund your fee and cancel your subscription. That's something you wouldn't get from a full-time employee or some random freelancer.

Why might I not be a good choice?

Let's be honest, this way of working isn't for everyone. If you really need your developers to be in meetings, or you need to have invoices with line items and hourly breakdowns, I'm not a good fit.

Also, while I'm amazing at C#, SQL and JavaScript development and other pieces of the Microsoft / Azure ecosystem, I can't know everything.

If you're looking for help with React, Angular or other front-end frameworks, for example, I'm not a good fit.

Your questions answered.

How many hours do I get each month?

I don't bill by the hour, and I don't track hours. I find it to be a very inefficient and unpredictable way of working with clients.

You might find some freelancer on Upwork for £20/hour and think "I could hire them at the same price and get 200 hours of work!" But that's like comparing apples to oranges.

My focus is on delivering results at a consistently high level of quality and as little risk to you as possible. Without that high bar of quality, more hours of work just means more code to fix in the future.

I know hourly billing is entrenched in this industry, and this may require a mental leap you're not yet comfortable with. That's why I offer the money-back guarantee. Try it out and see for yourself.

Well then, how many issues will you finish each month?

This is a tough one to answer because issues can be of wildly different complexities. “Improve validation on our checkout page” is much different than “Build an integration with this third-party API”.

While I can't tell you how many issues I'll finish (and that's not really an interesting metric anyway), I can guarantee that you will get a steady stream of updates and progress from us. No more dealing with developers that “go dark” for weeks or months at a time.

Each week I will ship something of value to you. Larger issues will be split and delivered progressively to improve communication and collaboration, and to make sure you are getting consistent value out of our relationship.

But what about a weekly check-in call?

As with the daily stand-up, the answer is also "no". I've streamlined my process and made it completely transparent, so routine communication and check-ins are unnecessary. It's better this way!

I really need to explain something to you though.

Totally fine! I love context and knowing more about what you'd like us to build. If something is still unclear, I'll set up a brief chat as needed.

Can I call you if my site goes down?

I'm not able to offer emergency support, and it's probably better for someone on your team to handle it. Ideally, for security reasons, I wouldn't even have access to your production environment.