Why I built PostFrames

I built PostFrames because I needed it first.

A while back I started Busque Festa, a marketplace for parties and events. I knew from day one that it would live on social media, mostly Instagram. To get any traction I had to show up constantly: posts, carousels, stories, week after week.

There was one problem. I have a full-time job. Busque Festa, and everything around it, happens in the evenings and the gaps. I don’t have hours to spend in a design tool, and I’m not a designer anyway.

So I tried the usual things. Canva was fine until I wanted ten posts that actually looked like the same brand. Every post drifted a little. Redoing last week’s layout with new words took longer than writing the words. Hiring someone wasn’t on the table for a side project.

What I wanted was simple: describe a post, get a finished one back, on-brand, in a couple of minutes. And if I changed one line of text, I wanted only that line to change, not the whole design.

So I made a small tool for myself. Set the brand once, type what the post should say, get a real post out the other end. The same input always produced the same result, so I could fix a typo or spin up a whole series without starting over.

It worked better than I expected. I started using it for Calcula Online too. At some point it stopped being a script and became a product. That product is PostFrames.

It still carries the same three things I needed back then: fast, on-brand, and reproducible. If you run your own social and don’t have time to design every post, I think you’ll feel the same relief I did.