How we figure the number

Gridpoint Solutions separates what we checked, what you estimated and what happened after installation. Paul Mikhay, a journeyman electrician, uses this method to make the first decision reviewable.

Three layers, kept separate
Layer Evidence Label
Observed A dated call check, website check or actual business record We checked.
Estimated Your inputs and explicit assumptions in the formula below Estimate. Not a promise.
Verified Day-30 rescue log, recordings, calendar bookings and completed-job records Your ROI, only when supported by the records.

What is the Estimate formula?

Estimate = M × C × V. M is missed job opportunities in the period you counted. C is the share you think could become completed jobs, expressed as a fraction. V is your contribution per completed job after direct costs. Enter a percentage and the calculator divides it by 100, the definition of percent; there is no research-derived conversion constant.

No industry answer rate, voicemail rate, callback rate or job-value default enters this formula. Your call log supplies M; C is your labeled assumption; job records supply V. The count can cover a week or a calendar month, but you must keep the period consistent. We do not silently turn a week into a month.

What does a worked example look like?

Made-up inputs for illustration only: a reader counts 8 missed job opportunities in a week, assumes 25% could become completed jobs, and enters $200 contribution per job. The Estimate is 8 × 0.25 × $200 = $400 for that week. These are invented teaching inputs, not a customer result, industry average or forecast.

With the same made-up $200 contribution, two completed jobs would cover the $297 monthly Missed Call Rescue fee. The $997 setup fee is additional unless the written founding-client terms apply. A weekly Estimate cannot establish that those jobs will occur or that the monthly fee will pay for itself.

What changes at day 30?

Paul reviews the rescue log and reconciles the trail: missed call, text reply or answered conversation, booking, completed job, payment and direct costs. A repeat caller is not a new opportunity each time. Existing customers, rescheduled jobs and work you would have won anyway need separate labels. Record uncertainty instead of assigning all revenue to the system.

Verified net contribution attributable to the system, less its actual cost for the same period, is the basis for the day-30 ROI discussion. If expressing a percentage, divide that net amount by the actual system cost and multiply by 100. Include setup costs paid during the period; if cost is zero, a percentage is undefined. A record of a conversation alone does not support a financial return.

What do we refuse to promise?

We do not promise revenue, job counts, rankings or a review rating. We do not call pre-install numbers savings or results. We do not count every missed call as a lost customer or every booking as a paid invoice. Where the records cannot establish attribution, the report says so.

Try the missed-call Estimate or consider after-hours calls.

Questions before you commit

Are these industry averages?

No. The calculator uses your count, your assumed completion share and your contribution per job. A published industry benchmark can help frame a question, but it does not replace those inputs. The estimate stays attached to the period and assumptions you chose, so you can check them later.

When can the number be called ROI?

Only after the day-30 verified log supports it. Reconcile conversations, bookings, completed paid work, direct costs and the system costs for the same period. Where attribution is uncertain, say so. An estimated opportunity value before installation is not a verified return and is never labeled that way.

Bring your numbers. Talk to Paul.

30 minutes, phone or Google Meet. You leave with a one-page number: what your missed calls cost you last month, from your own numbers.

Your pre-install number is an Estimate, not a promise.

Book the 30-minute fit call Call (864) 477-7895