Why a "coming soon" page can hurt your credibility more than having nothing live

A "coming soon" page reads, on its face, as a harmless placeholder — a way to hold a spot on the site for a feature that isn't ready yet without lying about it being ready. In practice it sends a more specific signal to a technical buyer than most vendors intend, and the signal isn't neutral.

What the page actually communicates

An MSP evaluating tooling has learned, usually the hard way, to read a "coming soon" page as one of a few things: the feature isn't built and there's no visible timeline; the vendor is testing demand before committing engineering time to it; or, less charitably, the page exists to make the product roadmap look broader than what's actually funded and staffed. None of these three readings is flattering, and a buyer sophisticated enough to be evaluating a consolidated platform in the first place is exactly the buyer sophisticated enough to reach for the least charitable one by default.

The email-capture form makes it worse, not better, because it reframes an honest gap in the product as a lead-generation mechanism. The visitor came to check whether a capability exists; they leave having been asked to trade their contact information for the privilege of being told later. That's a bad trade from the buyer's side, and buyers notice bad trades.

The alternative isn't silence, it's specificity

• Say what phase the capability is actually in — on the roadmap, actively being built, available on configure, or live in your own practice today — and mean each label precisely enough that a reader could catch you if you mislabeled one.
• Show your build-phase sequence publicly rather than implying every module is equally close to shipping. A reader who can see the phases can calibrate their own expectations instead of guessing.
• Let a reader verify a claim rather than asking them to trust it — point at a test count, a changelog entry, or an architectural fact they could confirm themselves, instead of adjectives.

The visitor came to check whether a capability exists; a coming-soon-with-email-capture page asks them to trade contact information for the privilege of finding out later.

We've made exactly this mistake ourselves and corrected it — a previous version of our own site described nearly every module the same generic way, with an email form attached, and we changed the labeling once it stopped matching what was actually shipped in our own practice. We'd rather a reader catch us being vague again and tell us, the same way outside review caught it the first time, than keep a page that reads better than it's true. Right now that means: Nexus is in private beta with a limited design-partner cohort, no public pricing, module labels updated as the build phase actually changes underneath them — nothing dressed up past what's real.