Kartheek Akella

I m Karthik, the maker of PostRoom, launching today. I d value a practical view from people who review client content.

Here s the edge case: a client approves a caption, then someone changes the wording before it reaches the scheduler. The approval was for the old text.

I chose a simple rule: any saved caption edit clears that version s approval. The changed caption needs a fresh client decision before it can enter the approved-only CSV. Clients use an expiring review link and need no account. This covers text only; visual proofing and publishing stay in your existing tools.

For your workflow, would every edit need reapproval, or would you distinguish a typo fix from a changed claim or CTA? Who should make that call? I d also like to hear how you keep the final approved text intact when handing it to a scheduler.

I recently built a small PDF editor with AI for myself. That got me wondering about another use for these small apps.

Has anyone here built a free tool specifically to help people discover their main product?

I m getting Inquir Compute ready to launch. It s a platform for running apps, databases and background jobs, and it s where I host the editor. Alongside sharing what I m building here, I m looking at other ways to reach developers.

A small tool for the same audience sounds worth trying. But I don t know how often that turns into customers, rather than a second app you now have to maintain.