When your relationships live in PowerPoint

Every services BD team models its key customer relationships in some manual form. The format varies. PowerPoint org charts with color-coded contacts. Spreadsheets where each row is a stakeholder and each column is a status field. Whiteboards photographed at the end of every account-review meeting. Outlook contact folders annotated with personal notes. Mental maps in a senior person’s head, surfaced verbally during pipeline reviews. Different teams pick different tools, but the work is identical: stakeholder maps assembled by hand from meeting memory.

The reason it persists isn’t ignorance. It’s that no tool the team has tried actually does the modeling job. CRMs show pipeline. Spreadsheets show numbers. None of them shows the picture of the relationships, and the picture is what the team and their leadership actually need to make a decision.

This piece is about why visualization beats scoring in stakeholder reviews, why the manual-modeling workflow is evidence of an unmet need, and what replaces it.

The monthly ritual

The most common form of the workflow is the PowerPoint rebuild. Walk into a BD operations room at an enterprise services firm in the last week of any month and there’s at least one person updating an org-chart deck: starting from last month’s slides, updating titles where contacts have changed roles, adding the three new people the team met since the last review, recoloring contacts whose relationship status shifted from “warm” to “cooling” or vice versa. The exercise takes a senior person somewhere between four and twelve hours a month, depending on how many accounts are active.

The output is a deck. Slide 1 is the org chart for Account A, color-coded. Slide 2 is the same for Account B. By slide 6 the team has a visual portfolio of the relationships they’re tracking. Leadership reads it, asks two questions, and decides where to invest the next quarter’s BD time.

Then the deck gets stale. Two weeks later it’s already wrong, because three meetings happened that changed the picture. By month-end the senior is rebuilding it again. Teams that don’t use PowerPoint run the same cycle in a different artifact: a stakeholder spreadsheet rebuilt monthly, a whiteboard re-drawn weekly, a verbal account briefing repeated in every pipeline review. The format varies. The work is identical, and the work is manual.

The first thing to notice is that the work being done is genuinely high-quality. The senior maintaining the model, in whatever form, is doing real relationship intelligence: integrating signals from across the team, weighting recency, applying judgment about who’s actually influential versus who appears to be. The manual artifact isn’t the laziness. It’s the only output format that the team and their leadership can both consume.

The second thing to notice is what the workflow is doing that no CRM does. The CRM has every contact in the deck or spreadsheet. It can produce a list, sorted by last activity. It cannot produce the picture. The picture is what gets the decision.

Why visuals beat scores

A senior BD leader at an enterprise services firm described the dynamic in a stakeholder interview earlier this year:

“The visual plus the score works. Score alone doesn’t work. If I show a PowerPoint slide that literally has month-by-month the same chart, they get it immediately. Visually get it. It’s like, oh look at that… It bypasses their objection meters.”

“How do you visualize relationships? Right now it’s PowerPoint. Which is insane. You get a snapshot, and then next month it’s different because you’ve had different engagements. You’re always guessing.”

Two observations packed into the quote. First, visuals bypass analytical resistance in a way numbers don’t. Second, even though the workflow is insane, the senior is still doing it, because the picture is the thing that lands.

The cognitive pattern under this is familiar. Stakeholders reading a number engage their analytical resistance immediately. They argue with the number. They ask how it was calculated. They poke at the methodology. By the time the conversation reaches the decision, the number has been litigated for ten minutes and trust in the data is half-degraded.

The same stakeholders looking at a network map process it pre-analytically. They see clusters of contacts, lines that thicken or thin based on relationship strength, colors that show recency. The picture lands as a felt sense first and gets analytically validated second. The decision happens in the felt-sense moment. The analytical validation confirms what the picture already showed.

This is why “visual plus score” outperforms “score alone.” The visual carries the gestalt. The score carries the precision. Together they get the decision in fifteen seconds and survive the follow-up questions.

A scoring system without visualization is half a tool. It produces a number, the team argues about the number, and the decision stalls. SavvySpark explicitly designs around this: the Spark Score (a percentage) and the Connection word labels (Strong, Good, Moderate, Weak, Minimal) live alongside the network map view, not instead of it. The numbers and the words are there for the moments when precision matters. The map is there for the moments when the picture is what makes the decision.

What the manual workflow is doing

The fact that every team builds some version of this artifact tells you the underlying need is universal. The question is what specifically the workflow is doing that any replacement needs to also do.

It shows the org chart with relationship overlay. Reporting structure is the skeleton. Relationship strength is the soft tissue. A good stakeholder model puts both on the same page. CRMs show the contact list, sorted. They don’t put the contacts in their org positions, and they don’t draw the relationship overlay on top.

