I have seen more than one tracking proposal built the wrong way around, and it happens often enough that I think it is worth describing plainly instead of pretending it is rare. The wrong way is starting with hardware.
I have seen more than one tracking proposal built the wrong way around, and it happens often enough that I think it is worth describing plainly instead of pretending it is rare. The wrong way is starting with hardware. Someone has a rough idea of how many readers, tags, and gateways a facility probably needs, a number gets attached to each one, and a quote goes out before anyone has actually walked the floor and written down the real sequence of steps a part or an asset goes through. It reads like a proposal. It is really a guess with a price on it.
I understand why this happens. A prospect wants a number quickly, and pricing hardware off a rough headcount of doorways or square footage feels like progress. But I have watched this shortcut cost more time in the long run than it saves, because the moment someone finally does the real walkthrough, the quote usually has to change, and now you are re-doing work in front of a customer who has already seen a number that turned out to be wrong.
The value of an actual process walkthrough is that it exposes the specific, unglamorous details that decide whether a tracking system works, and none of those details show up if you are only counting doors. It shows you where a part or a container physically cannot be tagged, because it is sealed inside something during a step, or because the material at that stage blocks radio entirely. It shows you which of the stations people call by name in conversation do not match the actual sequence of what happens on the floor, because informal shorthand and the real process are not always the same thing, and a proposal built on the informal names ends up describing a process that does not quite exist. It shows you where the highest-value read point actually is, which is very often the exact moment something changes state, comes off a tool, gets released from a fixture, moves from work-in-progress to finished, rather than wherever is most convenient to mount a reader.
I have also seen a walkthrough catch something even more basic: that the questions being asked had never actually been asked internally either. A team can operate for years managing a process by memory and habit without anyone having written down, end to end, exactly what happens to a thing from the moment it arrives to the moment it ships. Being asked to map it out loud, for the first time, in service of a tracking proposal, sometimes surfaces gaps the team did not know they had. That is not a wasted meeting. That is the actual value of doing discovery properly.
The best proposals I have been part of building do not try to price the entire system in one shot before any of this discovery has happened. They price a first phase, usually the highest-value, most well understood piece of the process, and treat the rest as pending a site survey or a short discovery engagement, priced separately and specifically. That is not indecision. It is an honest reflection of the fact that a facility’s real process, its real materials, and its real read points cannot be fully known from a floor plan and a phone call. A customer who is asked to commit to a fully-priced, guessed-at system up front is being asked to trust a number nobody has actually verified yet.
I would rather tell a prospect plainly that the full picture needs a walkthrough before I can stand behind a number, than hand them a confident-looking quote built on assumptions that are likely to be wrong in at least one important way. The former sometimes feels slower. It is also the version that does not need to be apologized for later.