Book a session
Sample Deliverable — Relaunch90™ Applied

The Channel Flip, Applied: TrueTread Goes Digital-First

One tire distributor. A channel mix built for a market that's already moved. Here's the full Relaunch90 cycle — Foundation Lock, Business Model Redesign, Operating Model & Architecture Fit, Test the Model, Pilot Build & Launch, Verdict & Handoff — applied step by step, exactly as a real 90-day engagement runs. Fictitious and composite.

Sector: Commercial & Retail Tire Distribution Org size: 14 branches, ~340 people Trigger: A digital-native marketplace won a fleet bid on price Cycle length: 90 days Status: Fictitious · Built From Practice Patterns · Composite
Built directly from the live Creativa framework: Relaunch90™ →
This is a fictitious case. There is no real client and no real engagement behind this document. It was constructed from patterns commonly seen across commercial-distribution channel transformations — the kind of operating-model friction, customer-segment resistance, and pilot economics that actually shape a company's first 90 days of a channel-mix inversion — to demonstrate the methodology honestly, on a scenario realistic enough to be useful. The company, its size, and every named figure are composites, not a real organization or a real result. No number anywhere in this document is drawn from a real client's data.
The Brief

A Website Doesn't Change a Channel Mix. It Just Gives the Old One a Login Page.

  • 14 branches. Commercial fleet accounts and walk-in retail, roughly 65/35 of revenue.
  • Every fleet reorder starts with a phone call to the customer's own branch rep.
  • The website exists. It quotes. It doesn't sell.

By the numbers: a healthy, well-run regional distributor. That's exactly the problem — the numbers describe a company built for a market that's already moved on.

Then a digital-native tire marketplace won a fleet bid TrueTread had held for six years — on price, with same-week install scheduling built into checkout. Two weeks later, a mid-size delivery fleet's ops manager asked her account rep, unprompted: "why can't I just reorder the same 40 tires online?"

  • Digital transactions: 10% of volume, unchanged for three years.
  • The website's own checkout: built for one-off retail purchases, never for a recurring fleet account.
  • No branch had ever lost a fleet account to price before.
Why this fails as a website project The default failure mode for every "let's also sell online" initiative: bolting a storefront onto a business model built around a phone call and a counter rep. A channel doesn't get adopted because it exists — it gets adopted when the operating model behind it can actually deliver on what it promises. Relaunch90™ treats the Business Model and the Operating Model as one causal chain, not two separate projects.

What "success" had to mean here

The Model Contract locked one distinction before Day 0: usage isn't the goal. A digital channel commercial fleets actually trust with a recurring order is.

  • Floor: 25% of transaction volume through the digital channel by Day 90.
  • Stretch: 40% of transaction volume through the digital channel by Day 90.

Ninety days doesn't flip a channel mix from 90/10 to 10/90 — no honest methodology claims that. It proves the new model works, live, against real accounts, and gives leadership a real number for how fast the rest of the flip can go.

1Foundation Lock · Strategy & Objectives

The Right to Win Isn't "Cheaper." It's "Never Have to Call."

Winning Aspiration: become the tire supplier commercial fleets never have to think about — reorder, install scheduling, and invoicing in one place, with the branch network as backup, not the front door.

Where to Play: existing fleet accounts first — the highest-trust, most price-realized segment — then price-sensitive DIY retail once the platform is proven.

How to Win: not lowest price. Fewer phone calls, a guaranteed install slot at checkout, and a fleet account's own purchase history one click away. The digital marketplace competitor only wins on price — TrueTread's 14-branch install network is a moat it doesn't have.

6–12moProve the model
Digital revenue mix at or above the Model Contract floor
1–3yrMake it the default
60% of fleet accounts self-serving reorder without a call
3–10yrInvert the mix
90% digital · branch network re-purposed as install/fulfillment hubs
Design principle Levels 1–3 of the Transformation Framework — Strategy, Objectives, Customer Value — are confirmed here, not redesigned from zero. TrueTread's strategy wasn't wrong. It was built for a channel mix that no longer describes where the market is going.
2Foundation Lock · Model Contract

Ninety Percent Physical Isn't a Preference. It's What the Org Chart Produces.

