Beyond support tickets — what does the ongoing relationship look like? Roadmap visibility, QBRs, a voice in what you build?

The full executive answer

For founding customers, the relationship is the closest thing to a product advisory seat you will get from any vendor: quarterly business reviews with me, run on real data — your adoption bands, your NPS responses, your usage against the journey stages — because the analytics that make a QBR substantive are native to the product. Feature requests from founding customers are not tickets in a queue; they are conversations that visibly move the roadmap, and that influence is a deliberate part of the founding-customer value exchange.

On transparency: the public changelog is a curated, append-only, product-level narrative — the edited story of what changed and why, not a raw commit feed — and it already carries the release history. Status, SLA, and trust pages complete the picture: the operating posture is that customers should never learn something important about us later than the public does.

Roadmap honestly stated: QBRs today are founder-delivered, which caps how many customers get the full treatment — that is a feature of the founding tier and a constraint of the stage, both at once. As the customer team builds, the cadence formalises: named CSM, structured QBR deck generated from the same in-product analytics, and a published roadmap process. The instrumentation for all of it exists now; the ceremony scales with the team.