It shows changes over time. The senior in the quote above said it directly: “month by month the same chart.” The picture from this month, the picture from last month, the picture from six months ago. The change is the signal. A static snapshot doesn’t surface that this account has been quietly losing connections for three months.

It separates known from unknown. A good stakeholder model shows contacts the team has met as solid, and contacts the team hasn’t met yet as dashed or grayed. The visual immediately surfaces gaps. CRMs can’t do this because they don’t have the people the team hasn’t met yet. The manual artifact includes them because the senior knows they exist.

It separates believers from skeptics. The color coding usually has at least three states: champion, neutral, detractor. Sometimes four or five. The visual shows where the firm has support and where it has resistance, in one glance. The CRM has none of this; the team has been writing it on whatever artifact they maintain because there’s no other place to write it.

It survives the leadership review. The picture is the artifact leadership uses to make decisions. A spreadsheet of numbers doesn’t survive that meeting. A score doesn’t survive that meeting. The picture does, because the picture is how the conversation works.

A replacement for the manual workflow has to do all five of these things. Most of the alternative tools BD teams have tried do one or two and call it done. The team falls back to whatever manual artifact they’ve been using because that artifact does all five, even badly.

What a live network view does that the manual artifact can’t

A manual artifact, in any form, is a static snapshot built from memory. The cost of the workflow is the manual rebuild. The cost of the artifact’s staleness is that two weeks after build, it’s already wrong.

A live network view, generated automatically from your CRM and calendar data, does the things the manual artifact does plus three things it can’t.

It updates in real time. Every meeting that happens, every email exchange that lands, every CRM update changes the picture. The view your team looks at on Tuesday reflects what happened Monday. The senior who used to spend 8 hours a month rebuilding the deck or spreadsheet gets those hours back, and the picture is more accurate than the manual artifact ever was.

It models decay. Connections fade automatically when activity drops off, with stronger relationships decaying more slowly than weaker ones. A relationship that hasn’t had a meaningful touch in three months shows as fading even if no human has manually updated it. A manual artifact can’t do this; it shows whatever the senior remembered to update.

It surfaces gaps the team hasn’t noticed. When a connection that was Strong six months ago is now Moderate, the visualization highlights it. The team sees the change before the relationship goes inactive. The manual artifact shows the current state but not the trajectory; the live view shows both.

These three additions don’t replace the manual artifact’s strengths. They extend them. The live view does the same five things the manual artifact does (org chart with relationship overlay, change over time, known versus unknown, believers versus skeptics, leadership-ready artifact) and adds the three things the manual version can’t (real-time update, decay modeling, gap surfacing). And it does the original five with less manual work, which means the senior gets their afternoon back.

The handoff use case

The clearest test of whether your relationship visualization is doing the job is the new-BD-leader onboarding. Imagine someone joining your team next month, taking over six named accounts from a senior who’s leaving. Their first question is “what does the relationship picture look like at each of these accounts?” Their second is “where are the gaps I need to fill in the first 90 days?”

The manual workflow handles the first question badly and the second one not at all. The new lead reads the deck or spreadsheet, sees who the team has met, sees the status notes, but the artifact is a snapshot from three weeks ago and doesn’t show what’s changed since. The senior who built it is gone, so the new lead can’t ask the questions that would make the snapshot useful. The team’s institutional memory of the relationships isn’t in the artifact; it was in the senior’s head, and the artifact is the one-page summary they were leaving behind.

A live network view handles both questions in 20 minutes. The new lead walks through each account, sees the current relationship state (current, not three weeks old), filters by Connection strength to find the relationships that matter most, filters by Spark Score for the person to find the believers, and uses the change view to see which connections have weakened over the last quarter. By the end of the walk-through, the new lead has a working map of where the firm is strong, where it’s vulnerable, and which contacts to prioritize in their first month of meetings.

This is the test that matters. If the visualization survives the handoff, the firm owns the relationship asset. If the visualization is an artifact the senior built and nobody else can update, the firm is renting the asset from whoever knows the most. The manual workflow defaults to renting. A live view defaults to owning, because anyone who joins the team can read the same map and act on the same signals.

What the workflow looks like in practice

The replacement is a single live view of the relationship map, with drill-down into individual accounts and connections. Leadership reviews the portfolio at the start of every BD operations meeting: accounts trending up get a quick mention; accounts trending down get the meeting time. Reps drill into individual accounts to prep for meetings, see who on the team knows whom, and watch for connection changes that need a response. The Sparkboard ranks accounts and people by relationship strength across the entire portfolio, optimized for “where should we invest BD time next.” Same data, three jobs.

For the broader case on relationship intelligence as a category, see why your best relationship intelligence lives in someone’s head. For the measurement framework that uses these views as leading indicators rather than wins-and-losses scoring, see the broken scorecard.

To see SavvySpark’s network views in your own data, look at our solutions or start a free trial.