Hokma Solutions / New service

Find where your business leaks money, before you spend on AI.

Most companies know AI could save them money. Few know where to point it first. This audit answers that with your own numbers: a ranked list of where revenue and hours leak, a plan for what to build, and the decisions you need to make.

Read-only. I sign your NDA before I see any data, and I change nothing in your systems.

Top leaks, per yearSample company

  1. Billing$126K
    Failed payments with no follow-upConfidence: High
  2. Customer Success$104K
    Accounts that go quiet before renewalConfidence: Medium
  3. Onboarding$88K
    New customers who stall in the first 60 daysConfidence: Medium

3 data sets per number5 fixes, in order3 decisions

What you get

  • A ranked leak list

    Every leak has a dollar estimate, the data behind it, and how sure I am of the number.

  • An automation roadmap

    Each fix says what to build, what it connects to, how long it takes and what it should recover.

  • A decisions page

    One page for the owner. Each decision is a plain question with no more than three options and a link to the evidence.

The leaks I look for

I use read-only access to the systems you already have: your help desk, CRM, billing platform and project tracker. Typical leaks:

  • Failed payments nobody follows up.
  • Refunds that repeat for the same reason.
  • Leads that wait days for a reply.
  • New customers who stall in their first weeks.
  • Tickets that bounce between teams.
  • Numbers that two teams report differently.

How each number is made

A leak only makes the list if it holds up from more than one direction.

  1. Rules firstBefore counting anything, we agree in writing what counts as lost revenue, which dates apply and how duplicates are removed. The rules go in the report.
  2. Three independent data setsEach leak is counted three ways: from the billing record, from what customers said (cancellation reasons, chats and tickets), and from your own team reports.
  3. The middle number, not the biggestI report the median of the three and show where they disagree. A wide gap gets a lower confidence grade, not a rounder number.
  4. Fact, estimate or unknownEvery finding is marked. Where the data cannot support a number, the report says so and lists what would settle it.

Try it: how one number is checked

Pick a team from the sample company. You see the three independent counts, the middle number that goes in the report, and the confidence grade that follows from how far apart they are.

Interactive sample. Every name and number in it is invented.

Billing record

Invoices, failed charges, refunds

$131K

What customers said

Cancellation reasons, chats, tickets

$118K

Team reports

The numbers each team already tracks

$126K

Middle number
In the report
$126K
Confidence
High
Why
All three agree within a few thousand dollars. The billing record is the most exact source for this leak.

High when all three sit within 12 percent of the middle number. Medium within 30 percent. Low beyond that.

Sample report: Brightline Scheduling

Invented sample. The company, Brightline Scheduling, is fictional. Every name and number in it is made up.

A fictional 85-person SaaS business, about $9M in yearly revenue.

Page 1. Where the money leaks

Estimated revenue lost per year, by team. Each bar is the median of three independent data pulls. Three teams hold about two thirds of the total.

  1. Billing. Failed payments with no follow-up$126K
    Three data sets: $118K to $131KConfidence: High
  2. Customer Success. Accounts that go quiet before renewal$104K
    Three data sets: $91K to $117KConfidence: Medium
  3. Onboarding. New customers who stall in the first 60 days$88K
    Three data sets: $74K to $95KConfidence: Medium
  4. Sales. Leads waiting more than a day for a reply$79K
    Three data sets: $52K to $86KConfidence: Low
  5. Support. Repeat refunds for the same three issues$63K
    Three data sets: $60K to $67KConfidence: High

$460K a year in total, across five teams.

Page 2. Automation roadmap

Sample automation roadmap, in build order
OrderFixTeamBuild timeExpected recovery
1Failed-payment follow-up, with a person taking over after the third attemptBilling2 weeks35 to 45 percent of the leak
2Early-warning score from usage and tickets, sent to the account owner weeklyCustomer Success3 weeks20 to 30 percent
3Onboarding nudges and a queue of stalled accountsOnboarding2 weeks25 to 35 percent
4Reply drafts inside the CRM so no lead waits past one hourSales2 weeks30 to 40 percent
5Help-centre answers and a triage agent for the three repeat issuesSupport3 weeks40 to 50 percent

