Services · How I help
4 ways to work together.
All engagements start with a free 30-minute discovery call. Every engagement is scoped up front — you'll know the shape of the work before we start. Below: what I do, who it's for, and what working together looks like week-by-week.
Performance & Architecture Rescue
Your Strapi build is slow, fragile, or about to launch and you're not confident. I find out why, and fix it.
Teams weeks from launch, or live and firefighting.
- typical:
- 1–3 weeks
Headless Build & Replatform
End-to-end delivery. Content model, migration, integration, launch, handover. Legacy CMS to headless, or a greenfield build done properly the first time.
Organisations with a real platform need and no delivery partner.
- typical:
- 8–16 weeks
Interim Technical Lead
Stepping into the chair when you need a senior technical lead and don't have one. Direction, architecture decisions, code review, mentoring — and a team in better shape than I found it.
Cover during a gap, or a team that's outgrown its current lead.
- typical:
- 3–6 months
Public Sector & Accessible Delivery
Digital services built to GOV.UK standards and WCAG, by someone who's delivered inside a national institution and knows what procurement, accessibility audits and FOI-able decisions actually require.
Public sector, GLAM, education, charity.
Rates on request — scoped per engagement.
How an engagement runs
Standard cadence for a full implementation. Scoped work compresses this into two weeks; coaching skips the discovery and architecture phases.
-
Discovery call
30-minute free call. We figure out if I'm the right fit. If not, I'll tell you who is.
-
Listening
Stakeholder interviews, content audit, infra read. I produce a written engagement brief before we touch a line of code.
-
Architecture
Content model, integration approach, plugin choices, deployment plan. Reviewed with your engineers, not over them.
-
Delivery
Embedded with your team. Weekly demos, two-week feedback cadence, your engineers in the driver's seat by week eight.
-
Handover
Runbooks, training sessions, on-call shadowing. I'm out the door 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.
Mostly. I'll occasionally take an interim tech 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. I travel for kick-offs, key workshops, and post-mortems where it helps; most enterprise clients see me on-site for the moments that matter during delivery.
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 booking into Q4 2026
I take a small number of engagements at a time — get in touch early if you have a date in mind.