Late 2025, I spent two months building out BlockPR's back end. A Sales Hub that tracked every lead and follow-up through Taskade Genesis. A Marketing Engine with a fixed weekly rhythm: proof on Monday, insight on Tuesday, a crisis case study on Wednesday, founder voice on Thursday, a conversion asset on Friday. A Reporting Engine that generated weekly summaries of coverage, leads, and revenue. An affiliate tracking system, refSTARS, so partners could see their numbers without asking me.
On paper it looked like a company that had figured itself out. Three pillars, Sales, Marketing, Operations, each with its own rhythm and its own automation layer. I wrote about it at the time like it was already working at full tilt, a team of five doing the output of fifteen.
That framing was ahead of the truth. The systems were real. I built every piece of them. What I glossed over is the part that matters more: building infrastructure and running it with discipline are two different skills, and I am much better at the first than the second.
What the systems actually did
The Sales Hub worked exactly as designed for a while. Every lead had a stage, a next action, a date. No more losing a conversation because it lived in someone's memory instead of a system.
The Marketing Engine's weekly rhythm produced good work when I sat down and followed it. The problem was never the framework. The problem was consistency, showing up for Wednesday's crisis case study even on the week nothing dramatic happened, or writing Friday's conversion asset when a client call ran long and the day got eaten.
refSTARS solved a real annoyance: partners used to ask me for updates on deals they'd referred, and I'd dig through messages to answer. Once it was built, that friction disappeared.
The part I didn't say out loud
A system doesn't run itself just because it exists. I think a lot of founders, myself included, want to believe that once the infrastructure is in place, the hard part is over. It isn't. The infrastructure removes friction from the work. It does not remove the need to actually do the work, on schedule, every week, whether you feel like it or not.
I built a five-day content rhythm and then some weeks published two of the five days. I built a lead tracker and then some weeks didn't update it for ten days at a stretch. None of that means the systems were fake or the writing was dishonest. It means I confused the existence of a good system with the discipline to run it, and those are not the same thing.
What I'd tell someone building the same stack
If you're setting up something similar for your own agency or company, the system design part is genuinely not that hard. Map your repeating tasks, put them in a shared workflow, automate the tracking and reporting so nobody's chasing updates. That part took me a few focused weeks.
The part that takes longer, and that no one writes case studies about, is building the personal discipline to run the system after the novelty wears off. That's not a tooling problem. Taskade Genesis, or whatever you use, can only hold the structure. It can't make you sit down on a Wednesday and write the case study you don't feel like writing.
I still think operational leverage, building something once so it delivers repeatedly, is the right direction for a service business like BlockPR. I just no longer think the system is the hard part. The hard part is the same as it's always been: showing up on the days the system says to show up, especially the ones where nothing is pushing you to.
Share this post