What was the scope of the engagement?

Two distinct pieces. One — a one-off website plus brand collateral build for the launch beauty brand on Astro with Decap CMS, including namecard and pricelist deliverables, with Claude Code as the local build companion. Two — an ongoing social management retainer across two of the operator's brands, one beauty salon brand in Ho Chi Minh City and one education brand, covering Facebook plus Instagram, with a defined weekly posting cadence per brand and a shared engagement reply discipline.

Why Astro plus Decap instead of Shopify or WordPress for the launch brand?

The launch brand needed a content-first marketing site that loaded fast, was cheap to host, easy to hand maintenance back to the operator, and had no recurring platform fees. Astro plus Decap CMS hits that envelope cleanly. Decap gives the operator a git-backed CMS without a backend service to maintain. Astro builds to static HTML with optional islands for any interactive piece. The build environment is a local Claude Code companion, which keeps the iteration loop tight without spinning up a hosted dev environment.

How is the multi-brand social retainer shaped?

One operator, two live retainer brands, distinct content calendars. The beauty salon brand runs at one weekly cadence on Facebook plus Instagram. The education brand runs at a higher weekly cadence on Facebook plus Instagram. Each brand has its own content pillars, voice, and audience profile, so the calendars are built separately, not copy-pasted. Content production sits with LUMA-E. Live engagement replies sit with the operator's team. Monthly reporting closes the loop on what posted, what landed, and what shifts for the next month.

What does owned end-to-end look like for a small retainer like this?

For the social retainer, owned end-to-end means we own the calendar build, the content production, the asset preparation, and the monthly reporting cadence. We do not own the in-platform engagement, since that needs the operator's voice for trust and reply nuance with paying customers. For the one-off web build, owned end-to-end means scope, design, content, build, and handoff with the operator's team able to maintain content via Decap without us. The shape of ownership is matched to what the operator actually needs.

Why is this case study in the LUMA-E library?

Three reasons. One — it shows what a multi-brand operator engagement looks like without overscoping into a single platform pivot when the brands have legitimately different needs. Two — it shows a small AI-first agency delivering both web build and ongoing social, where the same LUMA-E memory layer carries context across distinct brand calendars and a separate one-off build. Three — it shows a scope-only public case study where the brand names, the operator's identity, and the engagement shape are public per consent, and the numbers stay private per discipline.

What is in this case study and what is deliberately left out?

This page covers engagement scope, platform choices, multi-brand calendar shape, and ownership boundaries. It deliberately omits engagement counts, follower numbers, conversion figures, retainer fees, project fees, and internal project codes. Those are confidential. The engagement shape and the discipline are what is portable. The numbers stay with the operator.

Core delivery work·AVOS sits on top →

CASE · ASTRO · DECAP · MULTI-BRAND SOCIAL RETAINER

Three brand tracks.
One shared memory layer.

Vivian is an Australia-based multi-brand beauty and education operator. The engagement is two distinct pieces under one operator relationship — a one-off Astro plus Decap web build for the launch beauty brand (with namecard and pricelist collateral), plus an ongoing social management retainer across two live brands: a beauty salon brand operating out of Ho Chi Minh City and an education brand. Facebook plus Instagram per brand, distinct cadences, distinct calendars. Scope and discipline only — no numbers.

Operator

Vivian (Australia)

Brands in scope

Launch beauty · HCMC salon · Education

Engagement

One-off web build + ongoing social retainer

Status

● One-off complete · Retainer active

01 · The brief

Two engagement shapes under one operator.

A multi-brand operator does not need a single engagement shape across every brand. The launch brand needed a marketing site. The salon brand and the education brand needed ongoing social presence at different cadences. Splitting the work into a one-off deliverable plus an ongoing retainer matches the actual operational shape — instead of compressing three brands into one calendar.

02 · The web build

Astro plus Decap for the launch brand.

Astro builds to static HTML with islands of interactivity where needed. Decap CMS gives the operator a git-backed editorial interface without a backend service to maintain. The build companion is Claude Code, local. The brand collateral — namecard and pricelist — shipped as part of the launch package, not bolted on.

Astro plus Decap CMS marketing site for the launch beauty brand
Namecard plus pricelist as part of the launch collateral
Claude Code as local build companion
Handed back to the operator team for ongoing content maintenance

03 · The social retainer

Distinct calendars per brand.

Two live brands on Facebook plus Instagram. The HCMC salon brand runs at one weekly cadence with a voice tied to that specific market. The education brand runs at a higher cadence with a different voice and audience profile. LUMA-E owns the calendar, content production, asset prep, and monthly reporting. The operator team owns in-platform engagement replies — reply nuance is brand voice work that needs to live with the people closest to the live customer relationship.

Facebook plus Instagram across two live brands
Distinct weekly cadences and distinct content pillars per brand
LUMA-E owns calendar, production, asset prep, monthly reporting
Operator team owns in-platform engagement replies

04 · Shared memory layer

Three tracks, one context layer.

The compound advantage of an AI-first delivery stack does not show up on single-brand engagements. It shows up here — same operator profile, three brand identifiers, three calendar shapes, three voice notes, all carried in one shared memory layer. Three brand calendars do not mean three rebuilt context windows every month. The discipline of the memory layer pays back hardest on engagements with multiple tracks under one client.

05 · Why this case is here

Engagement shape over leaked numbers.

This page deliberately omits engagement counts, follower numbers, conversion figures, retainer fees, and project fees. Those are confidential. What is portable is the engagement shape: multi-brand operator work kept as distinct brand tracks rather than collapsed into one calendar, owned end-to-end where it makes sense, and an explicit ownership boundary on engagement replies. That is what we recommend to operators with similar brand portfolios.

Brand tracks

Launch web build + salon social + education social, one operator.

Engagement shapes

One-off Astro plus Decap build and ongoing multi-brand social retainer.

Memory layer

Shared context carries across all three brand tracks, every month.

MULTI-BRAND OPERATOR?

Run multi-brand engagements like Vivian —
distinct tracks, shared memory.

Same engagement shape, available for operators with multi-brand portfolios.

Book 30-min call See all work

Three brand tracks.One shared memory layer.