How much Sprout is enough?
Aceve ships 28+ products across Europe — different stacks, different customers, different trades. Sprout isn’t a mandate that forces them identical. It’s a guideline that makes them feel like Aceve and lifts UX to a good-enough floor. Start at the base. Climb as far as makes sense for your product.
The adoption pyramid
Pick a level to see what it includes. Wider at the bottom means more products should reach it.
The non-negotiable floor. Adopt Aceve’s colors, type and icons and your product instantly reads as part of the family — before you touch a single component. This is the one level every Aceve product should reach.
What Sprout is — and isn’t
The line between alignment and autonomy.
- The same icons, colors and typography
- Validated components, once they’re ready
- A good-enough UX floor on every screen
- Every pixel of how a component looks
- Your navigation and layout patterns
- How your service actually behaves
The right-hand column is yours. Product teams own how their service behaves — Sprout just makes sure it wears the Aceve face and clears the UX bar.
Why a pyramid?
Three commitments behind the model.
Start at the base
Three pages, and your product already reads as Aceve.