Cool Power×B2
Post-close integration roadmap · Confidential · Internal

The first 90 days after we own Cool Power.

A strategy plan we can actually follow — what we do in the first 30, 60 and 90 days post-close, who owns it, and how we know we’re on track. Built on the Cool Power diligence and the four P’s: people, process, platform, profit. Every item is grounded in what we found, not generic playbook.

Close / Day 1
Jul 31, 2026
Anchor platform
Cool Power LLCRonkonkoma, NY · est. 1999
Founder-operator
Jared Hager
Brand & paid media
BRNDMKRS · Nova
Measurement window
Days 1–30instrument before intervening
Year-1 budget
$10.63M revAdj. EBITDA $438.6K
Margin north star
25% EBITDAlong-term · ~18 mo+ (Jared)
Overall progress
0%
How we operate

Four principles, before the plan

Cool Power runs well and Jared is trusted. The posture for the first hundred days is to be visibly present and functionally invisible — these four principles come from our read of the business and govern everything below.

01
Ask, don’t announce. The first 30 days are ride-alongs, 1:1s and observation — not memos, reorgs, or new dashboards. The team should believe nothing changes that they wouldn’t agree to change.
02
Instrument before intervening. Measure for 30 days before pushing on any number. Instrument first, set targets second — pick levers first and you’ll miss the point.
03
Keep the team intact. No role changes in the first 60 days. The roles review below is a planning artifact — actions are sequenced and trigger-based, never day-one.
04
Costco winds down with dignity. Every Costco-facing role lands a new seat before the channel wraps. Timing drives off the Costco walk-through, not an arbitrary post-close deadline.
North star: tighter alignment between people, process, platform and profit, with real-time visibility into performance at every level. Cool Power is the first build of the B² Operating System — what works here becomes version one.
The arc

Ninety days, four moves

Each period has exactly one job — and a short list of things that are simply true by the time it closes. Read nothing else and you still know where we’re headed: earn the right, make the calls, show it moves, then compound.

01
Days 1–30Jul 31 – Aug 30

Earn the right

Be present, measure everything, and change nothing the team wouldn’t change themselves.

True by Day 30
  • Real baselines measured across service, install and commercial.
  • Financial targets set off real numbers — not guesses.
  • BRNDMKRS brand direction locked; first new uniforms on the crew.
  • Nova live on all paid media — Google Ads moved off Rhino by close.
  • The team believes we’re here to back Jared, not run him over.
02
Days 31–60Aug 30 – Sep 29

Make the calls

The month of decisions — pick the platform, set the targets, and start building the operating system underneath the business.

True by Day 60
  • FSM + accounting chosen as one architecture, not two.
  • The weekly business review running off a single dashboard.
  • New functional leads recruiting; the comp framework designed.
  • The hero brand film shot — the content library underway.
03
Days 61–90Sep 29 – Oct 29

Show it moves

Turn decisions into motion — pilots running, dashboards live, the first margin captured rather than just named.

True by Day 90
  • The new FSM piloting live with two techs.
  • Job-level P&L and channel attribution on the board.
  • The comp model rolling out; the brand launched to the public.
  • Margin capture measured — improvements booked, not flagged.
04
Months 4–12Oct 2026 – Jul 2027

Compound

Cut over, scale and embed — Cool Power becomes the first working build of the B² Operating System.

True by Year 1
  • Full stack cutover complete; legacy retired for good.
  • Costco wound down with every role landed elsewhere.
  • The rebrand across the whole fleet, site and showroom.
  • The path to 25% EBITDA visibly underway.
The calendar

Key dates & launches

The dated commitments — the relationship moments, the brand and fleet rollout, and the measurement-to-targets checkpoints. Everything operational anchors to close on July 31, 2026; the brand track runs on BRNDMKRS’s own calendar from the Jul 22 kickoff. Brand, media and fleet dates are our plan; the rest follow the principles above.

Go-live · the first weeks

Day 1 & the first month

Day one is a stake in the ground, not a shake-up. The month that follows is presence and measurement — plus the two places we move fast and visibly: the brand and paid media.

Pre-close · Jul 22–31

Providers kick off

  • BRNDMKRS kicks off Jul 22 — brand strategy deep-dive begins ahead of close.
  • Elevate + ServiceTitan Jul 24 — data migration begins; our ST tenant goes live.
  • Nova takes paid media by Jul 31 — all Google Ads off Rhino, onboarded.
Day 1 · Jul 31

