Roadmap.
What the Sprout team is working on now, next and later. Direction, not promise — when something ships it moves to the changelog, and when priorities shift, this page changes in a reviewable MR like everything else.
Now
0–6 months
Strategy & design principles published
Shipped · v3.7.0The eight principles, the five trust pillars and the AI patterns — public on this site, so every team designs against the same floor. Read more →
Tokens package on the Package Registry
Shipped@aceve/sprout-tokens v0.0.2 published — every product can now install the same tokens from one place. Read more →
The AI layer
In progressDisclosure label, receipt card and confidence indicator — the components that make AI trustworthy, ahead of EU AI Act Art. 50 (2 Aug 2026). Read more →
Metric baselines per product
In progressNPS, task-success and support-ticket baselines, so the next redesign can prove its effect instead of asserting it.
Next
6–18 months
Highest-traffic products onto Sprout
PlannedCohort-based, gentle migrations with trade-credible champions and a rollback path — never big-bang. Read more →
The extra apprentice in flagship workflows
PlannedOpt-in AI in one or two high-volume flows (quoting, invoicing), measured on acceptance and trust before it widens. Read more →
Standardised onboarding patterns
PlannedShared first-run and empty-state patterns to cut time-to-value across the portfolio. Read more →
Pages for the twelve undocumented Figma components
PlannedAlert, Select, Textarea, List item, the four button variants, the two skeletons, Media and Carousel all exist in the Figma library but have no page yet. Read more →
Component queue: toast, date picker, combobox
PlannedThe planned tier of the coverage board, in priority order — components that exist nowhere yet. Read more →
Later
18–36 months
New acquisitions inherit Sprout by default
PlannedAdopting the design layer becomes part of integration — quality and consistency from day one. Read more →
AI autonomy: suggest → draft → act
PlannedAutonomy expands one rung at a time, only where reliability is proven and always reversible. Read more →
One coherent Aceve experience
PlannedBrand consolidation across markets — a customer who trusts one Aceve product recognises the same quality in all of them. Read more →
How to read this
Honest by default applies to roadmaps too.
Direction, not promise
Horizons are deliberately coarse — themes, not tickets. The task-level work lives in GitLab where it belongs, and dates only appear here when they are real (like the EU AI Act deadline). A roadmap that overpromises burns the same trust the system exists to build.
Shipped means receipted
Nothing on this page gets to claim "done" quietly: every shipped item points at a version in the changelog, and component maturity always reflects the coverage board — the same status a developer sees before building on it.