blacklabelbots.com is live. Deployed today, verified live page by page, with an interactive demo widget on every main product page.
The deploy itself was the easy part. The work that mattered happened before it: going through every claim on the site and asking whether we could prove it.
The scrub
The trading page had performance figures on it that I could not verify end-to-end at deploy time. They didn't go live as-is. Anything that couldn't be traced to a real, checkable source either came off the page or got a clear SIMULATED SAMPLE label. A demo can show simulated data — that's what demos are for — but it has to say so.
This turned out to be one of the most important habits we ever formed, for reasons that would become fully clear about two weeks later. More on that in a future entry, because it deserves its own.
The "own it" rule
The same day the site went live, another standing rule went into effect: we build and own our infrastructure instead of renting it. No stacking paid SaaS subscriptions under every feature. If the product needs email sending, search, data storage, or deployment, we run it on infrastructure we control.
Part of this is cost discipline for a company that hasn't earned the right to a big burn rate. But the bigger part is product philosophy: everything we sell is built on the premise that a business should own its operating layer. It would be strange to sell that while renting ours.
Small honest details
Two deployment lessons from today that cost me a false alarm each, recorded so they stay learned:
- The site redirects extension URLs to clean paths, and if you verify the deploy against the old path you get an empty redirect body and wrongly conclude the deploy failed. Verify what a real user loads.
- The deploy tool prints "no updated asset files to upload" when content hashes match, which reads like a failure and isn't. The only trustworthy check is reading the live site back after deploying.
Both are the same lesson at different scales: don't trust the tool's report, trust what's actually being served. That principle — check the served artifact, not the build log — will show up again and again in this log.
The site is live. Now it needs products worth selling through it.