ROAM
Product Narrative / Category Positioning / Perception Architecture
2024
Remote work had fragmented team presence across a dozen tools without replacing what those tools couldn't replicate: the ambient awareness of being somewhere together. Roam was built to address that gap.
To build a product narrative that communicated Roam's actual value - not as another collaboration tool, but as an experience layer for how remote teams exist together.
The virtual office category had accumulated enough failed attempts that the concept itself carried scepticism. Roam needed to be legible as a distinct proposition rather than another iteration of the same idea.
To separate Roam's positioning from the feature-comparison logic that dominates the category - shifting evaluation from what the product does to what it changes about how a team feels.
The product's value was experiential rather than functional. Communicating that value required language that described a feeling without sounding like marketing - a constraint that most tools in the category had failed to navigate.
The diagnosis was a category problem: Roam was being evaluated against Zoom and Slack on feature terms it was not designed to win. The product was not a better video call or a better chat - it was a different claim entirely, and the existing narrative made that distinction invisible. Rather than competing on capability, the engagement repositioned Roam around the problem it actually solves: not how remote teams communicate, but whether they feel like a team at all. The map-based office, the drop-in presence, the ambient awareness - repositioned as architecture of belonging rather than a bundle of features. This produced a narrative in which Roam's simplicity relative to best-in-class tools became a feature rather than a liability - the signal that the product had made a deliberate choice about what it was for.
Built to communicate warmth and presence rather than technical capability. The system signals that what Roam produces is a human condition, not a software feature.
Calibrated to feel approachable without feeling casual - the register of a product that takes the problem seriously without performing its own sophistication.
Standardised around vocabulary of presence and belonging rather than productivity and efficiency. Each touchpoint reinforces the same claim: that Roam is where a remote team actually exists, not just where it works.
Built around warmth and spatial depth - communicating the feeling of an environment rather than the interface of a tool.
Structured to produce the feeling of entering a space rather than evaluating a product. The experience precedes the feature description.
Motion used to simulate ambient presence - the peripheral awareness of others that physical offices provide and that most remote tools eliminate entirely.
Onboarding redesigned to let prospective users feel the product's core proposition before encountering any feature list - addressing the evaluation problem at the point where the category narrative is most likely to misdirect it.
Trial-to-conversion rates improved following the narrative repositioning, with prospective users demonstrating higher comprehension of what distinguished Roam from the tools they were already using. Churn among teams that had adopted the product for presence rather than feature consolidation was measurably lower - confirming the problem had been audience matching rather than product quality. Roam did not become a better feature set. It became a clearer proposition - which allowed the audience for whom the product was actually built to find it before the wrong comparison made them look elsewhere.
Strategic Review
Every engagement begins with a focused conversation on context and ambition. The objective is to assess structural necessity and partnership fit.