Rebuild & migration
Archaic WordPress: headless or Laravel by phases
You start from archaic WordPress: slow, fragile plugins, legacy theme, editorial or business logic holding the product back. I step into that environment as it runs today and help you move into a modern stack without « tearing everything down »: headless WordPress (WPGraphQL or REST, React/Next.js front), or Laravel admin and API (REST or GraphQL) with progressive migration.
I come in as fractional technical PM/PO with hands in the code: depending on the mandate, I can develop critical migration phases myself, or lead your existing team (prioritize, sequence, organize the stack transition). Written plan, successive phases, no big bang. We talk first to see the time and need, then how to mobilize my time on the mandate.
Frame your rebuild Book a callLinkedInhello@lucrousseau.com
WordPress context
I step into your archaic WordPress as it runs today and map how to help you move into a modern stack: what blocks you, which architecture fits the product, no big bang.
Archaic WordPress
- Archaic stack: legacy theme, piled-on plugins, few APIs, perf and debt blocking the product
- Technical debt and a data model that is hard to migrate without prod risk
- Team in continuous firefighting, no clear roadmap to modernize the stack
Two paths: headless or Laravel API
- Headless: WordPress as CMS, WPGraphQL or REST, React/Next.js front on the client
- Laravel: business administration, REST or GraphQL API, progressive module migration
- Both approaches chained in phases, rather than a binary choice from day one
How we advance
Fractional, phased, with a plan
Not a full-time rebuild embedded in your org: phase mandates, rhythm and mobilization set after a first conversation on what you actually need.
I code the transition or steer the team
No team: I own build (APIs, headless front, Laravel modules) and the product plan. With team or agency: I lead sequence, priorities, and reviews, without replacing your tech lead day to day.
Successive phases, shipping to prod
Audit, path choice, then slices that ship to production: API layer, first headless journey, module under Laravel. Properly and fast, not an 18-month tunnel with no visible business progress.
Stack and contracts fixed before build
WPGraphQL, REST, GraphQL gateway, Laravel, React, Next.js: what serves your case, not stack fashion. Data contracts and boundaries written so your devs or I build on the same rules.
The flow
Four typical steps in a rebuild mandate
Audit and path choice
Current WordPress (perf, plugins, data, editorial), then a written decision: headless GraphQL/REST, Laravel admin + API, or a sequence of both.
Plan and migration order
Phase roadmap, risks, what we don't migrate yet, success criteria per slice. No large build before that deliverable.
Build phases with prod value
Strangler, feature flags, old/new coexistence: delivery by your team or by me depending on mandate. Each phase keeps the site usable and shows measurable business or perf progress.
Handover and lighter follow-up
Documentation, runbooks, team pass-off. Optional fractional follow-up (lighter rhythm) to hold coherence after the heavy migration phase.
Compare
Internal rebuild vs external product-system partner
Each engagement is scoped in written phases. High-traffic editorial WordPress: Editorial product at scale complements this phased rebuild approach.
| Dimension | Team alone on rebuild | Fractional technical PM/PO by phase (custom rhythm) |
|---|---|---|
| Direction | Often lost in execution; why drifts. | Go/no-go, sequence, success criteria held externally. |
| Pace | Big bang or permanent catch-up. | Fractional mandate tuned to need; phased value, not a continuous full-time rebuild. |
| Team role | Overloaded or missing internal lead. | Code on key phases or orchestration of existing team; plan, sequence, product-tech coherence. |
| Engagement | Fixed payroll for full duration. | Phase mandate (then optional lighter follow-up). |
How I build
Technical foundations
WordPress to modern, by steps: headless, Laravel admin + API, or both in sequence, without cutting prod.
Objections
Common questions
Both are possible, depending on what you already have. I code when a technical phase must move fast and no one is available to do it properly. I steer when your devs or agency have capacity: I prioritize, sequence, clarify prerequisites, and validate coherence, without micro-managing tickets.
It depends on content, team, and debt. Often: headless (WPGraphQL or REST + modern front) if WordPress editorial still helps; Laravel admin + API (REST or GraphQL) if core business logic must leave the CMS. Sometimes both, in phases. We decide in writing before build.
Both are in scope. WPGraphQL or REST on WordPress; GraphQL on the app or Laravel BFF when surfaces and consumers justify it; REST when simplicity and the team favor it. The phase plan states which contract for which module.
No. Phase mandates: we talk first to see the time and need, then how I mobilize my time (framing, build or orchestration, lighter follow-through). Not a « 40-hour rebuild » embed: your team builds, I hold the product-tech plan and sequence.
No. Your devs or agency keep operational rhythm. I clarify system and sequence; I don't manage people or daily tickets.
Two to four weeks of framing often avoids months of rework. Phase one can be exactly that, deliverable: plan, target architecture, migration order.
Documented handover; optional fractional follow-up to keep coherence without a permanent role. Similar model: Editorial product at scale or Launch a SaaS or MVP; see also all situations.
The agreed rhythm structures deep work, not whether you can reach me.
Ongoing, I make time to reply on Slack or your preferred channel. If an emergency lands outside scheduled days, I stay reachable and step in under a shared urgency frame we define up front (scope, priority, response time), not a vague 24/7 on-call promise.
Next step
Archaic WordPress? One call to see how to move into a modern stack (headless, Laravel API, phased plan) instead of a big bang without a map.
LinkedInhello@lucrousseau.comNext step
Let's talk about your context
A 30-minute call to see if fractional support (product, technical, or both) fits your situation in Quebec.
- EmailReply within 24–48 hourshello@lucrousseau.com
- LinkedInBackground or messageView profile
Not sure which profile fits? Browse situations or take the two-question quiz.