Vote on what we build next.

Three columns rather than four quarters. What is being built right now, what is queued next, and what was cut with the reason attached. There are no dated commitments beyond the current build, because a roadmap full of quarters is a wish list that erodes trust when it slips.

How things get prioritised

Customer escalations outrank feature requests, because an escalation is evidence that something is already broken for someone paying. After that: work that reduces build time, then work that widens the integration surface. Anything that only improves a demo is deprioritised on principle.

The cut column

The most useful column. It lists things asked for repeatedly and declined, with reasoning: outbound campaign tooling without consent verification, undisclosed voice cloning, and per-seat pricing on the self-serve tier. Publishing the cuts saves everyone the sales conversation that ends in a no.

How to influence it

Customers on any tier can file directly. The requests that move fastest arrive with the failing scenario attached — the call that went wrong, the integration that would not map, the report a client asked for. Abstract requests sit; specific ones get scheduled.