Hey everyone,
We just launched Katalyst for sales teams on Salesforce.
Simple idea: reps don't hate selling, they hate the hours they lose every week feeding the CRM. Logging calls, fixing stages and close dates, writing next steps, reconstructing what happened on a deal from three weeks ago. The CRM they "quietly hate."
Most tools just made data entry slightly less painful. It's still the rep doing the work.
Finally ditched my note-taking scribbles mid-call. The follow-up drafts actually sound like me, which is a nice surprise.
Katalyst
@duran257125 Follow-ups sounding like you and not a template was one of the harder things to get right, so that's great to hear. And getting to actually be present in the call instead of scribbling is the real win. Thanks for sharing.
Katalyst
@duran257125 Drafts sounding like you rather than a template was genuinely one of the harder things to nail, so glad it surprised you. And ditching the mid call scribbling means you're actually present in the conversation, which is where the real deal work happens. Thanks for sharing 🙏
Is there a minimum Salesforce edition required? Would it work on Professional or does it need Enterprise?
Katalyst
@vidushi_jalan No edition requirement, it works on Professional or Enterprise alike. It sits on your existing Salesforce as-is, so there's nothing to upgrade before you can get going.
Sales teams already spend too much time updating CRM. If this actually reduces that manual work, it could be very useful.
Katalyst
@letitia00 100%. That's the exact time sink we built it to kill. Reps sell, Katalyst keeps the CRM current.
Katalyst
@letitia00 Exactly the problem we set out to kill, the CRM upkeep is time reps should never have to spend. It captures the work from your calls and emails and keeps Salesforce current on its own, so the selling stays with you and the admin doesn't. Would love for you to put it to the test.
What's the right plan for a team of around 15 reps and 2 managers?
Katalyst
@mehtabbir_singh For a team that size you'd be on our team plan, which scales cleanly across all 17 seats with admins getting the pipeline hygiene and deal pattern views on top of what reps see. Best move: start the free trial (up to 5 users for a month) with a few reps and a manager to feel it on your real Salesforce data, then roll out to the full team. Happy to walk you through pricing directly at joinkatalyst.com.
Is this only for Salesforce? What about companies using other CRMs?
Katalyst
@anant_tantia Salesforce-only for now, that's where we went deep first. Other CRMs are a natural next step and on our radar, but I'd rather do each one properly than half-support a bunch. Which CRM are you on?
@divyansh_lohia We use SAP. But makes total sense with Salesforce being a CRM at core.
Do you plan to introduce the AI functionality accross other ERP platforms for operational and other modules ?
Katalyst
@anant_tantia Great question. The core idea, an agent that keeps a system of record current straight from real activity, isn't specific to CRM, so extending it to ERPs like SAP and other operational modules is very much the long-term direction. We're deliberately going deep on Salesforce first because it's the sharpest and most universal pain, rather than spreading thin too early. That said, SAP is a world we'd love to understand better, so I'm curious which module or workflow eats the most manual time on your side.
Who gets the most value from Katalyst today? AEs, Sales Managers, RevOps, or someone else?
Katalyst
@esha_gosalia Honestly, everyone in the revenue org gets something, but the AE gets the most by far. They're the ones Katalyst sits with all day: it preps their calls, writes their CRM updates, drafts their follow-ups, and tells them what needs attention each morning. That's hours back every week for the person with the least time to spare.
Managers and RevOps win right behind them, because when reps stop hand-updating Salesforce, the data actually gets good. Managers see real pipeline instead of stale fields, and RevOps stops chasing hygiene. But that only happens because the rep loves using it, so rep-first is the whole strategy. Win the AE and everyone upstream benefits automatically.
That queue-with-the-error behavior is the right call, way better than a false green check. The thing I'd poke at: a bounced suggestion can sit in the queue while the underlying opportunity keeps moving, another call gets logged, someone edits the stage. So when the rep finally fixes the value and accepts, are you re-deriving the suggestion against current Salesforce state at accept-time, or writing the value as computed when the suggestion was first made? We got burned by the second version once, wrote a technically-valid but stale field.