Overview
NEVIE-GLOBAL needed a UK home for its ecosystem: founder access, connected jewellery, learning and technology services, presented as one premium brand. This case study documents that build. It is our own product, so every figure below comes from the running platform; commercial results are marked To Be Confirmed until they are measured.
Challenge
The ecosystem spans very different offers — a £1 digital founder card, physical jewellery sold on pre-order, free learning and bespoke services. Each needed its own buying journey without the site feeling like four separate products. The UK platform also had to price in GBP, handle UK VAT, respect UK GDPR and keep the original French product names.
Objectives
- One storefront for founder access and connected jewellery, paid through Stripe Checkout
- Service pages that turn interest into a qualified, stored enquiry
- A learning space (NEVIE Academy) that shares the same account
- An admin console so the team can run products, content, leads and delivery without developers
- No invented figures anywhere: unconfirmed details are shown as To Be Confirmed
Architecture
The platform is a single Next.js 15 application using the App Router and React Server Components. PostgreSQL (through Prisma) is the system of record for products, orders, leads, content and projects. Redis backs rate limiting and short-lived state. Public pages read through tagged caches, so publishing in the admin refreshes only the pages affected.
UI/UX
The interface follows the NEVIE-GLOBAL identity: deep navy and electric blue with gold accents, in light and dark themes. Motion is used sparingly for reveals and progress, and it switches off for visitors who prefer reduced motion. Every page was checked at desktop and mobile widths for layout and horizontal overflow.
Backend
Server routes validate every input with schemas before it reaches the database. Quote requests accept structured project details and an optional brief; attachments are stored privately and are only downloadable by staff. Transactional email is sent over SMTP, configured from the admin console. Staff access sits behind a private console URL and mandatory two-step verification.
Security
Staff areas are protected by role checks on every request. Public forms combine rate limiting, a honeypot field and optional Turnstile verification. Card data never touches the server: payment happens on Stripe Checkout.
Testing
Type checking and linting run on every change, with automated tests and a CI workflow. Browser checks with Playwright capture each key page at desktop and mobile sizes and submit the quote form end to end.
SEO
Each page has its own title, description and canonical URL, with structured data for products, services, FAQs and breadcrumbs. English (UK) is the published locale; a French version is To Be Confirmed.
Screenshots
Results
The platform is running with its full catalogue, learning space, service pages and admin console in place. Traffic, conversion and revenue figures are To Be Confirmed and will be added once they have been measured over a meaningful period.
8 products on sale in GBP through Stripe Checkout
2 Academy courses and 3 articles published from the CMS
Quote, call, demo and waiting-list requests stored as CRM leads
Commercial performance metrics: To Be Confirmed
Lessons Learned
- Mark unconfirmed information clearly instead of filling gaps; it builds more trust than placeholder numbers.
- Keep one source of truth: products and content come from the database, not from copies in the code.
- Private by default: client projects only appear publicly when someone explicitly publishes them.
Share your goals and we will propose a first release.