Re:Launch HN: Okapi (YC W24) – A new, flexible CRM with good UX
by ucarion on Tuesday March 19, 2024 @05:53PM
(#39760683)
Task management, lists/views, and general "journeys" management are all on the roadmap. There's a lot of stuff you need to do to be generally competent in this space, we're definitely launching very early here.
When I talked about Apex, I really mean the "scripting language that sees data mid-transaction" aspect of the language. Sounds like you're not really seeing the value there either? I totally agree that good old webhooks or some other trigger is seems almost always good enough if the API is fast.
Appreciate the suggestions re: comms and consent management. We're still not sure how we want to handle dialers.
Re:Launch HN: Okapi (YC W24) – A new, flexible CRM with good UX
by ivan_gammel on Tuesday March 19, 2024 @07:30PM
(#39761410)
>I really mean the "scripting language that sees data mid-transaction" aspect of the language. Sounds like you're not really seeing the value there either?
I do see value there as long as it is a general purpose programming language running in your sandbox and not something vendor-specific.
Do you need Apex for that? God, please, no. Apex doubles or triples the cost of Salesforce, because you usually end up spending tens of thousands euro on some agency doing the customization. If you want to compete with SF, offer Java, JavaScript or TypeScript as lambda or managed microservice hosting with fast links to your db/api (and do it better than Heroku). The better are your integration options with custom code, the more attractive it will be for digital services and non-trivial use cases.
I would love to see proper communication management respecting user subscription preferences and consent. Maybe look at Braze for that. If you could handle the calls, both inbound and outbound, internationally and with power dialer that would be awesome.