Skip to content

Client build, names hidden

A book rental service sees what to post and which ads work

A book rental service made every post by hand and could not see which ads worked.

What to post. What to approve. Which ads work. Client build, brand and money hidden. The ads screens are a design prototype in build, with demo numbers.
Trade
E-commerce
Tools
  • Python
  • OpenRouter
  • Image and video generation APIs
  • Omni Socials
  • MySQL (read-only)
  • Meta, Google and TikTok ads (read only)
  • Slack
  • Email

Before and after

Before

  • Every holiday, season or launch needs its own post.
  • Each post means writing, an image, a video and a caption.
  • Ideas, approvals and posting sit in different places.
  • Nobody can say which ads work.

After

  • Milestone 1 delivered (Oct 2026). The second phase is already committed: a comments inbox and an advertising module.
  • The ads screens in the video are a design prototype with demo numbers.

What we built

  • Triggered by dates. A holiday, season or launch date starts the engine.
  • One event, four pieces. One post, one image, one video and one caption.
  • A review board. Ideas move stage by stage. The team approves before anything goes out.
  • Publishing on approval. Finished posts go to Instagram, Facebook and the other accounts.
  • Ads, read only. In build: an agent reads the ad accounts and builds the report. It never changes a budget.

Making every post by hand?

Tell us about the one report you rebuild by hand every week.

Or send one sample file on WhatsApp (opens WhatsApp). Fake names are fine.

Tell us how you post

We reply within one business day. No card, no contract.

More builds like this

More on AI Workflow AutomationSee all case studies