Help needed with Ceasar CRM
Hi,
How do I find contracts for integration development between Ceasar and ERP. Integration already exists need add additional features.
Looking for resources who can help.
[link] [comments]
Hi,
How do I find contracts for integration development between Ceasar and ERP. Integration already exists need add additional features.
Looking for resources who can help.
Reading through the Jobber, Salesforce, and Odoo/Zoho threads that have been posted here recently, there's a pattern that keeps showing up and almost nobody names it directly: the CRM swap rarely fixes the actual leak.
The leak is usually one of two things, and neither shows up on a feature comparison chart.
Ownership, not speed. Most businesses think their problem is "we're too slow to respond." It's actually "nobody is specifically responsible for making sure nothing sits unanswered." Speed only breaks under load, when the person who usually handles it is busy. A CRM can automate a reminder, but it can't assign ownership if the business never assigned it in the first place. Swapping platforms without fixing that just moves the same gap into a nicer UI.
Quotes that go quiet. Almost every field-service and B2B CRM will track a quote once it's sent. Very few of them force a follow-up if the customer goes silent. That silence is where the money actually disappears, not in the CRM you picked. I've seen businesses discover they were losing 15-20% of sent quotes purely to "we sent it and moved on," and no platform swap fixed that until someone made follow-up a required step instead of an optional one.
The businesses in these threads spending months evaluating Salesforce vs HubSpot vs Zoho vs Odoo are usually optimizing the wrong variable. The real question before any of that: what's your workflow when a lead goes quiet, and whose job is it to notice? If you can't answer that in one sentence, the new platform will just make the same gap look more expensive.
Curious if others here have seen the same thing, does a platform migration actually fix this, or does the underlying process problem just follow you to the new tool?
Does anyone have experience with both dynamics 365 CRM and salesforce CRM?
I’m still a novice when it comes to customizing and updating the CRM but I’m finding dynamics not the most intuitive system. And I struggle to make small changes in what we have at the moment. So I wonder if Salesforce is a bit more intuitive or will have the same hurdles. Or is it a skill issue?
Good evening from PA! I’m looking for a CRM that is relatively inexpensive as the one others on my team use is over $100 a month and as a newer agent I’m not quite yet in a position to be able to put that out due to other life circumstances. I understand you get what you pay for- and I do intend as I build my sales and acquire more states to use the same software they do. But at least something for now. I work captive, and with policy holder leads. Thanks!
A while back I posted here about a contrib module I was building called Changelogify.
Someone commented that they liked the idea and would try it once it had security coverage.
Well, it finally does :)
Changelogify now has a stable release covered by Drupal’s security advisory policy.
For anyone who missed the original post, Changelogify automatically captures changes happening on a Drupal site and lets you group them into human readable releases. Things like content changes, module operations, and user changes can become an editable release that you publish as a changelog.
The idea is to bridge the gap between raw logs and the release notes we usually end up writing manually.
Since I first posted it here, I’ve also done quite a bit of work on the module as part of getting it production ready, including:
Drupal 10 and 11 support
expanded event tracking
configuration hardening
better release generation
a draft and review workflow
a themeable public /changelog page
automated testing and CI
Drupal security advisory coverage
Going through the security review process was honestly pretty useful in itself. Reviewers caught things around Drupal conventions, hooks, compatibility, project structure, routing, and testing that made the module better.
So, to the person who said they’d try it when it got security coverage: your move 😄
And seriously, if anyone here uses it on a real Drupal project, I’d love feedback. Especially bugs, missing events you think it should capture, or ways the workflow could fit better into how agencies and Drupal teams handle releases.
Changelogify: Drupal.org/project/changelogify
Install with Composer:
composer require 'drupal/changelogify:^1.2'
I recently started my home service business with my partner (5-6 months), we are just 2, and we’re at the point of needing a platform, and was on the lookout for one. Every time I would search online for a platform it seems like Jobber is always insane with the amount of ads, so I made a trial and a demo and I’m just not happy at all with that price. And the sales rep we did the demo with was quite arrogant when we had a few questions.
Do you guys have any alternatives?
A few alternatives I landed on were Housecallpro, but the Trustpilot reviews seem a bit scary.
We’re also looking into CIientility and are happy with the price and the features for the price, and Workiz, however their price seems to be hidden.
Thank you for any suggestions.
We're a healthcare booking platform in Vancouver, about to roll out appointment reminders and two‑factor auth via SMS (plan to release in 2 weeks). Never done this before, and I'm drowning in provider options – Twilio, Vonage etc, you name it without me.
I don't want to pick something that's cheap at sign stage but becomes a nightmare later with deliverability issues or terrible support when something breaks.
For ppl who've been sending SMS at scale – what's been rock‑solid for you? Anything you wish you'd known before signing up? Hidden fees, integration headaches, regional quirks with phone codes? I'd rather learn from your scars than make my own haha. Cheers!
I've worked with enterprise CRM systems for years and keep seeing the same trade-off: simple systems eventually become limiting, while powerful systems become expensive and complicated to configure.
I'm exploring a different architecture.
Instead of building another fixed CRM, the underlying platform consists of configurable objects, fields, relationships, pages, permissions, automations and reports.
Sales would just be the first module. Support, Projects, Planning, etc. can extend the same underlying customer and business data.
The AI doesn't generate software or arbitrary code. It can only configure capabilities that already exist in the platform.
So you could say:
"Add contract value to companies, put it next to ARR, and create a follow-up when an opportunity stays in Proposal for 7 days."
The system creates a plan → shows exactly what will change → validates it → you approve it.
The part I'm most interested in is migration. Rather than asking a company to make a big-bang switch, the idea is to analyze the existing CRM, map its objects/fields/processes, preview the new setup and eventually allow teams/modules to migrate progressively.
I've attached a visual explaining the concept.
I'm specifically NOT looking for "cool idea" feedback. I'd like to know: what would make you refuse to switch to something like this? What would I have to prove before you'd trust it with your real business data? And which part of this sounds less useful than I think it is?