The Graph Sandwich: Connecting the Business Behind the Numbers

I’ve seen a common pattern in businesses: sales and finance struggle to connect their views of revenue. Sales works in the CRM. Finance works through invoicing and financial reporting. Both track new business, renewals and expansion. Connecting those activities to the financial results takes more work than it should.

The reports get produced. Explaining how the business produced those results is harder. You can see that a customer renewed. You may have no idea how much work it took to get there, what went wrong along the way, or what that renewal actually cost you. Those are the questions you need to answer before deciding what to improve.

01Put the team maps together

Every team has a map of its part of the business. Sales can trace an opportunity to a signed agreement. Operations can trace a customer commitment to the work required to deliver it. Finance can trace an agreement to invoices and payments. The trouble starts where those maps stop. Who can follow a promise in the sales process all the way through to the customer’s experience and the financial result?

I call that connected view a “graph sandwich.” I’m borrowing the name from mathematics for a business metaphor. And yes, I do love a good sandwich. Here, the ingredients are the maps each team already uses. Connect them through the same customers, agreements and events, and you can follow how work in one team affects another.

Build the view around the question you need to answer. For a revenue question, connect acquisition, sales, delivery and retention. For a financial-operations question, connect contract changes, billing, disputes and collections. Those views overlap wherever the same customer or event touches both. A renewal is a useful place to see why that matters.

02Same ARR, different economics

Consider a hypothetical customer whose $100,000 annual subscription renews at the same value, with no gap in service. Under unchanged ARR rules, the customer contributes $100,000 before renewal and $100,000 afterward. The number has not moved.

But suppose keeping it there took six months of negotiations, service reviews, revised proposals and internal approvals. Sales spent time defending the account. Operations investigated complaints. Finance untangled billing questions. You retained the same annual value, but it took far more internal resources to do it.

That effort has a cost. Additional spending eats into profit; time absorbed by this account is unavailable for other customers. Even if payroll stays the same, the business has used more of its capacity to retain the same ARR. The top line can look steady while the economics underneath it get worse. To improve those economics, you need to find what created the extra work.

03Follow the problem across the maps

Start with the renewal and work backward. Connect the signed agreement to the negotiations, the negotiations to the issues raised, and those issues to the work involved. Preserve dates and responsibilities so you can establish the sequence. In our hypothetical example, suppose the customer repeatedly raised a billing dispute during the renewal discussions.

The revenue view puts that complaint in context. It connects how the customer was won, what they were promised, what they received and whether they renewed. Across accounts, you can use it to examine whether your demand generation brings in customers you can serve profitably. For this account, the immediate question is why a billing complaint made the renewal harder. Answering it takes you into financial operations.

Through that operational view, you would trace the agreed terms into billing, then follow the invoice, dispute, correction and collection. Suppose a contract amendment never reached billing. The customer received an incorrect invoice, challenged it and had to repeat the explanation to several people. Finance could eventually correct the bill while the customer was still frustrated by the experience.

Now the two views connect. A missed contract update created a billing error. The error created customer friction and internal rework. That friction resurfaced during renewal and added to the effort required to retain the account. In a real investigation, the records and conversations would need to support each link. Together, they help explain how an operational problem can affect customer experience, margins and future revenue.

This gives leaders a more useful diagnosis. The CFO can see the cost of resolving the dispute. The COO can see where the handoff failed. The CEO can assess whether the same problem is making other accounts expensive to retain. The next challenge is investigating enough relationships to know whether this is an isolated incident or a recurring problem.

04Use AI to investigate in parallel

Across hundreds of customers, there may be many paths to examine: contract changes, delivery issues, billing disputes, support escalations and delayed approvals. Reconstructing each one by hand takes time. This is where I would use AI agents to help assemble the connections and compare possible explanations.

For our renewal, one agent could examine the contract and amendments, another the invoices and disputes, and another the support and renewal history. They could work in parallel, then bring their findings into a shared timeline tied to the same customer and agreement. Each finding should point to its source and distinguish a confirmed event from a possible explanation.

The aim is to make troubleshooting clearer: where did the records diverge, which issue kept resurfacing, and what else might explain the delay? That gives the team specific connections to check instead of a pile of documents to reconstruct. It also gives leaders a way to delegate the investigation across accounts, while retaining responsibility for the conclusions and decisions.

05Choose the fix and track the return

Once the investigation identifies the break, the intervention becomes more specific. In our example, it might be making sure approved contract changes reach billing, assigning an owner to exceptions and checking that the next invoice reflects the agreed terms. If the actual problem were a delivery commitment the product could not meet, the fix would belong elsewhere.

Before making that change, establish what the problem costs today and what improvement would count as success. Track invoice disputes, time spent resolving them and the work they add to renewals. Then compare the benefit with the cost of implementing and running the fix. Use those measures to estimate ROI, including the cost of AI and the review its output requires.

Keep the benefits honest. Hours released are capacity you can put to better use; they become cash savings only when spending falls. Shorter disputes and smoother renewals may also improve the customer experience and protect revenue. Track those outcomes over time so you can tell whether the change is helping. A plausible explanation earns a test. The results determine whether to expand it.

06Make it a leadership habit

As a CEO, I would start with a customer: how much they pay, how much revenue the business recognizes from that relationship and what it takes to win, serve and retain them. Then repeat across customers. Have multiple AI agents assemble and compare the relevant histories in parallel, so the leadership team can spend its time on the patterns, decisions and results.

Those patterns reveal where to test your value creation drivers. Poor customer fit may point to targeting and qualification. Repeated delivery failures may point to promises or capacity. Recurring billing disputes may point to contract handoffs. The graph sandwich helps connect each financial outcome to a part of the business you can investigate, assign responsibility for and improve.

Return to the $100,000 renewal. Next year, ARR may still be $100,000. But if the customer gets the right invoice, the dispute disappears and the team spends less time rescuing the relationship, that same ARR can cost less to retain. Now you can explain the result, what it took to produce it and whether your changes made the business better.