I run more moving parts than any one person should try to hold in their head. A security audit tool. A business intelligence platform. A client automation product. A translation platform. A deck generator. An education tracker. A managed services arm. Ghostwriting and publishing work on top of all of it.
For a long time I ran that from memory, a stack of browser tabs, and whatever notebook was closest. That worked until it didn't. So I built Meraki Command.
What it actually is
Meraki Command is the internal system that sits above everything I build and everything I run for clients. It is not a single app. It is the layer that watches all the other apps.
Under the hood it pulls from a few places I already had running:
Canopy Guard, the audit tool that scores a site across SEO, AEO, GEO, and security using a MITRE ATT&CK informed methodology. Every audit that runs feeds a lead into the system automatically.
Meraki BIP, my own business intelligence platform, where I track leads, client progress, and the actual numbers behind the business. This was already internal facing. Meraki Command sits on top of it and pulls the signal forward instead of making me go dig for it.
VeloxSync, the client facing back office automation product. Different job than BIP. BIP is me watching my business. VeloxSync is what a client's team uses to run theirs.
Meraki Lingua, the multilingual content platform, and Meridian, which turns a business file into a board ready deck. Both get status pings into Command so I know when a job is stuck versus when it's just running long.
VeloxSync for Education, tracking grade band student progress for the education side of the client base.
White Glove Service, the managed implementation arm for SMBs who need someone to actually do the setup, not just hand them a tool.
And then the parts of the business that never fit neatly into software at all. Ghostwriting and publishing work for a small roster of authors. That work does not run through dashboards. It runs through deadlines and drafts. Command tracks those too, alongside everything else, because a missed manuscript deadline matters exactly as much as a missed deploy.
Why I built it instead of buying something
I looked at project management tools before I built this. Every one of them assumed my business looked like one thing. A dev shop, or an agency, or a SaaS company. Mine is all of those at once, plus a security practice, plus a writing career. Nothing off the shelf was built for a business that shape.
The other reason is the audit pipeline. Canopy Guard produces a real, structured finding for every site it touches. Exposed files, missing SPF records, weak DMARC setups. That data needs to turn into a next step without me manually copying it somewhere. Command is where that handoff happens. An audit finishes, the finding gets scored, and if it clears a threshold, it becomes a tracked opportunity instead of a PDF sitting in a folder.
How it's built
Vercel on the frontend, Railway running the backend engine, the same pairing Canopy Guard itself runs on. Resend handles the transactional layer, report delivery and the follow up flows that fire in the first 24 hours after an audit. Google Calendar is wired in with color coding by category, technical sessions, social posts, DNS work, outreach, profile updates, so a glance at the week tells me what kind of day I'm walking into before I read a single event title.
None of that is exotic. The value isn't the stack. The value is that it's one place instead of eight.
What changed after I built it
The biggest shift wasn't speed. It was that I stopped losing things. A lead from an Alignable audit doesn't sit unanswered because I forgot which tab it was in. A ghostwriting deadline doesn't quietly slip because it lived in a different mental bucket than the client dashboards did.
If you're running more than one product or more than one kind of client work, you already know the real cost isn't the work itself. It's the tax of holding all of it in your head at once. Build the thing that holds it for you.
I'm still adding to Command as the business grows. If you're building something similar, I'd like to hear how you're handling the handoff between an automated finding and an actual human follow up. That's the part I'm still tuning.
Top comments (0)