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, leaving 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 bull$#!t we will remove.

01

At least 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, and the packages are less accurate than they should be.

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 KPIs anywhere. Ask a basic funnel question and the honest answer is "we just don't know."

TKT‑02 · Cost of Delay

What the bull$#!t
is costing you.

The tedium doesn't just slow you down — it leaks revenue. Every enrollment that misses its cutoff is pushed out a full month.

Every slipped deal gets pushed until the next window opens — and that revenue is gone forever.

Sometimes clients lose interest, and you're left with a deal that never starts.

Avg cost of one slipped deal (20 lives)

$2,820

Each month pulled forward = more revenue.
Missed enrollment cutoff = less revenue.
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 the removal leaves behind: 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

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

Your roster already grows ~10%/mo. Clear the busy‑ness and 15%/mo is in reach — here's the gap that creates.

TodayMo 12 · No TBRMo 12 · With TBR
Lives2,5007,84613,376
Revenue / mo$352.5K$1.11M$1.89M

Foregone revenue · 12 mo (PEPM only)

$3.46M

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

Month‑by‑month — roster & revenue gap (PEPM only)

MoLivesForegone / Mo
012,875$17,625
023,306$39,656
033,802$66,931
044,373$100,429
055,028$141,299
065,783$190,879
076,650$250,734
087,648$322,691
098,795$408,875
1010,114$511,765
1111,631$634,244
1213,376$779,667
Total$3,464,795

A model built on conservative assumptions — PEPM revenue alone, no insurance commissions — as a good‑faith estimate of the value at stake, not a guarantee.

TKT‑06 · The Decision

What's next?

You've seen the bull$#!t, what it's costing you, and what removing it looks like. The real questions are not about us. They are about you:


How do you want to get started?

How much tedious bull$#!t do you want us to remove, and how fast?