One of the first problems we’re tackling at Revster is the problem of remote teams having trouble keeping key stakeholders up-to-date on key topics that they need to be informed on.

This is a problem that we’ve validated consistently across growth company executives. On any given day, in any given meeting, topics are discussed, insights are uncovered, and decisions are made without the knowledge of people who should be informed or consulted. This importantly isn’t because of any need to contain information. It’s simply due to the friction involved in keeping all key people in the loop.

For example, a sales call might uncover some information about a competitor that a product manager really wants to know.  An internal meeting about a customer deployment could uncover an insight that marketing needs to action on. Dozens of conversations happen that senior executives might want to get summaries of, but never do. The org moves on and the information typically dead-ends inside a few heads. So much lost insight!

So, how do you keep key stakeholders informed? Our first product will work on this problem by building on a  conversation topic architecture. In any given conversation, several topics might be covered: sales, competitors, customer health, project status, marketing, product features, etc. Just like people can join slack channels based on a topic, Revster will allow people to be added to topics, and receive relevant updates and summaries of conversations that happen across the org that relate to the topic. Users can choose how and what format they receive updates, and they can be adjusted based on the topic.

This is more complicated than it sounds. How does an organizer know what information is ready to share with a group? How does the technology parse what’s important and what isn’t? What’s the best timing and format of informing folks.  These are the problems we’re working to fix, so everyone can be more informed and take action faster.