Cog Mission adventure · 6 years
Royal-T
Publishing royalty management — SaaS for authors, estates, and publishers who need clarity.
Royalties should not require a forensic accountant and a prayer. Royal-T tracks publishing rights and payouts so creators can focus on the next book, not the last statement.
Six years in, Royal-T is the quiet infrastructure behind royalty workflows — built for people who care about accuracy more than dashboards.
1 · Listen
Accuracy beats dashboards.
We listened for the statement that never matches the contract.
One engagement dropped us into the middle of a massive backlog of held funds and a paper-to-digital migration that was supposed to take eight months but had stretched into a grueling three years.
When a problem is hurting the bottom line, you don't start with reports—you start with trust.
Before we touched the data, we made one promise to the management team: this wasn't going to become a blame session. No one was going to punch below the belt. Everyone would speak in "I" statements so ideas couldn't be buried under accusations.
By removing managerial oversight from the working sessions, we gave the people closest to the process permission to be honest. The conversation shifted from defending decisions to solving problems. As the team experimented with the data, we helped them find the precise language to describe what was actually broken. That clarity—not another dashboard—became the turning point.
2 · Learn
Patterns matter more than anecdotes.
We write down what people actually said — not what we wished they had said.
When you are managing 60,000 international authors, their beneficiaries, and a catalog of 20,000 products, a single systemic error can quietly flip payment lines, accidentally sending US dollars instead of local currency across borders. We look for the "thorn"—the kind of deeply embedded issue that will keep causing constant, painful irritation until you finally step in with tweezers to pluck it out.
That pattern becomes the brief — not a slide deck for stakeholders who were not in the conversation.
3 · Build
When the stakes are high, you don't need more consultants. You need an A-Team.
We rolled in with ours.
Not because we had all the answers, but because we knew the answers were already in the room. The people processing transactions every day understood every workaround, every bottleneck, and every compromise the system had forced them to make over the years.
Our job was to listen, earn their trust, and build Royal-T with them—not for them. (A little homage to Mr. T felt appropriate.)
Together, we replaced years of accumulated complexity with simple screens, straightforward code, and workflows that matched the way people actually worked. Every feature had to answer one question: Does this help someone do their job with more confidence and fewer mistakes? If not, it didn't make the cut.
Royal-T wasn't designed to impress visitors. It was designed to disappear into the work.
It became the quiet infrastructure behind accurate numbers, smoother operations, and faster decisions—the kind of software people rarely talk about because it simply does its job. We pity the fools that mistake flashy interfaces for real value.
4 · Measure
Peace Filled Dreams.
We care about time returned, stress removed, and trust rebuilt.
Hundreds of thousands of dollars sat frozen in uncertainty. Every unanswered question followed her home. Every delay became another sleepless night, another "what if?" that refused to stay at the office.
The day those funds finally began flowing exactly where they belonged wasn't just an operational win. It was the first peaceful night's sleep she'd had in months. That's the scoreboard we care about. If the technology isn't helping people close the laptop, quiet their mind, and wake up ready for tomorrow, we're not finished yet.
And if our scoreboard doesn't match real life... We pull up another chair. And listen again.
5 · Improve
Iterate out loud.
When Royal-T shipped, we didn't declare victory—we went to lunch.
The people who helped us build version one are still sitting at the table deciding what ships in version two. Around here, feedback isn't a support ticket. It's tomorrow's blueprint.
Every idea goes onto a deliberately short "Wouldn't It Be Cool If..." list. Then we argue about it—in the best possible way. We ask questions. We challenge assumptions. We sketch. We throw away more ideas than we keep.
We've learned that every unnecessary feature is tomorrow's technical debt wearing a clever disguise.
Royal-T is happily humming along because we've resisted the urge to build everything. We build the next right thing. No architectural monsters. No feature bloat. No "while we're at it..." meetings. Just a small group of people who still love solving the right problems together.
And if Mr. T taught us anything, it's that every great A-Team knows when not to blow up the building.