01 / The challengeWhat did MagneFo need?
MagneFo was running on a template theme that had accumulated years of plugins. Every campaign meant a developer ticket, and the product pages were slow enough on mobile that the checkout funnel was leaking before customers reached it. The brand had also outgrown its original identity.
02 / Our approachHow did we run the project?
We separated the storefront from the catalogue. Content moved into a CMS with a model built around how the team actually merchandises — collections, campaigns, and editorial blocks — so marketing edits content directly. The front end was rebuilt as a Next.js application with a strict performance budget checked on every pull request, measured on a throttled mid-range phone rather than a developer machine.
Discover
We listen and write it down
Scope + estimate
Design
You try it before we build
Prototype
Build
A demo every sprint
Sprint demos
03 / What we builtWhat did we build?
The storefront renders statically where it can and fetches only what genuinely changes per visitor.
Images are served through a CDN with responsive sources and modern formats.
Alongside the build we refreshed the visual identity — wordmark, type scale, and a palette with contrast verified against WCAG 2.2 AA — and delivered it as design tokens wired directly into the codebase, so the brand and the implementation cannot drift apart.
Fig. 01 · Feature map. Details vary by plan.
Built with Next.js and TypeScript on the front end, Sanity for content, and Stripe for payments, deployed on Vercel.
04 / ResultsWhat changed for the business?
- Engagement
- Storefront rebuild + brand refresh
- Scope
- Headless commerce, CMS, identity
- Stack
- Next.js, Sanity, Stripe
- Enforced in CI
- Core Web Vitals budget