The Polished Brunette

Dina — founder of Atomic Brunette, LLC. On Instagram as @thepolishedbrunette (brand) and @bangbangsdina (personal). The Tasteful Editor: a lifestyle curator whose audience trusts her to filter the noise and surface what's actually worth buying.

The Polished Brunette is Dina's owned editorial home at thepolishedbrunette.com — the destination her Instagram audience can shop, subscribe to, and come back to. A calm, feminine, intentional site that turns her IG reach into a compounding affiliate business she controls, not a feed she rents.

Behind the public site is Dina's /admin dashboard — a login-gated editor where she runs the catalog herself. Adds products, swaps photos, edits the home hero copy and her about-page paragraphs, reorders the filmstrip, imports her existing Beacons links. The repo is the renderer; Dina is the source of truth.

The brand wins by what it leaves out: less, but better.

Dina already had an engaged Instagram following — people who trusted her as the friend with exceptional taste. The audience wasn't the problem. The problem was that a reel caption isn't a place to click a product, read the backstory, or subscribe to anything. Every time she recommended something, the revenue and the relationship walked off to another platform.

Dina's problem was a business problem, not a content problem.

• Instagram owns the audience. The algorithm giveth and the algorithm taketh away. When it shifts, growth stops — and there's no way to reach the people who had already found her.
• Affiliate revenue was leaking. Every outbound "link in bio" sent her audience directly to Amazon, where Dina's brand disappeared and the only thing tracked was her commission on that single click. No catalog, no search, no return visits.
• The voice didn't scale. Her register — refined, editorial, intentional — wasn't going to survive if every product description was hand-written or, worse, templated.
• Building the infrastructure herself would take months. Shopify, CMS, auth, newsletter, affiliate tracking — all of it would be rented and bolted together.
• Story posting was a Canva grind. Every product Dina wanted on Instagram Stories meant manually dropping an Amazon stock photo into a Canva template, exporting, AirDropping to her phone, then uploading and adding a link sticker. Multiply by every product, every week.

She needed a single owned surface where her audience could read her, shop from her, and subscribe to her — with a back-of-house she runs herself, without ever leaving her brand.

theAppChicks shipped thepolishedbrunette.com in a single day — morning kickoff to live-on-production in under 4 hours on April 15, 2026. The product hasn't sat still since: the catalog moved to Supabase, the admin dashboard shipped, inline CMS gave Dina edit-on-page control of marketing copy, and a Beacons importer eliminated the per-product setup tax. Here's what Dina's business has now, as capabilities Atomic Brunette owns:

An audience she owns

Every visitor can subscribe to her newsletter at thepolishedbrunette.com. The email list is on her domain, sent through her Resend account. If Instagram's algorithm shifts tomorrow, she still has a direct line to the people who chose to hear from her.

A catalog Dina runs herself

Products live in Supabase — name, description, merchant URL, thumbnail, story image, category, sort order, active/inactive. Dina manages every field from /admin/products: tap-to-edit on mobile, drag-to-reorder, instant activation, image upload from her phone (camera or library) straight into Supabase. No git, no PR, no developer in the loop. The hero filmstrip on the home page is whichever 8 products she's flagged active right now.

Affiliate revenue infrastructure that compounds

Every outbound product link routes through one helper that strips Amazon's noisy session params, adds Dina's associate tag, attaches traffic attribution, and tags every link as sponsored with a visible disclosure. Same pipeline scales to every future merchant (Colorescience, Lululemon, Nike, REI, Chewy already wired in).

Inline CMS — edit on the live page

When Dina is signed in, every editable region on the public site shows a small pencil. Click it, change the copy or swap the image, save. Hero headline, hero body, about-page intro paragraphs, pillar names and blurbs, shop intro, newsletter title — 29 keys plus the hero and profile photos, edited where they render. No /admin/cms page to navigate to; the marketing site itself is her editor. Regular visitors see no affordances.

Beacons one-click migration

Dina's existing Beacons.ai page (her old link-in-bio hub) is the source for everything she's already endorsed. An import pipeline pulls her Beacons catalog into Supabase — Amazon URL, image, title — idempotent on re-run. Imports land inactive and uncategorized; Dina activates and categorizes during her normal curation pass.

A voice system that scales

Before any copy was written, a persona doc codified the brand — The Tasteful Editor: preferred language (polished, handpicked, effortless, elevated), forbidden language (obsessed, must-have, you need this, luxe, dupe, glam), a five-point selection filter for every product, and a deliberate outdoor-as-supporting-category framing. That persona is now the system prompt for every content agent writing for the brand. The voice survives scale automatically.

A business that's portable

