Serrin Book →
Embark Studio
v1.7

Calendar · April 28 to May 2

This week's content

Posts · 30 days

30

1 per day · 100% on time

Cost displaced

$48K /yr

vs $4K/mo agency retainer

Time per post

5 min

trend to scheduled

Trend signals

184

scanned this week

Mon · Apr 28

08:30

5 carry-ons that survived a year

Live IG · 6 slides

Tue · Apr 29

11:00

Brass keys, leather wear-in

Scheduled IG · 6 slides

Wed · Apr 30

08:30

Why we picked waxed canvas

Scheduled IG · 6 slides

Thu · May 1

12:30

Founders' first trip · Lisbon

Draft IG · 6 slides

Fri · May 2

08:30

Field notes · weight vs volume

Draft IG · 6 slides

Trend signals · feeding next week's drafts

Reddit · YouTube · HN · PubMed
  • Reddit · r/onebag

    Peak 28L lightweight loadouts, +38% week

  • YouTube · transcripts

    Travel duos cite weight first, looks second

  • Hacker News

    Long-thread on durable canvas vs synthetic

A representation of the Embark Studio content workspace. The weekly calendar shows five posts (one live, two scheduled, two draft) with abstract image swatches, captions, and status. Stat tiles on top show 30 posts in 30 days, $48K per year cost displaced versus a $4K monthly agency retainer, 5 minutes per post from trend signal to scheduled, and 184 trend signals scanned this week. Below the calendar, three trend signals from Reddit, YouTube, and Hacker News feed next week's drafts.
Outcome

$48K/yr agency cost displaced with an end-to-end content agent

$48K/yr

agency cost displaced

Embark · Personal project · ongoing

Python Claude API Ideogram v3 Playwright Meta Business Suite

The setup

Embark is a small travel-goods brand. The traditional path is a $4,000-per-month content agency: weekly calls, two posts a week, slow turnaround, generic stock photography, captions written by someone who has never used the product. Most early-stage consumer brands cannot afford the agency they need; the ones that can spend $48,000 a year and still complain about output.

The hypothesis was simple. A small senior-built agent should be able to do every step of a content pipeline that an agency does, and do it daily instead of twice a week, for the cost of API calls.

How it works

Four stages, all automated, with one human review checkpoint before scheduling.

  1. Trend scan. A weekly job pulls signals from Reddit, YouTube transcripts, Hacker News threads, and PubMed abstracts in the brand’s category. Claude Haiku 4.5 distills each signal into a structured analysis: takeaways, what is novel, quotable lines, sources.
  2. Carousel draft. A second Claude pass converts a chosen trend into a six-slide Instagram carousel: a thesis slide, four supporting slides with concrete claims, a closing slide with a call. Caption draft included.
  3. Image generation. Ideogram v3 (QUALITY) generates each slide’s image with brand-locked prompts: travel-goods context, warm editorial palette, no text overlays where text is composited at draft time, no people, no faces. Cost: about $0.02 per slide.
  4. Schedule. A Playwright script logs in to Meta Business Suite (using a persisted session cookie, no password handling on every run), uploads the six images, pastes the caption into the Lexical editor, sets the date and time, and stops just short of clicking the final Schedule button. The human reviews the queued post and either confirms or rejects.

End to end, on a warm cache, the loop runs in about five minutes per carousel.

What it ships

The trend scanner alone has been the highest-leverage piece. Most “trends” are not trends; the LLM analysis layer filters the noise and surfaces the few signals worth posting on.

What was hard

The four-stage pipeline is the boring part. Three things took the time.

1. Brand-voice guardrails for image generation. Out of the box, Ideogram interprets “travel goods, editorial photography” as cruise-line stock or mountaineering brochure. Neither is the brand. Producing a consistent voice required a prompt template with explicit anti-references (“not a backpack catalog, not an outdoor adventure brand, not a luxury hotel ad”), explicit material palette (“waxed canvas, leather wear-in, brass hardware”), explicit context cues (“warm afternoon light, deep amber and cream tones, hard-edged shadows”), and a strict negative-prompt list per slide. The first version of this template generated unusable images about 40 percent of the time. The current one fails closer to 5 percent. That gap is mostly anti-references.

2. Meta Business Suite scheduling is brittle. The Lexical editor inside Meta Business Suite resists the standard Playwright clipboard paste. Caption text has to be injected via a specific keyboard sequence into the Lexical contentEditable; UI updates upstream break this every few weeks. The agent does not click the final Schedule button on its own, both for safety and because Meta’s automation detection is sharper at the schedule confirm than anywhere else in the flow. The human-in-the-loop checkpoint is non-negotiable; trying to remove it would be a feature in search of a small per-post time saving and a large risk of an account flag.

3. The trend-to-post conversion is where the agent earns its keep, and where it most easily fails. Most trend signals do not become good posts. The LLM analysis layer needs strong rejection criteria, not just summarization: “skip if the claim cannot be sourced,” “skip if the post would require footnoting medical or financial guidance the brand cannot make,” “skip if three other posts this month have covered the same angle.” Without those rejection rules, the agent produces a steady stream of plausible-sounding content that erodes brand voice over time. With them, output volume drops by half but every post is one the brand would actually want to publish.

Outcome

A daily content cadence that has held for thirty consecutive days, run by a one-person operator with five minutes per day of attention, at less than two percent of the agency cost path. The pipeline transfers cleanly: the same architecture is portable to any small consumer brand whose content needs out-pace their content budget.

Stack

Python end to end. Claude Haiku 4.5 for trend distillation, Claude Opus 4.7 for caption drafting where voice matters more than throughput. Ideogram v3 (QUALITY) for image generation. Playwright with persisted Meta Business Suite session for scheduling. A small structured-output layer using Pydantic for trend analyses; a markdown calendar for the editorial roadmap; a dashboard built in plain HTML that lists every post’s status at a glance.

← All lab notes