Company

What “specification-stage” means (and why we say it)

A note on publishing a product site before the product exists, and the lines we will not cross to make it look finished.

This site describes a product that does not exist yet. That sentence is unusual enough to require an explanation.

Most software marketing implies more than it has built. Screenshots are mocked up, logos are aspirational, and “trusted by” sections appear before the first customer. The conventions are so common that buyers discount them automatically. We would rather not add to the noise.

What we mean by specification-stage

Specification-stage means the product is designed and documented, but not implemented. There is no production service, no public API, no certification, and no paying customer. The playground is a static mockup. The pricing page describes planned tiers, not current offerings.

We publish the specification because it is useful before code exists. Editors can tell us the framework is wrong. Engineers can tell us the API contract is unworkable. Procurement can tell us the security model is missing something. Feedback is cheaper now than after build.

What we will not claim

  • Customers we do not have. No logos, no testimonials, no “trusted by” bar.
  • Certifications we have not earned. SOC 2 is in progress, not achieved.
  • Accuracy figures we cannot evidence. Targets are labelled as targets.
  • Coverage we have not validated. “50+ languages” is a target, not a current capability.
  • Press coverage that does not exist. The press page lists our own announcements and says so.

Why the honesty is hard

Honesty is commercially inconvenient. A site that says “not available” converts worse than one that says “book a demo” and implies a working product. Every page here has a version that would perform better in a funnel and worse in a procurement review.

We are optimising for the second review. A newsroom that discovers the gap between the marketing and the product will not trust the next claim. The trust cost compounds.

What “available at launch” means

It means the capability is specified and intended for the first public release. It does not mean it is built. Where a feature is in development, we say so. Where it is only specified, we say that instead. The labels are defined on the integrations page.

How to read this site

  • Product pages describe the intended design, including limitations.
  • Trust pages describe commitments and current status, not audited facts.
  • Pricing describes planned tiers; nothing is billed.
  • The playground is a labelled mockup and sends no content anywhere.
  • Case studies are illustrative scenarios, not customers.

When the status will change

We will change the status when three things are true: a pilot is running with a named partner who consents to publication, an independent evaluation has been completed, and the security and accessibility claims have evidence behind them. Until then, the banner stays.

If you see a claim on this site that looks overstated, email transparency@mediameter.eu. We will correct it or explain why it stands. That offer is part of the product, not a support formality.

MediaMeter Editorial

Written by the MediaMeter editorial team. We publish our methods, limitations, and corrections.

https://mediameter.eu/resources/blog/what-specification-stage-means/
Newsletter

Monthly notes on journalism quality.

One email a month. Methods, limitations, and what we are learning. No product spam.