Back to home

Case study · Services

55+: a new frontend and a back office in 5 languages, in ~6 weeks

We rebuilt the frontend and built from scratch the multi-language back office the team uses to manage services, clients and orders — with payments built in.

5 languages
across the whole product, from frontend to back office
3
management domains: services, clients and orders
~6 weeks
full redesign + back office from scratch
Timeline
~6 weeks
Investment
€16,000 – €24,000
Stack
Next.jsSupabaseStripeSendGridNetlify
We went from managing everything by hand to a panel where the team works in their own language. The day-to-day change was immediate.
Marta S.Co-founder, 55+

The problem

55+ had a working product but dragged two anchors: a frontend that didn't match the brand, and an operation managed by hand, with no internal tool to administer services, clients and orders. With a team and an audience working across several languages, any half-measure would fall short.

What we built

Two pieces, one system:

  • Rebuilt frontend with Next.js: the public face of the product, faster and aligned with the brand.
  • Complete back office from scratch, in 5 languages: the internal panel where the team manages the three domains of the operation — services, clients and orders — each with its own creation, editing and tracking flows.

Underneath: Supabase as backend and database, Stripe for payments, SendGrid for transactional email and Netlify for hosting.

How we did it

Multi-language wasn't a patch at the end: it was designed from day one as part of the architecture, so every view — public or internal — existed in all 5 languages without duplicating code. Deliveries were weekly, with the 55+ team testing the back office on real data from week three.

This scope maps to our Product tier: a complete application in production, integrations included, in 3–6 weeks.

The result

The whole operation lives in a single tool: creating a service, tracking an order or charging a customer goes through the panel, in the language of whoever uses it. What used to be manual work scattered across spreadsheets and messages is now a flow with state, history and payments built in.

Got a similar project? Tell us about it and we'll give you a timeline and range on the first call.

Book a call