All-hands & continuity

  • 5-minute stake from B²: “We’re here to back Jared. We’re not changing how you do your jobs.”
  • No reorg, no new dashboards, nothing operational announced.
  • Private continuity reassurance to key seats — Cassandra, Kathy, Jared.
Closing week · Aug 3

Closing dinner

  • Dinner with Jared and the leadership team — Cassandra, Dan, Duane, Sal, partners.
  • The relationship investment that sets the tone for the partnership.
  • Low-key, warm, no agenda beyond getting to know each other.
Weeks 1–4

B² on the trucks

  • Ride-along days — service with Jay, an install day with Duane, a commercial site with Sal.
  • Roughly a day a week through month one.
  • 1:1s with every leader: “what works, what doesn’t, one thing you’d change.”
Aug 17

Introductory team party

  • The whole company, families welcome — hosted by B².
  • Debut the first new uniforms and swag.
  • Food, prizes, the first informal “new chapter” moment.
Days 1–30

Measure, don’t intervene

  • 30-day KPI measurement window — instrument true baselines across every segment.
  • Lead-source tagging switched on at intake from day one.
  • Final QoE delivery from the diligence firm; targets set at Day 30.
Through Q1

The brand rolls out

  • Uniforms & merch (Aug 17 → full rollout ~Sep 17).
  • Vehicle wraps — pilot Sep, full fleet over Day 180–365.
  • Public brand + new website launch Nov (funded $150K relaunch).
Phase
Owner
The roadmap at a glance

Timeline × workstream

Six workstreams down the side, four phases across the top. Click any item to jump to its detail. Filter by phase or owner with the controls above. The marks the one call still to confirm — the Sage↔ServiceTitan accounting integration.

Aligned to the operating budget This roadmap maps to the budget at budget.bsquared.capital — Year-1 plan $10.63M revenue, $695K one-time initiatives + $779K CapEx. Budget phases: Day 1–90 Stabilize · Day 90–180 Build the operating system · Day 180–365 Accelerate growth. Mind the cash plan — $100K at close, ~$337K additional liquidity needed, $300K minimum-cash — so the CapEx-heavy items (fleet adds, brand relaunch) follow the budgeted dates rather than running ahead of them.
Grounded in Cool Power diligence
B² extrapolation our read, not stated
Confirm tension with diligence — verify
The work, in detail

Workstreams

Six workstreams, each carried from diagnosis through implementation. Click a status pill to cycle Not started → In progress → Done → Blocked; it saves in your browser so this stays a live tracker.

Measure, then target

Benchmarks & financial targets

The 30-day measurement window sets the baseline; at Day 30 we lock the targets off real numbers. Most baselines are owed by QoE — we mark those honestly as TBD rather than inventing a number. The anchor is Jared’s own goal: 25% EBITDA on current revenue, no growth assumed, in roughly 18 months.

“Aiming for a 25% margin on current revenue, without factoring in revenue growth. Goal is to achieve this margin in approximately a year and a half, potentially sooner.”Jared, on-site 4/06
MetricBaseline (today)By Day 30By Day 9012-month / long-term targetSource
Internal planning artifact

Roles review — who we keep, build behind, backfill, or wind down

Modeled on the diligence “Administrative Position Review,” grounded in Cool Power’s actual org. This is planning only. Consistent with principle 03, there are no role changes in the first 60 days; every action below is sequenced and trigger-based. Salary figures aren’t disclosed in diligence except where noted — we don’t fabricate them.

Handle with care. This panel names people and is the most sensitive part of the document. It exists to de-risk key-person concentration and plan succession — not to move fast on headcount. Costco-facing roles wind down only after the channel does; back-office centralization is sequenced after the system cutover.
Seat / personComp basisAssessmentAction & timingPriority
The platform switch

Legacy stack → target stack

The back-end FSM is, in Jared’s words, the single most important technology call — and it must be chosen as one architecture with the accounting system, not sequentially. Migration is deliberately slow: pilot with two techs, parallel-run dispatch, full cutover targeted ~Day 150 (not during summer peak), Kathy holds veto on the date.

Decision made — now in motion The stack is ServiceTitan (FSM) + Sage Intacct (accounting). Elevate kicks off data migration Fri Jul 24 — the same day our ServiceTitan tenant goes live — with an official go-live of Sep 18 on Elevate’s migration plan — well ahead of the budget’s Dec assumption (FSM/ERP, $150K one-time) — and all new service providers officially onboarded by Sep 14. This reverses the April diligence record, where Jared explicitly rejected ServiceTitan (“never gonna let us do that”) in favour of a Workiz / Workwave shortlist. Accounting was left undecided then, so the one thing still to confirm is the Sage↔ServiceTitan integration before the accounting cutover.

