Skip to content
All notes
OPERATIONS

OCT 2026 · 6 MIN

Check the software you already pay for first

Most teams don't have a missing-software problem. They have three settings turned off and a habit nobody wrote down.

By Daniel Barraza · dbar Labs · Boerne, Texas

When a business owner calls dbar Labs about AI, they usually think they're behind because they haven't bought a new tool yet.

Someone in their peer group just signed up for an AI receptionist, a custom CRM integration, or a monthly automation wrapper. Meanwhile, their own team is still copying notes between tabs, chasing missed clock-ins, or re-typing the same customer info three times a day. So the instinct is natural: we need to buy something new.

Most of the time, that instinct is expensive and wrong.

When we run a $249 AI Opportunity Audit, we follow a strict order of operations before we ever recommend custom code or a new monthly subscription:

  1. Fix the process first (who owns the step, what facts are required upfront).
  2. Use and train on the tools you already pay for.
  3. Configure existing settings that are quietly sitting turned off.
  4. Buy a proven off-the-shelf tool only if the current stack genuinely can't do the job.
  5. Integrate or build custom software only when the math clearly pays back the build.
  6. Change nothing when the volume is too low to justify touching it.

Steps 1 through 3 aren't as flashy as a custom bot. They also solve about half of what people think they need AI to fix, usually for $0 in new software spend.

Why good software looks broken in the real world

Software vendors love selling features on a demo call. They're much worse at helping a four-person office configure those features two years later when staff has turned over, mobile carriers have changed how text messages get delivered, and everyone is just trying to survive Tuesday morning.

Over time, a quiet gap opens up between what your software can do and how your team actually uses it at 8:15 a.m. When that gap gets painful enough, teams assume the software is broken, or that they need an AI layer on top of it.

Before you spend a dollar on new tools, look at three everyday examples of how this actually plays out.

Example 1: The clock-in problem that isn't a caregiver problem

Take a typical scheduling workflow in home care or field services. A coordinator spends the first two hours of every morning calling field staff who didn't clock in on the mobile app, then spends Friday afternoon manually fixing timesheets so payroll and billing match.

On the surface, it looks like a staff compliance issue, or an excuse to buy an automated AI outreach tool to chase late check-ins.

Then you trace what actually happens on a shift:

  • The building blocks the signal. A caregiver walks into a large assisted-living facility with thick concrete walls. Satellite GPS drifts by 150 feet. The scheduling system's default geofence is set to a strict 50-foot radius, so the app rejects the clock-in. After failing twice, the caregiver gives up and texts the office.
  • The alert goes to the wrong person first. The software is set to ping the office scheduler the minute a clock-in is late, instead of texting the caregiver 10 minutes before the shift boundary so they can fix it themselves.
  • The alert delivery path quietly died. Years ago, someone set up mobile alerts using email-to-text gateways (like @vtext.com or @txt.att.net). Carriers have shut those gateways down or throttled them heavily, so half the reminders never arrive.
  • The dashboard hides the why. The live schedule screen has a column that shows the exact exception reason (GPS distance vs. late arrival vs. wrong device) but that column is unchecked in the default view. So the scheduler makes 15 blind phone calls every morning.

Not one piece of that problem requires buying new software. It requires switching on Assisted GPS (so the app reads Wi-Fi and cell towers inside big buildings), routing the first reminder to the worker via direct SMS, turning on the landline phone-in fallback for dead zones, and checking one hidden column on the dispatch screen.

Software cost: $0. Time saved: hours every week.

Example 2: The quote bottleneck that isn't a CRM problem

Or look at a small insurance or service agency with an owner and three producers. Quotes are taking too long to turn around, producers are re-keying the same household details across carrier portals when a first-choice carrier declines, and warm prospects are going cold after the first quote goes out.

Meanwhile, one person on the team is paying $20 a month out of pocket for a personal ChatGPT account and pasting rough call notes into it to draft follow-up emails, with no shared rules on what client data stays out of the prompt.

If you jump straight to "let's build a custom AI integration between our phone system, our CRM, and our carrier portals," you're going to spend thousands of dollars automating a messy intake habit. Worse, you risk putting an automated tool near coverage advice or binding decisions that legally and practically belong with a licensed human.

When you look at the workflow step by step, the first moves are much simpler:

  • Stop starting quotes with half the facts. If a producer takes an inbound call without capturing the six basic underwriting facts upfront, they have to call the customer back twice before they can even quote. A one-page intake checklist next to the phone fixes more delay than any software bridge.
  • Turn on native follow-up ownership. Most agency CRMs already have a task owner and a "quote sent, 48-hour follow-up" status built in. If nobody assigns the owner before hanging up, leads sit in a shared inbox because everyone assumes someone else called them back.
  • Put clear guardrails around drafting tools. Using AI to clean up internal call notes or draft a plain-English renewal email is genuinely useful, as long as personal identifiers stay out of consumer tools and a licensed human reads every word before it goes to a client.

Once the intake facts are clean and follow-up ownership is clear, then you can measure whether re-keying across portals still burns enough hours to justify a scoped automation build.

Example 3: A 15-minute audit you can run on your own stack today

Before you book a demo with a software vendor, or even before you book an audit with us, pick the one workflow in your business that annoys you most on a Monday morning and ask four questions:

  1. What are we typing or asking for twice? If your team has to call a customer back for basic info, write down the five or six fields required before work is allowed to start.
  2. Which setting in our current software did we never finish setting up? Open the admin panel of the main tool you already pay for. Check notification routing, mobile tolerances, and hidden table columns. Half the time, the feature you want is sitting behind an unchecked box.
  3. Did an old delivery channel break? If your team says "the system never sends reminders anymore," check whether those alerts rely on old email-to-text addresses or shared inboxes nobody monitors.
  4. Where is the team using shadow AI right now? Ask your staff, without getting anybody in trouble, who is already using a personal AI account to draft emails or summarize notes. Give them a safe, approved way to do it and a clear one-page rule on what never gets pasted in.

Why we tell you this before you pay us

People sometimes ask why an AI firm spends so much time talking clients out of buying new AI tools right away.

The answer is simple: trust and math.

If we charge you $249 for an audit and show you that three configuration changes in the software you already pay for will save your coordinator six hours a week starting tomorrow, you're going to trust us when we point to the second problem on your list and say, "This one actually needs a $1,500 proof of concept, and here is how fast it pays for itself."

And if your best move right now really is just flipping three settings, tightening an intake checklist, and changing nothing else? The Decision Pack says that plainly, too. (If you do decide to build with us after the audit, the full $249 credits toward a proof of concept or implementation booked within 30 days of Decision Pack delivery. Not redeemable for cash.)

Start with the tools you already pay for. Make them do their job first. Only build what's left.