What we set out to build
To run social presence as an operational surface — watch, respond, publish, measure — instead of as a series of one-off posts.
What was built
- A monitoring and publishing surface built around the studio's own accounts
- Operational rather than campaign-shaped: designed for continuous use, not batches
What it achieves
- Consolidates what is otherwise three tools and a spreadsheet into one place
The stack
Python, API integrations.
Common questions
How was this built?
A founder brought the idea and the domain knowledge. We brought the team. The founder funded the build with a monthly subscription, and they hold equity in the company that resulted. We label every case study, because a studio that publishes its prices and argues the other side of its own comparisons has to be equally precise about its own portfolio.
What state is it in?
Internal tooling. We state that plainly rather than describing everything as production: several things here are deliberately gated, and the reason is usually evidence rather than a missing feature.
Can you build something like this for us?
That is the point of publishing it. The same patterns are in the catalogue at published prices, and you can scope your own version on the plain-English page without contacting us first.
Where to next
If something here is close to what you need, the same patterns are in the catalogue at published prices, or you can describe your version in plain English and get it scoped and priced without talking to anyone.