Part III — Keeping the book
Chapter 16
Carry it into the system that already holds the person
On the evening of September 6, 2026, three entries were waiting for my word in a new app my team had built inside HubSpot, the system where we already keep the records of everyone we work with. Each one was value I had received myself. I tapped Confirm on all three.
The next morning I was on a call, walking someone through what we'd been building, and I described it this way:
"Now that I'm two apps in, because what was here yesterday was three decisions waiting for me to confirm the value, and I clicked the button and … went away and HubSpot's updated."
It isn't an elegant sentence. Look at what's missing from it. I didn't open a spreadsheet. Nobody emailed me a form. The value was waiting where I already work, I gave my word, and the record changed.
That's the whole idea of this chapter, and it's the only one in this book that depends on our software. If you don't use HubSpot, read it for the shape. Every move under "What to do" works in any system that already holds the records of your people.
What this is
This chapter is Chapter 1's view, grown up. Chapter 1 asked you to open one view inside whatever system already holds the record of the person. When I ruled on that wording, I said what the view is in our own system: "In HubSpot, it would be a CRM Index View." This chapter puts the book on the records people already open every day, puts the confirm action where the person whose word counts will actually see it, and builds the rules of the practice into the software, so that no screen can quietly break them.
Our vocabulary has a word for why it matters where the book lives, Value Visibility: "Making real value legible across a relationship. Counterintuitively, showing someone the value they received is often what completes it — visibility is not the report you file afterward, it is part of how the value becomes real."
How to tell where you are
- Your book of value lives in a document or a sheet that nobody opens while they work.
- To confirm something, a person has to leave the tool they're in, or wait for someone to send them a form.
- The person a moment of value is about can't see it anywhere they normally go.
- The value and the money live in different systems, and get compared from memory.
- If somebody asked your software for a total across both lanes, the outside lane for value that reached people outside your own side and the inside lane for value your own side received, or for a score per person, it would happily produce one.
What to do
1. Put the account on the records people already open. In our app, a short card on a person's record, a company's record and a meeting's record lists the moments linked to it: what that person received, what they did, what they confirmed. It's ordered newest first by when the value happened, never by when the entry was typed in. Money shows as a quiet marker. There are no tallies, and the card can't confirm anything. A project gets a tab of its own, and a deal gets a card that walks from the deal to the moments its company and its people carry, without ever showing a total for the deal.
Beside the book, our system now holds a second, smaller kind of record: the CARE record from Chapter 2. It says who a piece of work is for, what we hope it makes possible, and what we've promised along the way. It's linked to the people it's for, to the project, to the entries that come from the work, to the goal it serves, and to a task for anything we've promised to come back with. It has no stage and no amount, and there's nothing in it to confirm.
And an entry can now be opened before the value has happened. It starts at Expected, the first stage, with what one person is expected to receive, written in words, and the day that was written down or said. When the value lands, the same entry moves to Witnessed, and what landed is written from the evidence, not copied from what was expected.
If you lead by KPIs today. On a project or a deal, the number you'd look for is a total, and our cards show none. What you get in its place is the moments themselves, and a CARE record on the project is how what leadership meant reaches the system of record, right beside them. Chapter 13 shows how to read the two together in place of the number you used to steer by.
2. Put the confirm action on the entry itself, and only in front of the right hand. On the entry's own card our app offers three buttons: Confirm, Dispute and Not shown. They appear only when the signed-in person is a hand our rules allow. For value inside the team, that's the receiver, or the leader linked above them. The person who did the work never sees them. On an entry about someone outside the team, nobody on the team gets the buttons at all, because that confirmation has to be the outside person's own words or act. And since a fix we shipped in October 2026, someone who can't confirm an entry doesn't see a button, rather than seeing one that would fail when pressed.
3. After the tap, read the record back. Our app doesn't trust what it thinks it just wrote. It reads the record again and shows what the record says now. If the write was refused, it shows the refusal in plain words.
4. Give the book one page, and open it on something real. Our app's page opens with one plain sentence about what the app is for, and right under it a real example from our book that you can open all the way down to its evidence. It's the entry that holds my sentence from the top of this chapter. Then come the entries waiting on someone's word, in two halves. One half is the entries the signed-in person can confirm. The other half is the outside entries, and there's no button on those, because the confirmation has to be theirs. The page says it in one line: "Value received outside the team is confirmed in the receiver's own words. Show them the evidence, then save their reply on the record." Entries that still need evidence, and placeholders still waiting for someone to say what happened, are held apart in their own closed sections. Then the month's two numbers, under the heading "Marked confirmed, by month", side by side and never added. An empty month shows two zeroes, and every figure opens onto the entries behind it. The figures for the whole book and the one export sit in a closed section for whoever reconciles the book. The export produces two separate tables, one per lane, never one sheet.
The first version of the page opened on a single sentence about what was true across the whole book, which is how I'd ruled it in September. In October 2026, getting the page ready to show to partners, we moved that sentence and the whole-book figures into the closed section and led with the example instead.
5. Build the refusals into the software itself. Our app refuses leaderboards, targets, a score or rate for any one person, and any total across the two lanes. Those refusals don't live in a note on one page. They live in the one shared calculation that every screen in the app reads, so a new screen can't bring them back by accident.
6. Show money quietly, and leave a place for the invoice-date check. Money sits beside the entry as a small marker and never moves it from one stage to the next. Leave a place for the money check this practice cares about most: was the value confirmed before the invoice went out? That check compares two dates, so it needs an invoice date on the order record. Decide where yours will come from before you promise the check.
7. Know who is signed in, and which record is theirs. Our app works out whose word it is from the login. When one person has two records, they confirm on the record their login points to, and that isn't always the record their value is attached to. Our rulebook names that limit instead of hiding it.
8. Send every write through one door. Every confirm in our app goes through a single write path that runs the same checks as everything else that writes to the book.
How you know it worked
A person confirms their value where they already work, without being sent somewhere else to do it.
The evening at the top of this chapter is what it looks like: the value was waiting where I already work, I gave my word, and the record changed.
For someone outside the team, build it so a buyer opening a quote sees the moments recorded for them. Opening it marks those moments Shown, and they're asked, plainly, whether it's right. Confirmed comes only from something they do that leaves its own record, like a signature, a reply or a purchase, because anyone can forward a quote link and the software can't prove who tapped. You know it worked when a buyer reads their own moments there and says "yes, that's what happened."
Where it goes wrong
A separate tool for the book. Keeping the book in an app of its own, apart from the system where you already work with the person, is the SaaS Trap: "Fragmenting the context your people rely on — where each rational tool purchase silos the intelligence needed to serve customers." The book belongs on the record that already holds the person.
The software shows a buyer the wrong thing. Before our app existed, one piece of our quote setup already read the book. When we looked at it in September 2026, it showed a confirmed entry as still waiting, it didn't keep the two lanes apart, and when a buyer's company had no confirmed value it would show that buyer a demo record instead. A real buyer would have been looking at an illustration presented as their own account. Repairing it was the first thing we ruled the quote work had to do.
A button the person can't use. For a while our app showed a Confirm button to people on entries they had no standing to confirm. Pressing it would have failed. We took the button away from anyone the rules don't allow.
One person, two records. If your system holds more than one record for the same person, decide which one their word lands on before you put a confirm button in front of them.
A write that goes around the door. An entry written outside the one write path never has the checks run on it. A single door only protects the book if every write uses it.
Rules on the screen instead of in the calculation. The first version of our page carried the team's internal rule citations right there on screen, beside the buttons. In October 2026 we took them off and put plain words in their place. The rules belong in what the software does, not in the words on its buttons.
The software gets ahead of the practice. A page can show any month's two numbers. It can't close a month. Closing the month is a practice (Chapter 11), and until someone runs it, the software is showing an open month in a tidy frame.
Read further
- In this book: Chapter 1, on opening one view with no software at all; Chapter 2, on the CARE record; Chapter 7, on showing value to the person it was for; and Chapter 11, on closing the month.
- The Value Creation Protocol, Chapter 19, "The Four Unified Views". The first of them, the Unified Customer View, is "Every relationship signal in one place," which is the place this chapter asks you to carry the book.
- The Value Creation Protocol, Chapter 6, "The SaaS Trap", on why one more tool fragments the context people rely on.
- The Value Era, Chapter 15, "In its own kind", on what gets kept and who gets to say so.