The stack I came from

A content calendar in Notion is genuinely beautiful, and for a few weeks it is a pleasure to use.

Like most people, I started here. I built a content calendar. It was beautiful for about six weeks. Then it got unwieldy, then it got abandoned, then I rebuilt it, and that one got abandoned too.

The thing I eventually understood is that it did not do the work. It gave me more work to do. Every episode meant new rows, new statuses, new links to paste in. The calendar was a second job that existed to remind me about the first job.

A system that only tracks work is not a system. It is a to-do list with better formatting.

A genuine upgrade on what I was doing before. The forms and the triggers were the part that earned their keep, and I got real mileage out of both.

Airtable came next, and it was a real step up. Forms to collect things, triggers to move them along, a structure that held together better than the calendar it replaced.

What happened then was not that Airtable let me down. It is that pushing on it taught me what my workflow actually was, and what worked for me and for the people around me.

Once I understood that clearly enough, building the product turned out to be easier than continuing to assemble it.

For storing and sharing files it is free, universal, and everybody already has it.

For a long time this was how I handled guests. Episode goes live, I drop the clips and the graphics in a folder, I send the guest a link. Done, I thought.

What actually happened is that guests got a link to a folder and no idea what to do with it. No suggested caption, no drafted post, no sense of what would help. The people with the most to gain from sharing the episode, and the biggest audiences, got a URL and a shrug. Most of them did nothing, and I do not blame them. I had given them a chore.

That failure is the reason Convia drafts posts for guests rather than handing them assets.

Approvals, comments, and seeing the post the way it will actually look. If you are a team passing content back and forth, it is a good tool and I would still recommend it for that.

The first content team I worked with used Planable, and we collaborated in it. It genuinely worked.

But it had no sense of who I was. Every post started from an empty box. The tool knew about posts and approvals; it did not know about my show, my guests, my topics, or the fact that I had already said this thing better four months ago.

There was no content management underneath it and no intelligence behind it. It was a very good surface with nothing behind the surface.

The queue model is genuinely smart: you set your posting times once and then stop thinking about scheduling, which is exactly what you want when the hard part is consistency.

I moved to Buffer for scheduling and stayed a long time. It is one of the best-run products in this category.

Two things pushed me off, and neither is Buffer's fault. The first was arithmetic: Buffer prices per channel, and by the time I was running eight I was paying close to a hundred dollars a month for scheduling alone, while still writing every post myself.

The second mattered more. Buffer could tell me a post did well. It could not tell me that a particular topic outperformed everything else, or that something I said in episode fourteen deserved a second run. It knew about posts. It did not know about my show.

The generation was never the problem. It is good enough that some of our thumbnails are showcased on their product page.

I still like this one. Some of our thumbnails are showcased on their product page.

What I needed and could not get was the surrounding infrastructure: sending my brand assets once instead of every time, using multiple headshots depending on the format, and having everything catalogued so I could find what I made three months ago.

This is a pattern I hit over and over. The hard part of most of these tools was not the thing they did. It was everything adjacent to the thing they did.

If your process is well defined and you enjoy building, n8n will take you a long way for very little money. The versatility is remarkable and I am still a genuine fan.

This is where Convia actually started. Before there was a product, there was a set of n8n workflows I built for myself: get the episode, pull the transcript, generate the posts, push them out. It worked.

I hit two walls. The first was context: my workflows could move data but could not hold anything. Every run started from zero. Every improvement meant another node and another branch, and the whole thing got more brittle as it got smarter.

The second was the platforms. Publishing to eight places is not eight API calls. It is eight sets of rate limits, eight token refresh cycles, eight media specifications, and eight sets of requirements that change without much warning. I was spending more time maintaining publishing plumbing than making content.