I build digital platforms. And fix the ones already in trouble.
I'm Alex Bennett, an independent technical lead for enterprise Strapi and headless platforms. My day job is inside enterprise Strapi implementations (the ones going well and the ones that aren't), after a decade building platforms agency-side and at the British Library. Independent work is part-time and fixed-scope. You get me directly: no account manager, no juniors learning on your budget.
- Writing — “Is canvas design dead in the age of AI?”
-
portfolioServices: cards redesigned as a row of offers -
libraries.globalrefactor(ui): eliminate LibrarySearchParams mapping shim in LibraryIndexGrid
Front End Developer in 2015. Technical Lead and Head of Web Development from 2020. Implementation Manager at Strapi since 2024. Agencies, a national institution, now the vendor.
Led web development at 43 Clicks North, then covered the Head of Web Development role at the British Library for a year during the postholder's parental leave.
My full-time role is at Strapi, inside enterprise implementations. The independent work on this site is separate from that role and cleared with my employer.
Led the web development team's interim service response in the hours after the 2023 British Library cyber attack, in collaboration with the Digital Engagement team.
What I do
Part-time, fixed-scope engagements alongside my day job. Scoped up front, so you know what you receive.
| code | service | description | format | typical |
|---|---|---|---|---|
| S/02 | 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. | Fixed scope | Diagnosis 1–2 weeks, part-time |
| S/03 | 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. | Phased | 8–16 weeks, part-time |
| S/04 | 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. | Retained | A few hours a week, 3–6 months |
How I work
The operating principles behind every engagement.
No agency overhead
You talk to the person building it. No discovery phase that produces a slide deck, no chain of people between your question and an answer.
Judgment, not headcount
You're paying for the decisions, not for hours of typing. I use AI-assisted tooling where it earns its place, so less of the budget goes on repetitive implementation and more on architecture, review and the choices that are expensive to get wrong.
You keep the knowledge
I'd rather leave your team able to run and extend the thing than leave you dependent on me. Handover isn't a phase at the end, it's how the work gets done.
Selected work
Case studies, abridged where confidentiality requires.
- Role
- Technical Lead
- Organisation
- British Library · Arts Council England· '24
- Owned
- Technical direction and architecture for the platform, code review, and the accessibility standard the build was held to. Product, design and content sat with the British Library and Arts Council England teams; day-to-day development was shared with the web development team.
- Stack
- Public digital serviceAccessibilityWCAG 2.1 AA
LibraryOn
Technical lead on LibraryOn, the national digital platform for public libraries in England: a searchable map of every public library in the country, each with its own page.
A national library map in public use: every public library in the country listed, each with its own page for opening times, accessibility and services.
Building High-Performance Strapi Apps: Common Pitfalls and Best Practices
Where Strapi performance problems actually come from, why populate=deep is a trap, and how to design schemas that don't get expensive as they grow.
What people say
Colleagues, clients, and the person whose role I covered. Marked quotes are public recommendations you can read in full on LinkedIn.
Alex is an exceptional developer, a skilled technical lead, and an inspiring development mentor.
I had the privilege of having Alex cover my role as Head of Web Development at the British Library for a year while I was on parental leave. Throughout this period, I felt completely at ease, knowing that the department was in such capable hands. Alex is an exceptional developer, a skilled technical lead, and an inspiring development mentor.
From the outset, Alex seamlessly stepped into the role, quickly establishing a strong rapport with internal stakeholders, which proved invaluable throughout the year. Upon my return, I received an abundance of positive feedback from stakeholders who commended his outstanding communication skills and proactive approach to problem-solving. Alex’s ability to engage and collaborate effectively with various teams significantly contributed to maintaining the smooth operation and progress of our projects.
Furthermore, I personally observed Alex’s mentoring abilities. He provided guidance and support to our developers, resulting in notable improvements in their skills and performance. His mentorship was met with extremely positive feedback, underscoring his talent for leadership and development.
During his tenure at the library, Alex also demonstrated his adeptness in crisis management. He managed a major incident with remarkable composure and decisiveness, showing initiative in a situation where many others might have faltered. His ability to remain calm under pressure and effectively navigate complex challenges speaks volumes about his capabilities as a leader.
I highly recommend Alex to any organization seeking a forward-thinking developer, technical lead, or development manager. His technical expertise, leadership skills, and unwavering commitment to excellence make him an invaluable asset to any team.
01 / 09
06 · Get in touch
Planning a Strapi rollout? Let's talk.
I take a small number of engagements each year, deliberately. Best fit: teams with their own frontend engineers (whatever the framework) bringing Strapi in to replace a legacy CMS or stand up a new headless platform. Discovery calls are always free.