Supabase, Resend, and the Amazon associate tag are all in Dina's accounts. The domain is Dina's. The content and code live in a repo she owns. If she ever changes vendors — or changes agencies — the business moves with her.

The story-posting grind was the next bottleneck. Three phases sequenced to remove it without overbuilding.

• Phase 1 — auto-generate the image. A behind-the-scenes renderer composes Dina's brand template with the product's photo and name. One-click "download" in /admin, plus a "bulk ZIP export" so she can pick a week's worth and AirDrop them in one go. The Beacons import (already shipped) is the on-ramp — every Amazon link she's ever shared becomes a story-ready PNG without a Canva session.
• Phase 2 — publish from /admin. A "Publish to IG story" button posts the rendered PNG directly to her Instagram via the Graph API, with the link sticker pre-attached. Gated on a small Meta-permissions discovery spike before commit.
• Phase 3 — scheduled rotation. A /admin/stories/schedule calendar plus a Cloudflare Worker cron auto-publishes from a queue of products on the cadence Dina sets. Plugs into the same Phase-2 publish endpoint — no new IG integration, just a scheduler on top.

• A calm editorial landing page that explains the taste, not a wall of product grids.
• A hero filmstrip of her current 8 picks — refreshed whenever she edits in /admin, with no deploy.
• A journal with real imagery, real writing, real recommendations — not AI-breathless product blurbs.
• Affiliate product cards that show real Amazon thumbnails beside her tagline, with visible disclosure so the recommendation feels honest.
• Product pages on her site — read the backstory, then click out to buy when they're ready.
• A newsletter signup that's an invitation, not a pop-up ambush.

• A login-gated /admin she signs into with a magic link or one-time code (cross-device).
• A products page that's tap-to-edit on her phone — every field, every image, every reorder happens from her thumb.
• An image picker that opens straight to the camera or photo library; uploads land in Supabase and appear on her site.
• An inline pencil on every editable region of the public site — change a hero headline or an about-page paragraph in place, save, see it live.
• A /admin/design typography editor for the 12 brand-typography settings — no CSS edits.
• A Beacons importer that turns her existing link-in-bio into a Supabase catalog in seconds.
• One Supabase project, one Resend account, one Amazon associate tag, one domain — all in her name.

The Polished Brunette is the pattern for any creator with an Instagram or TikTok audience who's tired of renting:

Your audience already trusts you. The question is whether you're capturing that trust into something you own — a catalog, an email list, a brand home, an admin you actually run — or letting it bleed off to a platform that owes you nothing.

It's also proof the theAppChicks model works for voice-first content brands — not just trading apps, coaching platforms, or membership sites. The same delivery cadence that ships a native trader app in 3 weeks ships a refined lifestyle brand in 4 hours, then layers in a Supabase-backed admin, an inline CMS, and a Beacons importer in the weeks after. Different industries, same model, same ownership outcome.

Live + actively shipping. thepolishedbrunette.com public on April 15, 2026 (initial launch in under 4 hours from empty repo to apex domain). Since launch: Supabase auth, role-based admin (Dina = editor, Carey = admin), products + storage, sort-order + 8-active-cap UI, design typography editor, inline CMS for hero/profile/copy, Beacons importer. In flight: Instagram Story automation Phase 1.

Included for the curious. This is how the outcomes above are delivered; none of it is the story.

Layer	Choice	Why it serves the business
Framework	Next.js App Router + React + TypeScript	One site for marketing, journal, affiliate catalog, and /admin
Styling	Tailwind	Brand voice (typography, color, spacing) lives in tokens — and 12 of them are editable from /admin/design
Content	MDX journal + Supabase product catalog	Long-form stays file-backed; products live in a catalog Dina owns and edits
Auth	Supabase (magic link + one-time code)	Magic link for same-browser; one-time code for cross-device — Dina logs in from her phone without a desktop
Storage	Supabase	Image uploads from Dina's phone land in her project, not a third-party host
Email	Resend	Newsletter + contact from her domain, deliverability on her reputation
Hosting	Cloudflare Workers	Fast global edge, auto-deploy, preview URLs on every branch
Analytics	Cloudflare Web Analytics	Cookieless — no consent banner interrupting the reading experience
Realtime	Supabase	Edits in /admin reflect on the public site without a redeploy

Authoring model: the repo is the renderer; Dina is the source of truth. Products, marketing copy, and images all live in Supabase, edited from /admin. Every change Dina makes is hers, on her own data.

• Live site: thepolishedbrunette.com
• Brand IG: @thepolishedbrunette
• Dina IG: @bangbangsdina
• Source repo: theappchick/thepolishedbrunette (private)
• Brand persona doc: theappchick/thepolishedbrunette/docs/brand/persona.md — the operational contract every content agent writes against