Why I am going all in on the one-day-a-week developer

· Published · 1 min read

In a few weeks, without looking for it, I met five near-identical profiles.

The same profile, five times

  • A bit technical: a developer in another life, a former PM, a jack-of-all-trades entrepreneur, the owner of a small business…
  • Discovered AI over the last six to nine months (hi, Claude).
  • Vibe-coded some pretty impressive things, things I would not have believed possible a year ago…
  • …and saw the limits arrive: incomprehensible bugs, first paying customers with no idea what is behind the product, big security questions, vibe-code quality collapsing.

All of them reached me one way or another: directly, through an introduction, through a message.

And all of them wanted the same thing: a developer who watches their back. But not full-time.

And that is genuinely interesting.

A niche that suddenly makes sense

The “developer one day a week” niche was very rare before. It makes complete sense now that many people move forward without a developer, and the developer becomes a consultant who accompanies them.

So I am going all in on it: supporting those who build without a developer but want a professional who checks in regularly.

What it covers

  • Setting up AI harnesses
  • Regular security and performance checks
  • Technical advice and direction, rather than a yes-man AI
  • Debugging the incomprehensible problems
  • Continuous AI watch, so you stay up to date without spending your evenings on it
  • Sharing good practices between my clients, as long as they are not competitors

In short: twelve years of experience and the fruit of my ongoing research, so that projects can exist and move forward with peace of mind.