The As-Is Business and Operating Model Canvas made the diagnosis concrete: nothing in TrueTread's structure — comp plan, phone-first workflow, branch-siloed inventory — was built to produce a digital transaction. The channel mix isn't a customer preference. It's the output of the machine as designed.

Day-0 Channel Mix

Share of transaction volume, physical vs. digital

90% Physical
10%
FieldValue
Headline metricShare of transaction volume placed through the digital channel
Baseline10%
Floor25% by Day 90
Stretch40% by Day 90
Riskiest assumptionCommercial fleet accounts will self-serve reorder online instead of calling their branch rep
Day 10 Gate Strategy One-Pager, three-horizon OKRs, As-Is canvases, and this Model Contract — all five deliverables signed off by the CEO and VP Commercial. The 90-day redesign clock starts here, not before.
3Business Model Redesign · Innovation Posture

Kill the Phone-Then-Keyed Order Before Building Anything New

The Ten Types of Innovation scan flagged two patterns already sitting inside TrueTread's own business, unused: fleet accounts already buy on a predictable cadence, they'd just never been asked to commit to it digitally. That single observation set the Three Box allocation.

Box 1Optimize
Branch counter, refocused on install and pickup — not order-taking
Box 2Abandon
Unstructured phone / fax / email ordering — retired, not digitized
Box 3Create
Fleet self-service portal + DTC retail storefront with guaranteed install-slot booking
The move that mattered Business Model Navigator flagged "subscription" and "channel" patterns as the closest fit — not a marketplace play, not a price play. Fleet accounts buy the same 40 tires every quarter; the model just never asked them to commit to that cadence online.
4Business Model Redesign · To-Be Canvas

Six Blocks Move When the Channel Inverts

Designed block by block, from the Value Proposition outward, then pressure-tested against the digital marketplace competitor's own economics. It doesn't have 14 branches or an install network — TrueTread's redesign leans into exactly what the challenger can't replicate.

BlockAs-IsTo-Be
Value PropositionA branch rep who knows your accountA branch rep who knows your account — reachable in one click when self-service isn't enough
ChannelsBranch counter + phoneApp/web self-service + click-and-book install at any branch or partner installer
Customer SegmentsLocal walk-in fleets + DIY retailNational fleet accounts (self-service) + price-sensitive DIY retail (DTC)
Revenue StreamsPer-tire sale + branch install laborRecurring fleet account contracts + bundled online install fees
Key Resources14 branches' floor inventoryDigital platform + regional fulfillment hubs + expanded install-partner network
Key PartnershipsIndependent local installers, informalFormal install-network SLA partners + last-mile delivery carriers
Business Model Design Review Signed off by the CEO and VP Commercial as the version the Operating Model gets built against. The Minimum Lovable Service: a fleet account can reorder its exact standing SKU list and get a confirmed install slot in under 90 seconds — not a full storefront on Day 1.
5Operating Model & Architecture Fit · POLISM Build

Every POLISM Component Traces Back to a Business Model Block

Built directly from the To-Be Business Model — not a generic org redesign. Each component exists to deliver a specific block from Step 4.

PProcesses
Order-to-install workflow redesigned for online orders + fleet self-service reorder
OOrganization
Branch counter reps retrained as Install-Network Coordinators; new digital customer-success role
LLocations
14 branches re-classified — 5 stay full-service, 9 become fulfillment + install-only hubs
IInformation
Ecommerce platform + fleet portal + real-time cross-branch inventory visibility
SSuppliers
Last-mile delivery carriers + 2 new install-partner chains for coverage gaps
MMgmt. System
New KPI cascade: digital revenue %, cart conversion, install-slot fill rate
6Operating Model & Architecture Fit · Architecture & Culture

The Gap List Was Short. The Fear List Wasn't.

The Enterprise Architecture gap-check was scoped strictly to what the pilot needed to run — not a full architecture program.

DomainGap found
BusinessBranch P&L model didn't yet credit a branch for an online order it fulfilled or installed
DataSKU and fitment data inconsistent across 14 branches' legacy inventory systems
ApplicationsNew ecommerce platform and fleet portal needed to integrate with the existing branch point-of-sale system
TechnologyNo real-time inventory visibility across branches — the single largest pilot-blocking gap
The Cultural Activation Thread, starting here The unspoken fear inside every branch: "the website replaces me." The redesign said the opposite, and had to prove it structurally, not just say it — branch reps' new Install-Network Coordinator role is paid on account retention and attach-rate, not counter volume. The comp plan changed before the culture had to.
7Test the Model · The Risk Triangle

