Why we publish a public roadmap (and what it costs us)

We publish a quarter-level roadmap at /roadmap. Every item has one of four statuses: shipped, in_progress, next, or future. We update it monthly. We hold ourselves to it.

Why most companies don't do this

• It removes optionality — once you publish 'Q3 2026', a slip becomes a public failure
• It gives competitors a window into your roadmap
• It commits you to the prioritization, even if Q3 brings a market shift

Why we do it anyway

Customers spend money to enter a 4-year vendor relationship. They deserve to know what's coming and when. The cost of public slips is real but it's smaller than the cost of customers discovering a year in that the integration they were promised was vapor.

We've slipped two roadmap items publicly in the last year. Both were honest about why (one was a customer-driven scope expansion; one was a security-review hold). Customers responded with more trust, not less.

If you can't tell me when, the answer is no. We've already been burned by 'AI-powered' vendors who shipped slides instead of code.