BlackSig Systems/Systems/Reputation Engine

// Reputation Engine · Review Generation

Your rating is written by your unhappiest 5%. Not your best work.

It asks every customer while the job's still fresh. Happy ones get walked to Google in two taps. Unhappy ones get routed to you privately first, before it ever becomes a one-star review.

Reputation Engine · this month
61Customers asked
24Reviews landed
3Saved privately
Job closed → SMS ask → 5★ posted to Google✓ Posted
Unhappy signal → routed to owner, called same day✓ Saved
No reply → one polite nudge after 3 days✓ Asked

// The problem

Your best customers never leave reviews. Your worst ones always do.

The customer who loved the work tells their neighbor and moves on with their life. The one with a grievance opens Google that night. Nobody's asking the happy ones, so the angry ones write your public record, and your rating ends up reflecting your unhappiest 5%, not the hundreds of jobs that went right.

And that rating works harder than it used to. It's the filter in Search and Maps, and it's part of what ChatGPT and the other AI assistants weigh when someone asks "who's a good roofer near me." A thin or mediocre review profile quietly costs you jobs you never knew you were up for.

// What it's costing you

97%
of consumers read reviews when evaluating a local business (BrightLocal, Local Consumer Review Survey)
68%
now require a minimum 4-star rating before they'll consider a business (BrightLocal)
5% to 9%
revenue increase from a one-star rating improvement (Harvard Business School, Michael Luca)

The threshold keeps rising, too. Nearly a third of consumers now won't consider anything under 4.5 stars. Sit at 3.9 with forty reviews and you're invisible to most of your market before the phone ever gets a chance to ring.

The short version

Your rating isn't a vanity number. It's a filter that runs on every buyer, and every AI assistant, before you ever hear from them.

// What we build

Every customer asked. Every unhappy one caught first.

It wires into whatever marks a job done in your world, then runs the same loop on every job:

  1. Job closes → a short text or email goes out in your voice, while the work is still fresh.
  2. Happy customer: direct link to your Google profile. Two taps and the review is live.
  3. Unhappy signal: routed straight to you, privately, with the job context attached, before anything goes public.
  4. No reply: one polite nudge a few days later. Then it stops. Nobody gets pestered.
  5. Every review, good or bad, logged to your dashboard with an alert so you can respond.
  6. Requests can also point at Yelp, Facebook, or industry sites where those matter.
  7. Runs on every single job, automatically. Nobody has to remember to ask.

// The numbers

97%
of consumers read reviews when evaluating a local business (BrightLocal)
31%
will only use a business rated 4.5 stars or higher (BrightLocal)
88%
would use a business that replies to all its reviews, vs 47% for one that replies to none (BrightLocal)
5% to 9%
revenue lift per additional star (Harvard Business School, Michael Luca)

// Questions

Is intercepting bad reviews even allowed?

We don't intercept anything. Every customer gets asked. That's what keeps it inside Google's rules, which prohibit asking only your happy customers. What unhappy customers get is a direct line to you first, because most people just want the problem fixed and to be heard. Nothing stops them from posting publicly. In practice, a same-day call back resolves most of it before it becomes a one-star review.

Does it work with Google?

Google is the default target. It's the rating that shows up in Search, Maps, and increasingly in AI assistants when someone asks for a recommendation. We can also point requests at Yelp, Facebook, or industry-specific sites if those matter in your market.

What does it actually send my customers?

A short text or email in your voice, sent while the job is still fresh. It isn't a survey or a form. Happy customers get a direct link to your Google profile, two taps to done. No reply gets one polite nudge a few days later, then it stops. You approve every word before launch.

How long does it take to launch?

Two to three weeks. We wire it to whatever marks a job complete in your world, write the asks in your voice, and test the whole flow, including the unhappy-customer route, before it touches a real customer.


// How we work

Diagnose, build, run.

Diagnose. We map where your time and money leak and put a number on each one. You get that written assessment whether or not you hire us to fix any of it.

Build. One-time fee, scoped and priced before anything starts. Two to four weeks for most systems.

Run. Monthly. It lives on our infrastructure. We own uptime, absorb changes as your business changes, ship an improvement every month, and send a report showing what it produced.

Your best work should be the thing people read. Let's make it public.

The diagnosis looks at your rating, your review velocity, and your competitors', then tells you what the gap is costing. Yours to keep either way.