Fractional work

What a part-time tech lead can and cannot do for a project, and how to work that way.

  1. Full remote, freelance: the only team I would hire

    If I had to hire a team tomorrow, it would be freelance and full remote only: that is where the best talent actually is, not within a 30-minute commute.

  2. The first week without writing a line of code

    On any project, greenfield or brownfield, leave the keyboard alone the first week: understand, challenge the architecture, model the business.

  3. My support offer for SMEs that build tools with AI

    AI-built internal tools getting out of control, insecure, fragile? Here is how I help small businesses get them back on track, progressively, at their own pace.

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

    In a few weeks, five near-identical profiles asked me for the same thing: a developer who watches their back, but not full-time. I am making it my job.

  5. The developer market is shifting

    Large dev teams are shrinking because of AI. Meanwhile, small businesses are starting to build their own internal tools and will need experts a few days a month.

  6. Experience-based daily rates no longer measure anything

    Daily rate grids were built on years of experience because the keyboard capped the gap between good and bad developers. With AI, that bottleneck is gone.

  7. Building a product is easy. Distribution is the hard part.

    Developers often forget that building a product depends on them. Selling, onboarding and keeping customers does not. A simple plan for technical founders.

  8. The part-time senior developer: a new freelancing model

    In companies where the product only supports the business, vibe-coding hits a wall fast. A senior developer a few days a month is often enough to lift it.

  9. Full remote freelance, but [CITY] only?

    Requiring a full remote freelancer to live in a given city or country makes no sense. A legal framework or working hours, at a stretch, can.