3 ms·

Congratulations on the launch. I have not seen the product, but please treat contacts, accounts and opportunities as very first class if you don't do it already

Congratulations on the launch. I have not seen the product, but please treat contacts, accounts and opportunities as very first class if you don't do it already. Also, make change data capture easier. This will go a long way in doing cohort analysis, integrations and workflows. Make this first class for things like deal stage changes, and make out of the box reports around this

noleary 3y ago
On day one of product design, we decided to track all revisions by default. As you're alluding to, I expect this will make reporting vastly easier. In traditional CRM products, seemingly simple -- and important -- tasks like calculating pipeline at a previous point in time turn out to be really difficult. There's also the non-obvious changes that become really frustrating. To use a SaaS-based example, suppose you wanted to report on historical churn rates aggregated by customer success manager. Seems simple enough ... until you realize that you redistributed accounts and neglected to capture changes to Account Owner. We figured we'd spare our customers the effort of deciding what changes they need to track. We just track it all :)
- neeleshs 3y ago
  This is golden, and not just for reports. If you expose the change data stream as an API, many integrations become 10x simpler for your partners and customers. Providing a consistent definition for read-after-write (or search specifically) will make this even better. This is often problematic because the search index is often a different store and there are lags between primary writes and search index. Many bi-directional integrations need consistent read-after-write capabilities, or at least some way to tell how current the read paths are. I say this as a founder of a company with a significant part of the product doing integrations with other systems. And most are painful.

noleary 3y ago

On day one of product design, we decided to track all revisions by default. As you're alluding to, I expect this will make reporting vastly easier. In traditional CRM products, seemingly simple -- and important -- tasks like calculating pipeline at a previous point in time turn out to be really difficult. There's also the non-obvious changes that become really frustrating. To use a SaaS-based example, suppose you wanted to report on historical churn rates aggregated by customer success manager. Seems simple enough ... until you realize that you redistributed accounts and neglected to capture changes to Account Owner. We figured we'd spare our customers the effort of deciding what changes they need to track. We just track it all :)

neeleshs 3y ago
This is golden, and not just for reports. If you expose the change data stream as an API, many integrations become 10x simpler for your partners and customers. Providing a consistent definition for read-after-write (or search specifically) will make this even better. This is often problematic because the search index is often a different store and there are lags between primary writes and search index. Many bi-directional integrations need consistent read-after-write capabilities, or at least some way to tell how current the read paths are. I say this as a founder of a company with a significant part of the product doing integrations with other systems. And most are painful.