Illustrative mock-up · Figures are synthetic and shown to test the design, not to report performanceAsurion & SaxeCap confidential
RAM Command Center
Four modules · v0 concept
Week of 10 August · AT&T SoutheastD. ReyesDR
Monday · 6:40am · ran overnight
What changed in your accounts
Detection runs against each store group's own history inside its partner environment. Nothing is compared across partners.
7 signals worth a look · 12 more found and held backCapped at 7 so the week stays readable
Held back: you raised a Memphis record two weeks ago, and repeating it this soon weakens both. Available if you want it.
Leads this week · the inverse of a kudos
There is no pipeline in this business; there are regions. These are growth opportunities hiding in plain sight in data you already own, proposed for you to take or leave. Either answer becomes part of the record.
Lead · gap to best comparableStore 5502 is 1,100 points behind the best comparable store in its own cohortAT&T · home · vs 4471 at 21.3% · same partner, same format, same market tier
Lead · sustained declineMurfreesboro has declined five straight weeks on mobilityAT&T · 5 stores · mobility · worst week in its last 30 landed inside the run
Each take or pass is a moment of decision on the record: proposed 12 Aug, answered by you. This quarter you have taken 9 of 14 proposed.
Monday · signal 1 of 7
The storyline, ready to walk through
Headline first, then the evidence behind it, then what to actually say. This is the artifact for Thursday's session, not a report to be turned into one.
Local draftAdapted for D. Reyes · AT&T Nashville Metro · written 6:41am
Nashville Metro just had its best home week ever.
Not its best this quarter. Its best in the 78 weeks we have data for, and it was led by the stores you have been working with since June.
What sits behind it
15.6%home take rate, week ending 8 Aug
14.1%previous best, week of 29 Mar
+1.5 ptsabove the old record
4,210opportunities, roughly in line with the 8-week average
9 of 12stores above their own 8-week average
21.3%store 4471, the strongest in the group
Home take rate, last 12 weeks
Compared against Nashville Metro's own history. No other partner's data is used.
What to say in the room
Open with the record itself. It is the kind of number a district manager will want to take back to their own leadership, so give them the framing to do that.
Then ask what changed at 4471. It moved 6.2 points after being flat for nine weeks, and their team will know why in a way the data cannot tell us. That answer is worth more than the record.
Close by offering to run the same pattern at 2210, 3187, and 5502, which are the three still under their own average.
Setting aside asks for a one-line reason. That reason is what teaches the ranking.
Tuesday · standing steers reviewed
Two priorities collide
The enterprise wants home this quarter. This client asked you to lead with mobility. We will not quietly pick one, so both are here and the choice is yours.
Conflict found · Nashville Metro · the enterprise push and this client's standing steer point in different directions this week
From the enterprise
Lead with home attach through Q3.
Set by Revenue leadership on 1 July, applies to all AT&T store groups.
Reaching 128 of 134 accounts this week.
This week's home signal for Nashville is a record, which is the strongest version of this push you will get.
versus
From your client
Do not lead with home right now.
Captured by you on 28 June after the district review.
Client's words: the district is in mobility upgrade season and home reads as a distraction until October.
Applied without asking for 6 weeks.
How do you want to play it
Wednesday · ready for Thursday 10:00
The pack for Thursday's session
Assembled from what you kept, in the order you put it. Nothing here has been sent anywhere.
AT&T Nashville Metro · weekly review
Thursday 14 Aug · district leadership
Open with
Mobility upgrade season is landing. Chattanooga has moved four weeks running.
Up 2.9 points across the run, with the gain spread across six of eight stores rather than concentrated in one. Ask what the upgrade floor plan looks like heading into September.
Then
Nashville Metro just had its best home week ever.
15.6% against a prior best of 14.1%, led by store 4471 at 21.3%. Worth raising even though home is not the focus, because it is a record and it came from the stores you have been working with since June.
You shortened this from 4 sentences to 2
If there is time
Three stores are under their own average and could use the same pattern as 4471.
Stores 2210, 3187, and 5502. Offer the visit rather than flagging the gap, so it lands as support rather than as a scorecard.
This pack
Storylines kept3 of 7
Edited by you1
Set aside4
Steer appliedMobility first
Time to draft6 min
How much detail
Before it leaves
Cross-partner dataNone used
Your approvalRequired
StatusNot sent
Thursday onward · the part that compounds
What we learned from this week
Every kept, edited, and set-aside storyline is a training signal. This is the loop that turns a generator into something that gets better.
78%
Storylines used with light or no editing
Up from 61% in week 1
12%
Median share of a draft you rewrote
Down from 34% in week 1
94%
Cycles where your standing steer was applied correctly
Target is 100%
6 min
Your time from opening this to an approved pack
Baseline being measured
Why storylines were set aside
Client does not care about this line41%
Already covered it recently24%
Too small to be worth the airtime19%
The framing was wrong for this room11%
The number looked wrong5%
What happened after delivery
Store groups where a storyline was delivered31
Comparison group, no storyline delivered28
Take rate, 4 weeks after · delivered+0.7 pts
Take rate, 4 weeks after · comparison+0.4 pts
Weeks of data so far6
Not yet attributable. Six weeks is not enough to separate this from seasonality or from which store groups happened to get a storyline. The comparison is running so that the question can eventually be answered, and the honest answer today is that it cannot be.
Distilled per RAM so a manager of five sees the pattern, not the transcript: how often the
recommended course was held, deviated from, or retired. A rising deviation rate is a signal to
talk, not a score to punish.
What this makes possible later
Both depend on the account and activity layer this module is quietly building underneath it.
Later build
Activity Tracker
One record of store visits, commitments, and follow-ups, replacing the roughly 50 separate solutions in use across the field today.
Gate: this arrives only after the insight engine has been useful for a while. A tracker that shows up first reads as being watched.
Later build
Daily Advisor
What to do today, ranked against account state, open commitments, and where performance is moving.
Gate: needs the activity record to exist first. There is nothing to reason over without it.
Module · runs underneath everything above
Account Data Foundation
The account and activity layer that does not exist today. Every screen in this demo reads from it; none of them could run without it.
Initial build · thin sliceWhat ships first is exactly what the insight engine needs: entities, hierarchy, coverage, history, and steers. The activity record shown at the bottom arrives with the Activity Tracker.
One spine from partner to store
PartnerAT&TOwn environment · own governance1,240 stores
RegionSoutheastD. Reyes + 3 other RAMs214 stores
GroupNashville MetroCovered by D. Reyes · 78 weeks of history12 stores
Store4471 · Green HillsHome 21.3% · strongest in group2 lines
Store2210 · RivergateUnder own 8-week average · 3 weeks2 lines
GroupChattanoogaCovered by D. Reyes · 71 weeks of history8 stores
Feed health, checked before any insight is written
FeedLatest arrivalHistory depthStatus
AT&T performance · opportunities and take rateMon 6:02am78 weeksFresh
Sales hierarchy and RAM coverageSun 11:40pmCurrentFresh
Verizon performanceFri 6:15am64 weeksStale · held
Steer store · client and enterprise prioritiesLiveSince launchFresh
The Verizon feed is two business days old, so no Verizon storylines were generated this cycle. A storyline built on a partial week would reach a client with Asurion's name on it.
Partner separation is structural, not a rule
AT&T environment
Compared only against its own history and within-partner cohorts.
Verizon environment
Same schema, separate store. No join to any other partner exists.
Amazon environment
Same pattern. A cross-partner comparison is impossible by construction.
The schema is shared so the engine can reason the same way everywhere. The data is not.
Arrives with the Activity TrackerVisits, commitments, and contacts join this same spine, which is what makes the Daily Advisor possible. Nothing else in the foundation needs to change to receive it.
Module · later build, shown illustratively
Activity Tracker
One record of visits, commitments, and follow-ups, replacing roughly 50 separate solutions across about 150 RAMs. Shown here as it would work, not as a commitment to build it now.
Later build · illustrativeSequenced after the insight engine has earned trust. A tracker that arrives first reads as being watched; one that arrives after the tool has helped reads as memory.
Capture in one line, not a form
"Visited 4471 this morning, walked home attach with the store manager, promised to send the new planogram by Friday"
ActivityStore visit · 4471 Green HillsTopicHome attachContactStore managerCommitmentSend planogram · due Fri 15 Aug
Typed or spoken, one line becomes a structured entry. The RAM confirms the four fields; nothing is filed silently. Existing signals help complete the story: a client meeting on the calendar drafts a visit, an email thread that matures into an RFP drafts a commitment. Never ambient monitoring, never location.
This week, one record
MonVisitStore 4471 · Green HillsWalked home attach with SM · planogram promised1 commitment
TueCommitmentSend updated planogram to 4471Made Mon during visitDue Fri
TueVisitStore 2210 · RivergateUnder own average 3 weeks · coached greeting-to-offer handoffFollow-up set
WedCommitmentShare 4471's floor pattern with 2210 and 3187Offered in last week's session · carried forwardOpen · 6 days
ThuVisitStore 3187 · Hixson PikeDrafted from a calendar invite · confirmed by you in one tapAuto-captured
What this replaces
Solutions in use across the field today~50
Google Docs, Excel, email, memory→ one record
Commitments visible to anyone but the RAMToday: none
What it feeds
Daily Advisor priority queueRequires this
Inflection detection ("turned after your visit")Sharpens
QBR assembly · what we did, what movedUnlocks
Open question, flagged deliberately. Any capture that reads email, text, or chat needs the privacy and review constraints settled before design, not after. What is shown here relies on what the RAM enters or confirms: calendar and email-derived entries arrive as drafts and are filed only when the RAM taps to confirm.
Module · later build, shown illustratively · Thursday 7:05am
Daily Advisor
The destination experience: what to do today, ranked against account state, open commitments, and where performance is moving. Every line traces to something real in the record.
Later build · illustrativeNeeds the activity record to exist first; there is nothing to reason over without it. Shown so the direction of travel is visible, not to pull it forward.
Today, in order
1Nashville Metro session at 10:00. The pack is approved and loaded.Mobility leads per your steer decision Tuesday. The home record is your closing line. District manager asked for mobility focus on Monday's call, so the room is already leaning your way.Calendar
2The 4471 planogram is due tomorrow. Ten minutes today keeps the promise easy.Committed Monday during your visit. 4471 is your strongest store and the anchor of Thursday's storyline; a missed promise there costs more than it would anywhere else.Commitment
3Store 3187 has slipped a fourth week and has had no visit in six.The only store in the under-baseline trio with no contact this month. You offered to share 4471's floor pattern with them last week; doing it on a visit turns a scorecard into support.Drift
4Chattanooga's mobility run is one week from being a five-week story.If Friday's data holds the trend, next week's session opens itself. Nothing to do today except know it is coming.Signal
Ask about your book
Ask anything, e.g. "which stores haven't I visited since July?"
Illustrative mock-up prepared by SaxeCap for discussion with Asurion. Store groups, take rates, opportunity counts, and all
learning metrics are synthetic and exist to test the interaction design. They are not Asurion figures and should not be read as
performance. Structure follows the RAM Command Center exploratory initiative document. Asurion and SaxeCap confidential.