Customer feedback
Business reviews, support tickets, and direct requests feed a shared backlog our product team reviews every week.
How we build Cohesion
How we build Cohesion
Every release starts with a real workflow problem in a building. We validate it with customers running Cohesion today, ship in small increments, and expand based on what actually gets used.
We ship weekly. Every release, big or small, is documented in the changelog.
How a feature goes from idea to release
New capabilities move through the same process, whether it's a small fix or a new product line.
Gather input
Requests come in through customer success calls, support tickets, advisory engagements, and usage patterns in Savvy.
Prioritize
We score requests against portfolio-wide impact and the themes already on the roadmap, not just the loudest ask.
Build and beta
Engineering ships the smallest version that solves the real problem, then a subset of customers try it in a live portfolio.
Ship and track adoption
The release goes out, gets logged in the changelog, and we watch usage to confirm the workflow lands the way it was meant to.
Release cycle
Our release cadence
We ship weekly, not quarterly. Bigger capabilities land in stages across several releases instead of one big-bang launch.
- 01
Discover
Talk to customers already running the workflow today and confirm the problem is worth solving.
- 02
Design
Scope the smallest version that solves the real problem, using the integration and data model already in production.
- 03
Build
Engineering builds against the existing platform, no separate rip-and-replace effort required.
- 04
Beta
A subset of customers try the feature in a live portfolio before it becomes generally available.
- 05
Ship
General release, documented in the changelog, rolled out building-by-building like everything else in Cohesion.
What shapes the roadmap
Four inputs carry the most weight when we decide what to build next.
Portfolio and Savvy data
Usage patterns across Smart Access, Smart Experience, and Smart Maintenance show where a workflow is still manual and worth automating.
Security and compliance
Requirements surfaced in enterprise reviews and Trust & Security audits shape what ships and when.
Partner and integration requests
New hardware and software connectors usually start as a customer asking for one specific integration.
FAQ
Frequently asked questions
Related
Yes. Raise it with your customer success contact or during a business review. Requests get logged and reviewed against portfolio-wide themes, not just a single ask.
Weekly. Small releases ship continuously, and bigger capabilities land in stages across several releases instead of one large launch.
We share near-term plans directly with customers in business reviews. The Product Releases changelog reflects what has actually shipped.
A subset of customers already running the relevant workflow try a feature in their live portfolio before it becomes generally available.
The Product Releases page lists every release with what changed and which product line it affects.
Have a feature request or a workflow we should support?
Tell us what's still manual today. Our product team reviews every request against what's already on the roadmap.