This is where it started
“One update should go everywhere — but rewriting it for every channel means it usually ends up on just one.”observed → Started 2026.04.28
— So we built
Kamo
Livekamoweb service
A content ops SaaS that turns one product update into multi-channel content packs.
Developer evidence
What I owned in this project
- Period
- 2026.04 – Operating now
- Team
- Solo developer
- Contribution
- Planning · design · development · deployment · operations, 100%
- Owned scope
- Separates AI generation and publishing prep through the Idea -> ContentPack -> Variant -> Review -> Publish state flow.
Introduction
Kamo turns one product update into channel-ready drafts for blogs, social posts, and shorts. Choose only the channels you need, then review, approve, and prepare the content for publishing in one flow.
User flow
- 01
Enter one product update, release note, or promotion idea.
- 02
Generate a content pack and draft variants for the selected channels.
- 03
Finish review, approval, export, or publishing prep in one surface.
Highlights
- Branches one product update into blog, social, and shorts drafts.
- Lets teams choose only the channels they need and reduce review overhead.
- Connects review, approval, and export in a single content operations flow.