The Segment With the Most Revenue Was the Least Ready

DDesirability
Will fleet ops managers actually self-serve reorder instead of calling their rep?
FFeasibility
Can the install-partner network handle online-booked appointments at the volume needed?
VViability
Does digital margin hold once delivery + installer commissions are netted out?

Customer Segment Map

Digital readiness vs. account value / relationship influence — bubble size = share of revenue

High value, low readiness High value, high readiness Low value, low readiness Low value, high readiness VIP / legacy 14 accounts Small fleets 140 accounts Large fleets 46 accounts DIY retail Highest volume, lowest value Digital readiness → Account value / influence →
Why this map mattered The 14 VIP / legacy fleet accounts carry outsized revenue and the deepest branch-rep relationships — and were the least ready to self-serve. Not a training gap. A relationship the digital channel hadn't been designed to replace, only to extend. That's why they became Step 9's explicit exclusion from the pilot, not its first target.
8Test the Model · Pivot, Persevere, Abandon

The Website Was Never the Hard Part

Assumption testedMethodCall
Fleet accounts will self-serve reorder online15-account pilot, real portal, 3 weeksPersevere — with a "call my rep" escape hatch kept visible on every screen
Install-partner network can handle online-booked slotsTechnical pilot, 2 branchesPivot — existing scheduler couldn't handle partner-installer bookings; 2 install-partner chains contracted instead of building in-house capacity
Digital margin holds after delivery + installer commissionReal cost analysis vs. branch-absorbed laborPersevere — margin held once branch real estate + labor cost per transaction was netted against it honestly
Day 60 Evidence Gate Both canvases locked at v2. The platform cleared every test it ran. The binding constraint on the whole redesign turned out to be install-slot capacity — not checkout, not adoption. That finding reshaped where Phase 4's atomic units got spent.
9Pilot Build & Launch · Atomic Units

One Artifact, One Owner, Binary Done

POLISM ComponentAtomic UnitOwnerDue
Processes"Order-to-install" SOP v1 written and first executedOps LeadDay 68
OrganizationInstall-Network Coordinator role live at 5 pilot branchesOps LeadDay 65
Locations3 branches re-classified to fulfillment-onlyOps LeadDay 72
InformationFleet portal + cross-branch inventory dashboard live for pilot accountsData LeadDay 70
Suppliers2 install-partner chains contracted, SLA signedProcurementDay 63
Mgmt. SystemDigital revenue % tracked weekly in the VPF dashboardFinance LeadDay 66

The 90-day plan

Six phases, five gates, on the calendar. The redesign phases are short and front-loaded; testing and the pilot itself take up more than half the cycle — proof takes longer than design.

PhaseDay 1Day 30Day 60Day 90
Foundation Lock D1–10
Business Model Redesign D11–25
Operating Model & Architecture D26–40
Test the Model D41–60
Pilot Build & Launch D61–80
Verdict & Handoff D81–90
10Pilot Build & Launch · Launch & VPF Read

First Proof Point: Real Data, One Segment, Climbing

The pilot concentrated on one segment and one journey — the 60 mid-size fleet accounts most ready to self-serve, per Step 7's map — not a firm-wide rollout. Launched Day 75. First Value Realization read taken at Day 80.

First Proof Point — Day 80

Sample tracking view, as the VP Commercial and Transformation Office saw it weekly

Digital Mix
22%
↑ from 10% at Day 0
Fleet Accounts Live
60
Pilot segment, full cohort
Install-Slot Fill
91%
Against the two new SLA partners
Cycle
80 / 90
Days elapsed
Financial, Market, Operational — read together Financial VPF: digital orders carry a thinner unit margin but a lower cost-to-serve once branch labor is removed. Market VPF: the marketplace competitor hasn't matched TrueTread's install-slot guarantee. Operational VPF: the constraint predicted in Step 8 — install-slot capacity — is holding at 91% fill, not degrading as volume grows.
11Verdict & Handoff · Traceability & Verdict

Day 90: Cleared the Floor, Short of the Stretch — Told Straight