Today — legacy

  • ComputerEase — system of record: jobs, customers, invoicing, accounting (“like Access 1997”)
  • Manual dispatch — Kathy routes by intuition; paper + email, no auto-scheduling
  • Hand-prepped van inventory — per-tech boxes, no barcode, no replenishment baselines
  • Pulse Check — pre/post-visit comms & reviews (tech-initiated, not auto)
  • Lennox Pros · testo · Blue Book — parts pricing, smart gauges, commercial leads
  • Rhino → Scorpion — paid media (moving to Nova by Jul 31); “bland” site, zero attribution on $202k spend

Target — integrated

  • ServiceTitan — back-end FSM; Elevate migrating from Jul 24, go-live Sep 18
  • Sage Intacct ⚑ confirm— accounting, chosen as one architecture with the FSM
  • Auto-dispatch + auto-billing — preserve Kathy’s matching logic; recurring billing unblocks membership
  • QR inventory + auto-replenish — van stock visibility; PPE vending (Jared’s wish list)
  • Voice agent (Avoca / Fin) + Robby AI — booking automation, tech-assist
  • Converting site + attribution layer — Nova on paid media; channel-level CAC / ROAS
The data migration

ServiceTitan migration — Elevate

Scott’s team at Elevate owns the ServiceTitan data migration end to end — extract, transform, test, load. The plan paces to a Sep 18 go-live, well ahead of the budget’s Dec assumption. The joint tag marks the sessions Cool Power sits in; everything else runs on Elevate’s side.

StepWindowWhat happens
Kick-off meeting joint~Jul 24Understand the branch’s systems & processes; secure access to required systems and off-system data.
Data extractionJul 18–24Extract and analyze the data; develop the mapping hypothesis.
Initial data transformationsJul 24 – Aug 10Data transformed; the initial data gaps and questions developed.
Data review meeting jointAug 10Meet with the company to review data gaps and questions.
Data review iteration + updated transformationsAug 10–24Iterate on the Data Review app.
Test data loadAug 24Upload the test data.
Test data review & updates jointAug 24 – Sep 11Guided time for the branch to learn the system on real data and give feedback.
Test data approved jointSep 11Sign-off for Elevate to pull the latest data for loading.
Final data pull + transformationsSep 11–14Re-pull data and run final transformations, ready for production load.
Data sent to ServiceTitanSep 14Send the templates to ServiceTitan for upload.
Go-live jointSep 18Official go-live date.
Feedback + fixes joint~Sep 25Post-go-live support and fixes, via API or other techniques.
What could go wrong

The risks worth naming

From the diligence risk register — the unforced errors a bad 90 days would come from.

RiskLIMitigation
FSM + accounting decided separately or rushed.HighHighTreat as one architecture decision; evaluate in parallel; lock both by Day 60; pilot before cutover.
FSM cutover breaks dispatch in summer peak.MedHighTwo-tech pilot for 30 days; parallel-run dispatch boards; Kathy has veto on the cutover date.
Marketing attribution never gets built.MedHighTag lead source at intake from Day 1; formal layer in Phase 3; don’t wait for the perfect stack.
Costco wind-down mistimed.MedHighPhased, tied to pipeline triggers not dates; no hard deadline before the Costco walk-through.
Commercial sales gap — Sal is the whole motion.MedMedScope estimator hire by Day 60 to offload takeoff; grow into a salesperson if Sal wants help.
L3Harris concentration.LowMedQuarterly L3 reviews; pursue property-manager anchors so the book isn’t one relationship.
Measure → target → review

Two checkpoints we commit to

The discipline that keeps us honest: a month of measuring before we set a single target, then a full review against those targets at the quarter mark.

Day 30 — baselines & targets

Set the financial goals off real numbers

The 30-day measurement window closes. QoE is closed (revenue & EBITDA by segment, rev-per-man reconciled install vs. service). With true baselines in hand, we lock the financial targets — the path to 25% EBITDA, revenue-per-man-per-day, service-contract penetration and channel CAC. Targets are set after we measure, never before.

Day 90 — business review

State of the business vs. targets

A full review against the targets: what moved, what didn’t, what we’d change. A live KPI scorecard and weekly business review running, the stack decision locked with rollout begun, the comp model moving into use, the brand and fleet refreshed, and a 12-month operating plan co-authored with Jared and board-ready.