The one word that was hiding three problems
Okay, so here is a sentence, and I want you to sit with it for a second before we say a single thing about who said it or what company they work for. The vendors do not answer, and when they answer they do not commit, and when they commit they do not arrive. Hm. Right? That is one person describing one problem. Except it isn't one problem. It is three, and they have almost nothing to do with each other. Yeah, and that is the whole thing today. One word doing the work of three, and what happens to a proposal when nobody notices.
And the reason we are doing a deep dive on this at all is that the word was scheduling. That was the word. Right, when she was asked directly, straight out, what is the problem, the answer was scheduling. And if you stop there, and honestly most people would stop there, you go build a scheduling product. Exactly. You go build a calendar. Which would have been, I mean, it would have been a completely reasonable thing to build, and it would have solved possibly one third of the actual problem while being sold as if it solved all of it.
Northwind, twelve buildings, one metro
So let me set the table properly, because the source material here is a briefing document for an account, and it is very deliberately not a build plan. It says that about itself. It does. It says right at the top, this is not a build plan. It is about who is on the other side of the table, what they are actually buying, what it would cost to deliver, and where the line is past which this is just a bad account to take. Which is a much more interesting document than a build plan, frankly. Way more interesting.
The client is Northwind Residential. Twelve buildings, all in one metro. Run day to day by an operations lead, and the brief calls her Marisol Vance. And the very first thing the brief tells you about her, before anything about the buildings or the portfolio or the tooling, is that she is not the owner. Yeah, and that is not a throwaway biographical detail. No. That distinction does more work than anything else in the entire document. Because of what follows from it. Right. She can say yes to a pilot, and she cannot say yes to a contract.
And those two conversations, this is the line that got me, those two conversations have never once happened in the same room. Never once. So you have a person who can hand you a yes that feels enormous. Feels like a win. Feels like a huge win, and it is structurally incapable of turning into revenue on its own. And you will not notice that, because the yes is real. She means it. Oh, she absolutely means it. She just cannot deliver the other half, and nobody in the process is set up to notice the gap.
The committee that has never met
So who can? Well, that is where it gets properly uncomfortable. The brief describes the buying committee as three people who have never been in a meeting together. Ever. As a committee, at least, as far as the day produced any evidence for. Okay. So Marisol runs the work. A part-owner signs. And then there is the third one. Right. A maintenance supervisor who holds a veto that nobody ever wrote down. Nobody wrote it down. It is not on an org chart, it is not in a procurement process, it just exists.
And I want to be careful here, because the brief is careful here. It does not paint him as some obstructionist. No, it explains him. It says he is the one whose week gets worse if dispatch goes wrong. That is it. That is the whole mechanism. He is downstream of every decision made about this, and he absorbs all of it. And then there is one more fact about him, which I think is the actual load-bearing one. Go on. He has watched two systems get bought over his head. Twice. Two times somebody bought something that landed on him.
So he is not skeptical because of his personality. He is skeptical because of his history. Which is, I mean, that is a rational skeptic. That is the most rational person in the building. And the brief draws the conclusion out very plainly, and I will just read the shape of it, because it is the sharpest sentence in the section. A pilot that lands with Marisol and never reaches the supervisor buys a champion and an opponent at the same price. Ooh. At the same price. Same money, same effort, and you get one of each.
Three failures wearing one word
Okay so let us go back to the three failures, because everything else in this document hangs off that split. Right, and the brief is very disciplined about it. It takes the one word, scheduling, and it cuts it into three, and each of the three has a different owner and a different fix and a different price. So, one. The vendors do not answer. That is reachability. That is a reachability problem. Measurable, automatable, and the brief calls it the honest wedge. Honest is doing work in that phrase. It really is.
Two. They answer, but they will not commit to a window. And this one, the brief says, is a contracting problem. Not a software problem. Not a software problem, and this is where I think most teams get fooled, because it looks like software. It absolutely looks like software. It shows up in a system, right? You can see it in a system. There is a field for the window and the field is empty, or the field is vague, and so your brain says, well, that is a system problem, I can fix a system.
Nothing happens to him if he misses it
But the reason it is empty is the reason the brief gives, and it is one sentence. Say it. The reason a vendor will not commit to a window is that nothing happens to him if he misses it. Nothing happens to him. That is it. That is the whole thing. And read it again, because you can build a system that records a commitment, and displays a commitment, and reminds everybody about the commitment, and sends three notifications about the commitment, and you have changed absolutely nothing about whether that commitment was ever worth making in the first place.
Right, because the thing that makes a commitment mean something is not that it is written down. It is that there is a consequence attached to the other side of it. And there is not one here. There is not one, and that is not a thing a dispatch tool can conjure. You cannot ship a consequence. You cannot ship a consequence. It has to be negotiated by somebody who has leverage, and that is a contract conversation, which, remember, is with the person Marisol cannot get you in a room with. Oh. Yeah. It loops right back.
Okay and then three, which is the big one. The vendors commit and then they do not show up. Do not arrive. And the brief calls that a supervision problem, and then adds the detail that makes the whole account difficult, which is that it is the one that actually costs Northwind money. That is the one with the dollars behind it. That is the one with the dollars. So look at the shape of what we just built. The failure they will pay to fix is the one furthest from anything we can honestly build.
The demo that gets heard as a promise
Which gives you the trap, and the brief states it as a trap in exactly those terms. A demo that solves reachability will be received as a promise about arrival. And I love that it says received, not misunderstood, or miscommunicated. Received. It is not a slide problem. It is not a slide problem. You cannot deck your way out of it. Because think about the buyer's position for a second. She said the word scheduling. Her word covers all three. Her word covers all three, so anything you show against any one of them lands as a claim against the word.
So she is not being unreasonable when she hears more than you said. No, she is being completely reasonable, given the vocabulary she has. And you walk out of the room with a signature on a pilot and a belief on the other side that you have promised something you have not built and structurally cannot build. Which is a great way to lose an account in month four. Month four, and lose it while doing exactly what you said you would do. That is the part that stings. You deliver, and you still fail.
What the day did not produce
Okay, section three of the brief, and this is my favorite section, because it is a list of holes. Right, it is literally titled what the day did not produce. And there is a line before it that I think should be tattooed somewhere, which is that a proposal that quietly fills these in is fiction. Quietly is the word. Quietly. Because nobody fills them in on purpose. No, you fill them in because a proposal template has a box, and boxes want numbers.
So, hole one. There is no unit count that two people agreed on. And this is twelve buildings, which everybody agrees on, and then units, where the range that got offered was, and I am quoting the shape of this, wide enough that the midpoint is not a number, it is an average of two guesses. An average of two guesses. Which is such a precise way to say it. It is, because an average of two guesses looks exactly like a number when you put it in a spreadsheet cell. It looks identical. There is no visual difference. None. And then you multiply by it.
Hole two, no vendor list. They were told about fifteen. And shown four. Shown four. And the brief just leaves that gap sitting there without dramatizing it, which I appreciated. Hole three, no current spend. So no idea what the existing dispatch tool costs. Not the tool's cost, and not the supervisor's hours either, neither of which was available. Which means you have no denominator for any value argument you would want to make. Right, you cannot say we save you X because you do not know what X is currently costing.
The definition that does not exist
And then hole four, which I want to spend real time on, because I think it is the worst one. Go. There is no definition of a missed appointment. None. Not agreed, not written, does not exist. And the brief's conclusion is that without one, any success metric you write is unfalsifiable. Unfalsifiable. Which, let me just unpack that word, because it sounds academic and it is not. It means you cannot lose. Right. And if you cannot lose, you cannot win either.
Exactly. If nobody can point at a specific event and say, that one, that was a miss, then at the end of the pilot you have two sides looking at the same three months and each one has a completely defensible story about what happened. And no way to resolve it. No mechanism to resolve it. And here is the thing that connects it back, which I do not think I caught on the first read. A missed appointment is precisely the place where did not commit and did not arrive become impossible to tell apart. Oh, that is right.
Because in the record, in whatever system you are looking at, a vendor who never really agreed to Tuesday and a vendor who agreed to Tuesday and blew it off look identical. Identical row. Same row. And those are the two completely different failures with completely different fixes that we spent the last ten minutes separating. And they collapse right back together at exactly the moment you need to measure something. And the fix for this is cheap, is the maddening part. It is a conversation. It is one conversation.
So why does it not happen? Because it is the first conversation where the two sides can actually disagree. Ah. Everything before that is pleasant. Everything before that is vision. And the moment you say, right, define a miss for me, somebody has to take a position, and the positions might not match, and that is uncomfortable, so it gets deferred. And it gets deferred forever. It gets deferred right up until the review meeting where it decides everything.
Cost to serve, and the number nobody has
Okay, cost to serve, and this section is short and brutal. So the delivery estimate is weeks of forward-deployed work. And the tell here is what it is measured against. Right, there was an internal guess of one week. One week, which was withdrawn as too ambitious within a day. Within a day. And I think the withdrawal is more informative than either number. Say more. Well, a one-week estimate that survives is optimism. A one-week estimate that gets pulled inside twenty-four hours means somebody actually looked.
Fair. So the fixed cost is most of one founder for a month. Which is stated completely flatly in the brief, no editorializing. It does not need any. And then the variable cost, which is where it gets genuinely uncomfortable, because the variable cost is unmeasured. Not high, not low. Unmeasured. Nothing on record states a cost per dispatch call, or per vendor confirmation, or per re-attempt. And no maximum time-to-first-contact has ever been set. So there is no bound on the thing at all.
And then the hardest sentence in the document, which I want to read close to straight. That numerator is ours. Nobody outside can answer it, and nobody inside has computed it. Oof. And until somebody does, neither the price basis nor the walk-away threshold can be evaluated. Which is a really unusual thing to write in your own account brief. It is, because it is not a criticism of the client. No. It is entirely aimed inward. The client cannot help with this one. The client could not help even if they wanted to.
Per unit, per dispatch, per unknown
Which takes us straight into pricing, and pricing here is four open questions rather than four options. So option one, per unit. Which is the industry default, basically. And it is actively resented, and the reason is specific and it is good. Go on. Their current tool bills them per unit, against a fraction of units that ever generate a ticket at all. Ah, so they are paying for doors that never do anything. Paying for doors that never do anything, which feels like a tax, and they have noticed.
And I want to flag, the reason matters more than the fact. Because if you just write down, they do not like per unit, you have a preference. Right, a preference you might argue them out of. But if you write down the reason, you have a structural argument, and the structural argument tells you what to propose instead. Which is option two, per dispatch. Untested, but it fits how Marisol already thinks about the business. Because, and this is a lovely detail, she counts tickets, not doors. She counts tickets, not doors.
Option three, per vendor seat, which was never proposed and is simply unknown. And the brief says unknown and then just stops. Which I respect enormously, because that is exactly the place a normal document would speculate a shape for it. And then option four, which is not an option, it is the ceiling. The ceiling is unknown. Unknown, because no payroll figure, no tool spend figure, no turn cost figure exists anywhere in the record. So both ends are missing. Both ends. You do not know your own floor from the cost-to-serve section, and you do not know their ceiling from this one.
Refusals, not milestones
So then how do you make any decision at all? And this is where the document does something I really liked structurally. It does not write milestones. It writes refusals. Refusals. Things that must be refused rather than targets to hit. And the grammar is not a stylistic choice, it is the whole point. Because what happens to a milestone? A milestone gets slipped. A milestone gets quietly slipped in a status update, and everybody nods, and it moves two weeks, and then it moves again.
Whereas a refusal fails loudly. It has to. It is written as a thing you are not allowed to proceed past. So there are four. One, no contract conversation with a signer inside six weeks. That is the Marisol problem, formalized. Formalized with a clock on it. Two, the supervisor is not in the room by the second session. That is the veto problem with a clock on it. Yeah, and notice both of those are about people, not about product.
Three, a definition of missed appointment cannot be agreed. So that is the unfalsifiable problem, and it is written as a refusal rather than a nice-to-have, which I think is correct. And four, phase one gets scoped to arrival rather than reachability. And this is the one I would bet on being broken. By the client? No, by us. Oh. By our own enthusiasm. Because arrival is the demo everybody wants to give. It is the impressive demo. It is the one that makes the room go quiet, and it is the one we cannot honestly promise.
What survives is smaller than it sounds
So what actually survives all this? The wedge is reachability. And only reachability. Only reachability, and the brief gives three reasons, and the order is worth paying attention to. One, it is measurable on day one. So you can show something immediately. Two, it does not require the supervisor's cooperation to demonstrate. And three, it is the only one of the three failures we can honestly promise to move.
And I think the middle one is the underrated reason. Say why. Because everything else in this brief says the supervisor can sink the account. He has the unwritten veto, he has been burned twice, he is not in the room. Right. And reachability is the single thing you can prove works without needing him to lift a finger. So it is the one demonstration that cannot be blocked by the person most likely to block you. Which is a strategic fact dressed up as a technical one.
And the honest part, which I want to end on, is that this is a smaller promise than the buyer wants to hear. Much smaller. She said scheduling. She meant, at minimum, the vendors will show up. And what is on offer is, we can reliably reach them. Which is a third of the word. It is a third of the word, and saying that out loud, in the room, to the person who wants to hear the bigger version, is basically the entire discipline this document is recommending.
Yeah. And it is worth pulling one general thing out of it before we stop, because it is not really about dispatch at all. No. It is about the fact that a buyer's single word for a problem can be hiding several problems with different owners and different fixes and different prices. And there is a test in here for that. There is. When somebody names a problem, ask what happens if it is fixed. And see whether the answers agree. And here they did not, and one pressed question was enough to show it.
Which is a cheap test. Very cheap. It cost one follow-up question. And it changed what the entire proposal should be. So, where that leaves it. A pilot that lands with Marisol and never reaches the supervisor buys a champion and an opponent at the same price. The vendors do not answer, they do not commit, they do not arrive. Three failures, one word.