TBRCompany.com / DCBGWork Order · No. DCBG‑01

Tedious Bull$#!T*
Removal

* Busy‑ness. The polite version is on the invoice.

We're the 1‑800‑GOT‑JUNK for wasteful business systems. We remove the manual, tedious busy‑ness choking your operation — and leave a clean, automated system behind.

TKT‑01 · Site Walkthrough

What we found on site.

Every line below is a real piece of tedium pulled straight from your operation. This is the junk pile.

01

8+ disconnected Google Sheets & Forms feeding separate databases — with humans copy‑pasting between them.

02

New recruits hand‑keyed into both the Empower roster and the DCBG roster. The same person, typed in twice.

03

Auth0 accounts created by hand — one at a time, manually, for every single user.

04

The package builder runs through one person — Alex. ~10 minutes each. A single point of failure on your throughput.

05

That builder can't set per‑product family tiers (family for accident, employee‑only for critical illness) — so reps call in, frustrated.

06

Effective dates pushed back manually, month after month — with no visibility into what's actually going live. "Tired of it on the 19th."

07

No inherent KPIs. Ask a basic funnel question and the honest answer is "we just don't know."

TKT‑02 · Cost of Delay

What the junk
is costing you.

The tedium doesn't just slow you down — it leaks revenue. Every enrollment that misses its cutoff is out a full month. One slipped deal, gone, until the next window opens — and that revenue is gone forever.

Cost of one slipped deal

$4,700

per deal, per month it slips. Missed enrollment cutoff = out a month. Now multiply by every deal stuck behind the busy‑ness.

TKT‑03 · Removal Manifest

The Manifest

Removingremove
  • 8 spreadsheets & forms
  • Double data entry
  • Hand‑built Auth0 accounts
  • The "only Alex can run it" bottleneck
  • Family‑tier workarounds
  • Manually re‑pushed effective dates
  • "We just don't know" KPIs
Leaving Behinddeliver
  • One centralized data object
  • Single intake → both rosters
  • Invisible one‑click SSO
  • Self‑serve package builder
  • Per‑product family tiers
  • Auto‑projected closing dates
  • Inherent, live KPIs
TKT‑04 · The Delivery

What we leave behind:
The Empower Portal.

One system. One data object. Role‑based access so CEHAS, DCBG, agents, employer‑clients, and employees each see only their slice — login determines the interface. The DCBG vs. Empower split is automatic. No more spreadsheets, no more double entry, no more "we just don't know."

Layer 01

Foundation

  • Unified, centralized data store — retires every sheet
  • Auth0 role‑based SSO
  • Invisible, one‑click login

Layer 02

Agent & Recruit Lifecycle

  • Single intake → both rosters at once
  • Doc upload: E&O, AML, W‑9, licenses — with expiration tracking
  • Auto‑sequenced NDA → referral agreement
  • Admin notification timeline that green‑lights account creation

Layer 03

Compliance Engine

  • License / E&O / AML expiration alerts before submission
  • Credential gating — no live deals on lapsed paperwork

Layer 04

Client Intake → Quote → Enroll

  • Human‑guided census upload portal
  • Raw‑payroll → pro‑forma automation
  • Instant benefit‑overview quote
  • Employee Navigator / Claire enrollment integration

Layer 05 · the fix

Package Builder v2

  • Web‑native, DB‑backed, one‑click export
  • Per‑product family tiers, finally
  • Self‑serve & AI‑assisted — no Alex required

Layer 06

Effective‑Date "Closing" Engine

  • Auto pay‑date projection & rolling target date
  • Enforced micro‑deadlines, cost of delay surfaced
  • Master swim‑lane flow: client · agent · DCBG · EIG · CEHAS · Manhattan — from "new agent" to "fully enrolled → we've been paid → PEPM flowing"

Layer 07

Portals & Notifications

  • Client portal: stage view, collected docs, next step
  • Agent portal: pipeline + SOP prompts
  • Automated stage‑transition emails

Layer 08 · the proof engine

KPI / Analytics Layer

  • Inherent metrics: reps onboarded, reps producing, proposals generated, proposal→live, conversion, step durations, cycle time, slippage
  • Auto‑updated pipeline view
  • Doubles as the proof engine and the cost‑of‑delay source

Layer 09

AI Support Agent

  • Agents ask plain‑English questions — "what's my pipeline?", "which clients are missing docs?" — and get instant answers
  • Role & permission aware — every answer is scoped to what that user is allowed to see, nothing more
  • Surfaces SOPs and next steps on demand — onboarding help without pinging a human

// One more thing

What else do you need?

We can do (just about) anything you can think of.

TKT‑05 · Load Estimate

The ROI.

Lives today

~2,500

PEPM

$141

PEPM Rev / Mo

~$352.5K

Growing

~10%/mo

The hinge: the conservative "with TBR" 10% path is the exact same line as the aggressive "without TBR" 10% path. In other words — the conservative ceiling is the aggressive floor.

Conservative

Status quo 5%/mo → with TBR 10%/mo

Lives, month 122,500 → 7,846
vs. unaided2,500 → 4,490

Foregone revenue / 12 mo (PEPM only)

$2.4M

Month‑12 run‑rate gap ≈ $473K/mo

Aggressive

Status quo 10%/mo → with TBR 20%/mo

Lives, month 122,500 → 22,290
vs. unaided2,500 → 7,846

Foregone revenue / 12 mo (PEPM only)

$8.5M

Month‑12 run‑rate gap ≈ $2.0M/mo

Monthly revenue gap — PEPM only

MoConservativeAggressive
01$17,625$35,250
02$37,929$81,075
03$61,194$139,872
04$87,561$214,884
05$117,735$309,495
06$152,139$428,076
07$190,914$576,126
08$234,765$760,131
09$284,397$987,564
10$340,092$1,268,295
11$402,837$1,613,322
12$473,196$2,036,604
Total$2,400,384$8,450,694

These are models built on conservative assumptions and count PEPM revenue alone — no insurance commissions — as a good‑faith estimate of the value at stake, not a guarantee.

TKT‑06 · The Ask

What's next?

You've seen the junk, the cost, and the system we leave behind. The real question isn't about us — it's about you:

How do you want to partner with us?

One project, a phased rollout, or a long‑term build partner who lives in the system with you — there's no fixed shape here. Tell us what a great partnership looks like to you, and we'll build the engagement around it.