Case study

Akyra Active Life

One content engine, three brands, twenty-eight posts.

Parent brand site, a shared blog engine deployed per brand, and email infrastructure with delivery logging.

The challenge

What they needed.

Akyra Active Life is a holding company with three consumer brands under it: Jind Mahia, Laxakaar and Wavryn Active. The group had no place explaining the relationship between them, and no way to publish content for any brand without going back to a developer. That second problem was the expensive one, because all three brands compete in categories where organic search is the cheapest acquisition channel they have, and none of them were publishing.

Our approach

What we did.

Three things, deliberately separated so the group could move on each independently: a Next.js parent site with a page per brand and a careers section; one blog engine deployed once per brand, with posts stored as Markdown in the repository rather than in a CMS; and a transactional email application with a delivery log. Building one engine and deploying it three times meant no per-brand cost, no admin logins to lose, and content that stays version controlled and portable.

What we built

Everything that shipped.

Parent brand site with a page for each of the three brands and individual careers role pages
Shared blog engine deployed per brand, Markdown with front matter parsed by gray-matter and rendered with marked
28 posts live: 16 on Wavryn Active, 7 on Jind Mahia, 5 on Laxakaar
Each blog instance ships an AGENTS.md so the group can extend its own site with an AI coding assistant
Email dispatcher on React Email and AWS SES v2, with Prisma over SQLite for the record
Every send logs template, subject, status, provider message ID and error
Dry-run send status, so a campaign runs against the real list without sending anything

Inside the build