Thread by @mattgoldenberg

1/ Despite all appearances, @RoamResearch has not yet reached product market fit. It's reached what @ashmaurya calls "Problem / Solution fit."

Problem: Unstructured Data
Solution: Block level notes and bidirectional links.

https://twitter.com/fortelabs/status/1232718617298366464

2/ Like @Superhuman , they're solving a pressing problem, so there's lots of signal. But @Conaw has realized that the signal has lots of "it's so good BUT" in it, even from most excited users. A sure sign that P/M fit is not there yet. Hence no $ yet.

firstround.com/review/how-sup…

3/ My guess of remaining things Roam needs to reach P/M fit.

1. Discoverability. UI elements for all major functions.
2. Onboarding. A way to quickly show power of platform.
3. Mobile.
4. Page synonyms/aliases

4/ A potential 4th and 5th is speed and stability, but these are always moving targets as Roam moves "upmarket" into larger and more enterprise deals.

5/ It's worth noting that @RoamResearch has been making huge strides towards P/M fit as they go. For instance for a while I would have said "Better Export/Import" was needed, but they've since created best in class import/export.

6/ I should also note that I don't think all these features will make @RoamResearch a @NotionHQ /@coda_hq competitor, except for people that have been using those platforms wrong.

They excel at structured data, Roam, at unstructured data.

7/ To reach Problem/Solution fit for structured data, Roam will need to make attributes and components first class citizens, something much more like Coda's tables and views.

And then they'll have a whole lot more work to get to Product/Market fit for that class.

8/ This isn't a callout of Roam btw. I love @Conaw and am #roamcult for life. I want to see Roam take over both these categories and revolutionize the data paradigm of the internet. I truly think they can make it happen.