How I work. From the briefing to data-led iteration.
No agency process with a project manager between us. A direct four-phase method, clear deliverables at each step, and communication that records decisions without losing them across Slack threads.
- Do you work solo or with a team?
- Mostly solo : continuity from brief to go-live. For high-volume projects (large migrations, 1,000+ SKU catalogs, app development), I work with a trusted network of developers and designers : always under my coordination and responsibility.
- How does handover work at the end of a mission?
- Every project ends with a handover document: organized access, documented theme architecture, maintenance guide for common changes. I plan 1–2 Q&A days with your technical team or next vendor if needed.
- Can we start directly at phase 3 (Build) without scoping?
- I don’t recommend it, and I don’t propose it. Building without scoping or UX validation almost always leads to costly post-launch iterations. Scoping (3–10 days) is short compared to the cost of a redesign six months later.
- How do you handle emergencies or post-launch bugs?
- The first 30 days after go-live include mission support : bug fixes related to deliverables, minor tweaks, answers for your team. After that, maintenance is structured via quote or monthly retainer.
- Do you use specific project management tools?
- I adapt to your environment. If you use Notion, I deliver in Notion. Drive, same. I don’t impose a tool : I impose rigor on how decisions are logged, whatever the tool.