81–90 of 105 posts
Going through auth by clicking on Google Sign in to be met with "Please sign up with you work email" is pretty poor CX.
However, for context, we neither offer self-service onboarding nor a free tier.
As someone who finds even guided tutorials annoying, I appreciate that a hands-on sale and implementation isn't right for everyone, but we're confident that's the right approach for our business.
What this really does is prove the commoditization of the generic SFDC approach to "CRM", where it's horizontal and empty. It's price pressure for force.com, hence their push on "AI" and add-ons, to protect 30bn in revenue. HubSpot is easier to defend as you get far more OOTB business functionality, rather than a generic, un-opinionated toolbox. Attacking SFDC via your route is like attacking Excel with a barebones t…
New players will look like CRUD apps with the horizontal platform approach, and will have a hard time unseating existing big players.
But, the more the merrier. Congratulations and wish the authors the best!
Going through auth by clicking on Google Sign in to be met with "Please sign up with you work email" is pretty poor CX.
Thanks for letting us know; we can probably improve that message. However, for context, we neither offer self-service onboarding nor a free tier. As someone who finds even guided tutorials annoying, I appreciate that a hands-on sale and implementation isn't right for everyone, but we're confident that's the right approach for our business.
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
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
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 :)
Salesforce's "killer" feature really is the Custom Object. You can create a new data model, customize a UI and have a production API up and running immediately. I've been wondering when someone would attempt a modern take on this, and this seems like a decent start (from what I can tell in the video, login doesn't work).
Competitors like Hubspot do provide better functionality OOTB, but as soon as you want to automate or integrate, you quickly realize that they haven't "doggedfooded" their API's. Most business's of moderate size & complexity will eventually outgrow the platform.
> One thing we can’t decide if it’s a need-to-have is Apex
You might start with the just more serverless style event hooks that fire after the DB commits, but eventually you will need something that can be more "transactional".
But please... for the love of god... do not roll your own language like apex. Just pick something like typescript and sandbox it.
Same goes for UI components. Don't build your own crappy web component framework... Just figure out how to allow custom react/svelte/etc components to be embedded.
Other thoughts:
- Don't wait to nail down your access control model. One of the most daunting aspects for Salesforce Admin is designing the access control and entitlements model. For Custom Objects make sure to cover both FLS and RLS. IMO, the Salesforce approach here is pretty good, but just the admin UX is an absolute fire full.
- IF you build a low code workflow tool, enable it to transpile to a simple text based language and back. Salesforce Flow is a nightmare to maintain because the visual abstractions mask the details and make it impossible to construct a mental model.
- The SF metadata and deployment model has caused so much pain and they've still never been able to fix it. IaC style configuration could solve a lot of these problems, but I expect it will be a big challenge.
Congrats on launch. This is a space I've thought about a lot in my 12 years as CTO of a consulting agency that centers around Salesforce. Salesforce's "killer" feature really is the Custom Object. You can create a new data model, customize a UI and have a production API up and running immediately. I've been wondering when someone would attempt a modern take on this, and this seems like a decent start (from what I can…
Would handle all the challenging infrastructure & non-functional areas and just let you focus on writing code for workflow, integration, etc.
I've done some work with salesforce integrations and from my perspective, the pain comes in when trying to keep a bi-directional link between data in the CRM and data in the custom backend systems. At least in my case, there is a desire for a low latency sync so that the two data sources are as similar as possible. Salesforce, with its batch loads, open api spec, soap/rest api and 'use mulesoft' approach makes this p…
{ "error": [ "Your account has been locked for security reasons. Please reset your password." ] } And that's what I can see in network inspector, while the UI just does nothing after clicking on "Login" button.
Should be healthy again, sorry!
> We think the way you win in CRM in 2024 is by keeping the flexibility of SObjects, and then tacking on modern UX. What is driving that thinking? Is it something the market is asking for? > Salesforce is slow and clunky. And that doesn’t matter because people don’t buy Salesforce to be delighted. So if they are buying it despite bad UX, it stands to reason that UX isn't important to them. Who does your CRM attract,…
CRM space is very red ocean, so IMO a differentiator is required. Remember that these are tools that help people sell more, so that does need to be the focus.
e.g. "We are the CRM that caters to the needs of the domestic cleaning market" or "We are the CRM that automatically arranges sales calls in your diary".