Services · How I help
3 ways to work together.
Independent work runs part-time, outside my core hours at Strapi, and is fixed-scope or advisory rather than embedded full-time. Every engagement is scoped up front so you know what you receive and where it ends. Public sector, GLAM and enterprise are where most of it has been delivered. It all starts with a free 30-minute call.
Performance & Architecture Rescue
Your Strapi build is slow, fragile, or about to launch and you're not confident. I find out why, prove it, and tell you what to change first.
Teams weeks from launch, or live and firefighting.
- Diagnosis across API, database and frontend
- Verified causes, with the evidence
- Fixes in the order I'd make them
If the fix is a week's work, we agree a remediation phase and I do it. If it's six months of architectural debt, you'll know before spending anything more. The findings are yours either way.
Build & Migration
Technical ownership of the parts of a headless build that are expensive to get wrong: the content model, the migration, the integration seams, the launch. Your engineers do the volume. I own the hard decisions and review the rest.
Organisations with their own frontend engineers replacing a legacy CMS or standing up a new headless platform.
- Content model your team can explain
- A rehearsed migration
- Launch checklist, decisions written down
You keep the model, the code and the decision record. When it's over, your team runs it. Quarterly reviews if you want them.
Fractional Technical Lead
Senior technical direction for a team that has engineers and no one to set the architecture, review the difficult pull requests or say no to the wrong plugin. A set number of hours a week, not a full-time chair.
A team that has outgrown its current lead, or has none.
- Architecture decisions recorded as made
- Code review with the reasons attached
- A team faster without me by the end
Runs in three-month blocks. Either of us can stop at a boundary, and everything decided is written down so the next person can pick it up.
How an engagement runs
The shape of a build or migration, part-time. A review or rescue compresses this into one to three weeks; a fractional lead role skips discovery and architecture.
-
Discovery call
30-minute free call. We work out whether I'm the right fit, and whether part-time is enough for what you need. If not, I'll tell you who is.
-
Written brief
Stakeholder conversations, a read of the content and the infrastructure. You get a written brief, with scope and boundaries, before anything is built.
-
Architecture
Content model, integration approach, plugin choices, deployment plan. Reviewed with your engineers, not over them, and recorded as decisions.
-
Delivery in phases
Your engineers build. I own the hard parts, review the rest, and we meet weekly. Each phase ends with something running.
-
Handover
Runbooks, the decision record, a handover session. I'm out once your team is faster without me. Quarterly reviews available.
Common questions
The things prospective clients always ask before booking the discovery call.
I'm employed full-time as Implementation Manager at Strapi. This site is my own: anything I take on independently is separate from that role and cleared with my employer, and the work and case studies here are mine, not Strapi's. If what you need is Strapi's own support or services, that's a conversation to have with Strapi directly rather than with me.
Less than a full-time engineer, and I say so up front. Independent work happens outside my core hours at Strapi, so it's part-time by design: fixed-scope reviews and rescues, or a retained number of hours a week. What you get in that time is the senior decisions, not the volume. Anything that needs a full-time pair of hands is a job for your engineers or a delivery partner, and I'll tell you that on the discovery call rather than three weeks in.
Mostly. I'll occasionally take a fractional lead role on a wider JS-ecosystem project, but only if there's a clear headless-content angle. I won't be the right fit for, say, a Rails monolith or a mobile-only product.
UK-based, fully remote. Independent work is remote by default because it fits around a day job. I'll travel for a kick-off or a workshop where it clearly helps, agreed case by case.
Sometimes. My independent work is scoped for teams with a real platform need and their own engineers, so I'm not always the right fit for an early-stage team. The free 30-minute discovery call is open to anyone, and I'll tell you honestly if the open-source resources will get you where you need to go without me.
No. I'm one person and that's the point. When scope needs more hands I'll say so early and help you find them, but I won't quietly subcontract: you'll always know who's doing the work.
Availability
Currently part-time slots from Q4 2026
One or two engagements at a time, part-time. Get in touch early if you have a date in mind.