Every draft an automation writes waits for a person to approve it before it reaches a customer.

Page 3. Decisions for the owner

Where do we start?

  • Option ABilling only, fastest payback
  • Option BBilling and Customer Success together
  • Option CAll five fixes in sequence over one quarter

Who owns the company numbers?

  • Option AName one data owner now
  • Option BGive each team lead their own numbers
  • Option CLeave as is and accept the conflicts

Build or buy?

  • Option ABuild on the current tools
  • Option BBuy one tool per team
  • Option CDecide fix by fix

The full report also holds the written data rules, a confidence grade per finding, links to the source data, action items for each team, which fixes can start now and which wait for access, and a list of what could not be measured and why.

Example workflows from the roadmap

Each fix on the roadmap is a workflow you can see before anyone builds it. Step through three of them. The marked step is where a person approves before anything reaches a customer.

Interactive sample. Every name and number in it is invented.

Failed-payment follow-up Billing

Step 1 of 7

A card payment fails.

The billing platform reports it within minutes. Nothing goes out yet.

  • Northwind Studio, monthly planPayment failed
  • Card on fileExpired

Step 2 of 7

Was it the card, or the customer's choice?

An expired or declined card gets a reminder. A customer who paused on purpose gets no message, only a note for the account owner.

  • Card expired or declinedFollow up
  • Paused by the customerNo message

Step 3 of 7

A reminder is drafted.

Short, friendly, with the link to update the card. It is a draft, not a sent email.

Draft, not sent

Your card on file did not go through

Hi, your last payment for Brightline did not go through because the card on file has expired. You can update it here in under a minute. Your bookings keep working in the meantime.

Step 4 of 7

A person approves

A person approves it.

The billing lead sees the draft and the reason it was written, then approves, edits or skips it.

Send this reminder?

Northwind Studio, first reminder

ApproveEditSkip

Step 5 of 7

Day 3 and day 7, the same way.

Each later reminder is drafted and waits for the same approval. If the card is updated, the sequence stops on its own.

  • Day 1 reminderApproved, sent
  • Day 3 reminderWaiting for approval
  • Day 7 reminderNot yet due

Step 6 of 7

After the third try, a person takes over.

The account owner gets a task with the history attached, so the call starts with the facts.

  • Task: call Northwind StudioAccount owner
  • History3 reminders, no update

Step 7 of 7

Every step is on record.

What was drafted, who approved it and what happened next. The weekly report counts recovered accounts from this record.

  • Drafted by the workflowDay 1, 9:02
  • Approved by the billing leadDay 1, 9:40
  • Card updatedDay 2

Stalled onboarding Onboarding

Step 1 of 6

A new customer has gone quiet.

Ten days in, only one of five setup steps is done. The workflow spots it from product usage.

  • Cedar Lane ClinicsDay 10
  • Setup steps done1 of 5

Step 2 of 6

Which step is stuck?

The calendar was never connected, and a ticket about it was opened and closed without a fix.

  • Account createdDone
  • Calendar connectedStuck
  • First booking pageNot started

Step 3 of 6

A nudge is drafted for that step.

It names the one step, links the two-minute guide and offers a short call.

Draft, not sent

One step left before your first booking

Hi, your account is almost ready. The calendar connection is the step most clinics get stuck on. This two-minute guide walks through it, or reply and we will set it up with you on a call.

Step 4 of 6

A person approves

The onboarding lead approves it.

They can add a personal line before it goes. Nothing is sent without the tap.

Send this nudge?

Cedar Lane Clinics, calendar step

ApproveEditSkip

Step 5 of 6

Still stuck after five days? A call is booked.

The account moves to the stalled-accounts queue, sorted by plan size, so the team calls the biggest risk first.

  • Cedar Lane ClinicsCall this week
  • Two other stalled accountsIn the queue

Step 6 of 6

The outcome is on record.

Did the nudge or the call get them set up? The answer feeds the next month's leak estimate.

  • Nudge approvedDay 10
  • Calendar connectedDay 12

Lead reply drafts Sales

Step 1 of 6

A demo request arrives at 7:40 in the evening.

