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.
Phase 1 turns calendar dates into ready-to-post content. Phase 2, in build, adds approvals and a read-only ads view.
The problem
Every post is made by hand, and nobody can say which ads work.
- 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.
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.
- Roles for the team. In build: one person generates the report, another approves the budget.
What it does every day
- Dates on the calendar turn into draft posts.
- The team approves what goes out.
- In build: one view of what is waiting and how the ads are doing.
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.
Tools
- Python
- OpenRouter
- Image and video generation APIs
- Omni Socials
- MySQL (read-only)
- Meta, Google and TikTok ads (read only)
- Slack