Marketing My App Became Another App

I am Anton Rost, a solo founder and product builder in Germany. I build software after work. My current product is Sendezeit, a social publishing platform for founders and creators who handle their own distribution. It keeps one source attached to separate channel versions so review, scheduling, delivery and what actually went live stay in one place.

Before Sendezeit, I built Pocket Orbit, an iPad app for turning scattered thoughts into structured notes. Shipping the product was hard, but marketing it exposed another problem. One source video became different captions, titles, tracking links and upload notes across several documents. The documents drifted. A calendar could say something was planned without proving it was public. More ideas did not fix that handoff, so I started building the tool I needed.

People often assume social publishing is mainly a writing problem and that generating more captions solves it. I already had content ideas. The slow part was adapting one idea honestly for each destination, reviewing it, handling the provider handoff and knowing whether the post actually became public. A draft, a scheduled row and a live URL are three different states.

I was unprepared for how much distribution work begins after the product is finished. I could spend weeks building a feature and still have nothing ready to publish about it. Provider rules, media formats, review, tracking links and failed uploads create small gaps. Those gaps are where content disappears. I also learned that a large research archive can feel productive while producing very few finished pieces.

I am most proud of turning that messy internal workflow into a real product without hiding its limits. Sendezeit keeps the source, destination versions, calendar and delivery state connected. It distinguishes what was drafted, scheduled, attempted and confirmed live. I would rather show an honest unavailable state than pretend every provider works the same way.

Treat distribution as part of the product, not the task you start after launch. Begin with one real source. Make a separate version for each channel. Review every version before scheduling it. Record what actually went live. Then decide what the result means. A smaller loop you can repeat is more useful than a large content system you cannot trust.

Most of Sendezeit came from work I was already doing badly in separate tabs and documents. I am still testing what converts, what deserves automation and what should stay a human decision. If you publish your own product, I would rather hear where your workflow breaks than get a generic compliment. You can find Sendezeit at sendezeit.app and follow the build at x.com/antonships.