Nobody is at a desk. Without help, it waits until the next afternoon.

  • Ridgeway Physio, 12 staffNew lead
  • Asked aboutGroup class booking

Step 2 of 6

The CRM is checked first.

Is this a returning lead? Which plan fits their size? The draft will use the answers.

  • Past contactNone
  • Plan that fitsTeam plan

Step 3 of 6

A reply is drafted inside the CRM.

It answers their question about group classes and proposes two demo times.

Draft, not sent

Group class booking for Ridgeway Physio

Hi, thanks for asking about group classes. Yes, Brightline handles class sizes, waitlists and reminders. Would Tuesday at 10 or Wednesday at 2 work for a 20-minute walkthrough?

Step 4 of 6

A person approves

The rep on call approves it from their phone.

One tap to send, or edit first. The reply leaves within the hour.

Send this reply?

Ridgeway Physio, demo request

ApproveEditSkip

Step 5 of 6

No answer within the hour? It moves on.

The draft moves to the next rep on the list, so no lead waits overnight.

  • First repNo answer in 60 minutes
  • Second repApproved at 8:31

Step 6 of 6

Reply times go on the weekly report.

The sales lead sees how long each lead waited and who replied.

  • Leads this weekOn time
  • Slowest reply51 minutes

Three sizes, fixed prices

Pick by how many teams are in scope. The price is agreed in writing before any work starts.

One-team audit

$1,500

Delivered in 7 days

  • 1 team, for example Support
  • Up to 2 systems reviewed
  • Ranked leak list in dollars
  • Roadmap: top 3 fixes
  • 1 revision
Ask about this size: One-team audit

Three-team audit

$3,500

Delivered in 14 days

  • Up to 3 teams
  • Up to 4 systems reviewed
  • Ranked leak list in dollars
  • Roadmap: top 8 fixes, in order
  • Decisions page for the owner
  • 30-minute walkthrough call
  • 2 revisions
Ask about this size: Three-team audit

Whole-company audit

$6,500

Delivered in 21 days

  • Up to 7 teams
  • Up to 8 systems reviewed
  • Ranked leak list in dollars
  • Full roadmap with build estimates
  • Decisions page for the owner
  • 60-minute walkthrough call
  • 2 revisions
Ask about this size: Whole-company audit

The audit stands on its own. If you want any roadmap item built, I quote it as a separate fixed-price project.

How it runs

  1. KickoffYou answer a short questionnaire and grant read-only access or send exports.
  2. Data sweepI pull the numbers from each system and cross-check them against each other.
  3. FindingsI rank the leaks and send you a draft to challenge before anything is final.
  4. Roadmap and decisionsI deliver the final report and walk you through it.

What I need from you

  • A list of the teams in scope and who leads each one.
  • Read-only access, or exports, for the systems in scope.
  • The last 6 to 12 months of data where you have it.
  • One contact who can answer questions within a business day.
  • The two or three outcomes that matter most this year, for example lower churn or faster onboarding.

Questions

Do you need admin access?

No. Read-only access or exports are enough. I never change anything in your systems.

Our data is messy. Does that stop the audit?

No. I cross-check each number across more than one system and tell you how confident I am in it. Where the data cannot support a number, I say so.

Will you build the automations too?

The audit stands on its own. If you want me to build any item on the roadmap, I quote it as a separate fixed-price project.

Which tools do you work with?

Common help desks, CRMs and billing platforms, plus spreadsheets and exports. Tell me your tools before you order and I will confirm.

How do you handle confidentiality?

I sign your NDA first, work only inside the access you grant, and delete exports when the project closes.

What if you find very little?

Then the report says so, and you have saved the cost of building automation you did not need.

Who does the audit

I build AI tools for support and operations teams, including Support Coach, a reply checker live on the Chrome Web Store. So the plan you get is one I could build myself, written for people who run teams, not only for engineers.

This is a new service. You would be one of the first clients, and the proposal will say so.

Fifteen minutes, and you will know if it's a fit.

Tell me what your team is dealing with. I will tell you whether I can help and what it would cost.

Book a 15-minute call

Prefer to write?

Send a short brief