Why we built Cadenus

We run a video marketing agency. Reels, ads, retainers: the unglamorous, deadline-shaped kind of work where a good month means dozens of videos shipped across a roster of clients, each with their own voice, their own approver, and their own opinion about logo size.

By the time we passed our tenth client, our stack looked like everyone else's: a project management tool that didn't know what a client approval was, a scheduling tool that didn't know what production was, a review tool that didn't know what publishing was, a time tracker nobody filled in, spreadsheets for the money, and WhatsApp for everything that actually mattered.

Each tool was fine. The gaps between them were where our weeks went to die.

The Monday problem

The clearest symptom was Monday morning. It took half a day, genuinely, half a working day, to reconstruct the state of the agency: which edits were stuck, which clients had gone silent on approvals, what was promised for this week, whether the month's money was on track. The information existed. It just lived in six places, none of which talked to each other, and assembling it was someone's unofficial job.

The deeper symptom was that problems reached us after they'd become expensive. A video that sat with a client for eleven days wasn't a fact anyone hid; it was a fact no tool surfaced. By the time it came up on a call, it was an apology instead of a reminder.

Looking for the tool

We did the responsible thing first: we shopped. Configured generic PM tools into pretzels. Trialed the agency-flavored ones. Every option failed the same way: it modeled projects, when an agency's actual atom is the client relationship, their pipeline, their approvals, their channels, their money, their rhythm.

Nothing wanted to be the system where a brief becomes an edit, the edit gets approved by a person who doesn't want another login, the approved cut publishes natively to the platforms, and the whole thing shows up in the month's report and the month's margin. So the work kept fragmenting, and we kept paying for six tools to avoid owning one problem.

Building our way out

We started building in the gaps. First the pipeline, because stuck work was bleeding us. Then the client portal, because approvals were the slowest stage: one secure link, watch, approve or request changes, on the record. Then native publishing, because exporting an approved video from one tool to upload it into another was a daily absurdity. Then the money, because we discovered we couldn't actually say which retainers were worth it.

Somewhere along the way the internal tool got a name, Cadenus, from cadence, the delivery rhythm that is the whole point, and a rule that kept it honest: it had to run our agency first. Every feature was built because our own Monday demanded it, and shipped only when our own team stopped working around it.

Why sell it

Because the problem isn't ours, it's structural. Every video-first agency past a handful of clients hits the same wall, duct-tapes the same six tools, and burns the same Mondays. We'd already paid the cost of building the way out; keeping it to ourselves felt like bad math.

So Cadenus is what it says on the page: the operating system we wish we'd had at our tenth client, still running our agency every day, now open to yours. We onboard founding agencies personally, partly as service, mostly because their feedback is how the product stays honest.

If your Mondays look like ours used to, see how it works, or just start the trial and bring your chaos with you. That's what it's for.

Bogdan Cimpan, founder