RunBright
IndustriesHow it worksPricing
Log inRequest beta onboarding
Request beta onboarding
RunBright

One operating system for the leads, customers, conversations, jobs, payments, and follow-through that keep a service business moving.

Product

  • View the product
  • Industries
  • Websites
  • Inbox
  • Automated follow-up
  • Voice Agent

Evaluation

  • Compare plans
  • See the workflow
  • Read the methodology
  • Help center

Company

  • About
  • Contact
  • Partners
  • Careers

Resources

  • Resource library
  • Articles
  • Results methodology
  • Help center
  • System status
  • Log in
© 2026 RunBright. All rights reserved.
PrivacyTermsCCPA
Measurement methodology

See what evidence can prove.

RunBright has no published customer outcomes yet, so this page shows the publication bar, current measurement capability, and separately labeled third-party context.

Request beta onboardingSee the workflow
Current proof stateNo published customer outcomes

Product, implementation, commercial, and research evidence only.

Publication standard

Every result clears seven checks.

A publishable result needs a baseline, denominator, window, confounders, product telemetry, customer approval, and a named speaker with a role.

Publication gateClosed — no published outcomes
  1. 01
    BaselineStarting state and the method used to record it
    Required
  2. 02
    DenominatorEvery eligible record, including exclusions
    Required
  3. 03
    WindowObservation dates and enough time to interpret the change
    Required
  4. 04
    ConfoundersSeasonality, staffing, spend, offers, and other material changes
    Required
  5. 05
    TelemetryTraceable product events and source definitions
    Required
  6. 06
    Customer approvalExplicit permission for identity, wording, and supporting material
    Required
  7. 07
    Named speakerA permissioned person, role, source, and approval date
    Required

Product measurement

Inspect the operational record.

Connected records can show source, response, pipeline, jobs, invoices, payments, reviews, and attribution context without claiming what caused the outcome.

Customer record

Source through follow-through

The Customer Record keeps source, communications, work, money, consent, and the next action inspectable together.

Illustrative record
AB

Ava Brooks

Residential · Active

OwnerTaylor Morgan

INV-1048

Awaiting payment$249.00
Q-1048Approved

Payment

Not collectedRequired
STRIPEAwaiting payment
Next actionReview invoice and follow-through
Jobs and scheduling

Work and money states

Jobs views expose schedule, assignment, work status, and the open money step for the same illustrative record.

Demo workspace

Jobs

Every job from scheduled to completed

ScheduledConfirmed
Job statusCompleted
Money stepAwaiting payment
JobAssignmentStatusInvoice
Selected job#1048CustomerAva BrooksNext actionReview invoice and follow-through
Third-party research · Not RunBright results

External context

Research informs the evaluation.

Housecall Pro, BrightLocal, and Capterra describe buyer and customer context; none of their findings are RunBright results.

Housecall Pro · 2025

Customers Judge The Whole Service Experience.

The operational details around the job now influence who gets hired, who gets referred, and who gets called again.

96%expect a professional website
80%factor in online booking
73%would refer after a great experience
1,040 US homeowners and household decision-makersSurvey of 1,040 US homeowners and household decision-makers.Publisher methodology
BrightLocal · 2025

The Review Journey Continues After The Job.

Customers are willing to review, expect a response, and respond best when the request arrives through a familiar channel at the right time.

96%are open to writing a review
93%expect businesses to respond
40%prefer review requests by email
Representative panel of 1,026 US adultsRepresentative panel of 1,026 US adults.Publisher methodology
Capterra · 2023

Implementation clarity affects the decision.

Software purchase regret research highlights unexpected costs, difficult onboarding, and gaps between sales expectations and implementation.

35%cited higher-than-expected cost
34%cited onboarding or training difficulty
48%cited a problematic sales handoff
700 U.S. software-purchase decision participantsOnline July 2023 survey; this U.S. report covers 700 software-purchase decision participants.Publisher methodology

Future case study

Preview the proof contract.

The first case study will identify the customer, prior process, workflow change, eligible records, measured result, permissioned quote, and supporting media.

Preview only — future case study structuredraft
01

Customer and permission

Approved identity, owned logo, industry, segment, and publication consent

02

Baseline and prior process

Starting state, denominator, eligible cohort, source, and known data limits

03

Implemented workflow

Exact channels, responsibilities, review gates, activation date, and exceptions

04

Measured result

Value, unit, baseline, window, cohort, source, confounders, approval, and expiry

05

Named customer voice

Speaker, role, exact permission, source, and approval date

06

Supporting evidence

Approved product states or customer-owned media with captions and accessible descriptions

Guided beta onboarding

Define the baseline first.

Map one workflow and agree on what the product can observe before using later activity as evidence.

Request beta onboardingCompare plans
  • Baseline: Starting state and the method used to record it
  • Denominator: Every eligible record, including exclusions
  • Window: Observation dates and enough time to interpret the change
  • Confounders: Seasonality, staffing, spend, offers, and other material changes