WorkstreamDay 90 statusNote
Fleet self-service portalOn Target34 of 60 pilot accounts reordering online without a call
Install-partner networkOn Target2 SLA partners live, 91% slot-fill rate held through Day 90
Branch re-classificationOn Target3 of 9 planned fulfillment-only conversions complete
DIY retail DTC storefrontAdvancingLaunched Day 79 — too early in the cycle for a full read
VIP / legacy accountsStalled2 of 14 largest legacy accounts moved to self-service; the rest still call their rep

Digital Revenue Mix, by Week

Share of transaction volume placed through the digital channel, weeks 1–12 of the redesign clock

0% 20% 40% 10% 27% Week 1 Week 12 · Day 90

Pilot fleet accounts, final state (n=60)

On Target · 34 Advancing · 20 Stalled · 6
The Day 90 verdict — declared honestly, including what didn't move 27% of transaction volume, digital. The floor (25%) cleared; the stretch (40%) didn't. Every structural workstream — the portal, the install-network, the branch conversions — hit target. The one segment that stalled, VIP/legacy accounts, was flagged as the hardest case back in Step 7. That's not a miss. That's the map working.
12Verdict & Handoff · Day-91 Handoff

Day 91 Was Designed Before Day 1 Ended

The Traceability Map ties every surviving claim back through the chain: Strategy ← Business Model block ← Operating Model block ← Atomic Unit ← Test evidence. Nothing in the Day 90 verdict traces to an assumption that was never tested.

The fleet portal, the install-partner SLAs, and the 3 completed branch conversions all become standing operations, owned by the Transformation Office — not artifacts of a project that ends when the consultants leave.

VVisionizer
VP Commercial — owns the "90% digital" horizon
SStrategizer
Ops Director — converts the horizon into the next cycle's plan
MMobilizer
Digital Customer Success Lead — runs the weekly refinement cycle
The next-cycle decision Two calls, made on the evidence, not on momentum. A second Relaunch90 pass targets the VIP/legacy segment specifically — a different value proposition question, not a bigger version of this one. Meanwhile, the proven install-slot-capacity dimension hands off to a Chain Reactor cycle to scale execution now that the model itself is no longer in question.
Conclusions

The Channel That Held Without a Phone Call

One 90-day cycle turned a 10% digital channel that had been flat for three years into 27% — with every structural piece of the redesign holding, and one honest exception named instead of buried.

Day 0 → Day 90, at a glance

Day 0 Day 90
Digital revenue mix
10% → 27%
Fleet accounts self-serving
0 → 34 of 60
Branches re-classified
0 → 3 of 9
Install-partner network
0 → 2 SLA partners
Model Contract, Locked to Delivered

The full traceable chain: the metric signed on Day 10, against the number the Day 90 verdict actually confirmed — and where the trend line puts the channel mix if it holds.

10% → 27% digital mix (Day 90) · Floor 25% cleared · Stretch 40% not yet
Floor the minimum credible Day-90 proof point · Stretch the ambitious read · Trending toward the 3–10yr OKR horizon: a 90% digital channel mix
TrueTread Commercial Tire — a channel-mix inversion, still early

The Model Contract (Step 2) this cycle was run against, and the number every downstream Atomic Unit traces back to.

1

The forcing function beat the persuasion lever. Retiring phone-order-taking for the pilot cohort — with a visible escape hatch — moved more behavior in three weeks than three months of "please use the portal" would have.

2

The install-network was the binding constraint, not the website. The platform passed every test it ran. Guaranteeing a real install slot was the hard part — and the one investment that had to happen before launch, not after.

3

One non-negotiable protected the transition. No account was ever auto-migrated off phone support. Every self-service account chose it — which is exactly why the ones that moved, stuck.

4

The residual gap is relationship-based, not technical. The 12 stalled VIP accounts aren't confused by the portal — their whole relationship with TrueTread runs through one person's cell phone number. Cycle 2 has to redesign that relationship, not the checkout flow.

One 90-day cycle. A distributor built for a 90% physical channel mix, asked to prove a digital-first model could actually work — not just exist. The methodology doesn't guarantee the full inversion. It guarantees an honest, traceable answer about how far the model actually moved, and exactly where to point Cycle 2.