27 July 2025
How we think about the roadmap
Our roadmap is shaped by 50% customer requests, 30% data signals (which features get used), and 20% taste. We don't outsource our taste. Here's what we say no to, and why.
Three inputs
- Customer requests. Every tenant call ends with us asking "what would change your day this week?" We log every answer in Linear. Recurring requests across 5+ tenants get prioritized.
- Data signals. We watch which features get used. If we ship something and 30% of tenants haven't touched it in 60 days, we either fix the discoverability or kill the feature.
- Taste. We decline some customer requests because they'd make the product worse. The current example: we declined a request for a "loyalty points" module because we don't believe in adding plastic gamification to flower-buying. The shops who want it can use a third-party loyalty integration.
What we say no to
- Anything that takes the customer relationship away from the shop. We don't do consumer aggregation. The shop owns the customer.
- Anything that dilutes the brand. We won't white-label Floree as "FlowerOS" or whatever a partner wants. The mark stands.
- Anything that's adjacent without being core. We won't build a CRM. We'll integrate with one.
- One-off enterprise customizations. Every customer is a tenant; tenants don't fork the codebase.
What's on Q3 2025
- Driver app + dispatch routing
- Self-serve corporate portal
- KSA Saudi VAT (15% vs UAE 5%) full support
- A small POS hardware leasing line for shops that don't want to buy outright