When the growth story gets ahead of the buyer story

Field Note · September 3, 2026 · 5 min read

A presenter showing a growth chart to investors while a product demo runs nearby

A company can describe where it is going to investors while explaining what it can deliver today to agency buyers. The two accounts still need to describe the same business.

A company starts with a focused product for one part of the justice system. The product works, customers use it, and the company begins to see a broader opportunity. It adds capabilities, hires for new markets, and talks with investors about what the business could become.

The investor presentation now describes a platform with room to expand across agencies. The website still describes the original point solution. Sales materials mention some newer capabilities, but the implementation team knows they are available only under particular conditions. None of these materials has necessarily made a false claim. Together, they leave a basic question unanswered: What can a customer buy and use now, and what is the company still building toward?

This is a possible consequence of growth for a public safety or justice system vendor. The company has changed faster than the explanation it gives to different audiences. A funding round may bring the gap into view, but a new product, acquisition, or move into a neighboring market can do the same.

The work is to describe the business as it exists today and its intended direction without making the agency buyer infer that every future capability is ready for deployment.

Growth changes the claims a company makes

An investor presentation has a legitimate reason to discuss market opportunity, revenue, expansion, and the path ahead. A buyer evaluating a system has a legitimate reason to ask what it does, what it depends on, and what adopting it would require. Those audiences need different evidence. The trouble begins when the claims beneath that evidence no longer line up.

Suppose a hypothetical vendor began by helping prosecutors receive digital evidence from law enforcement agencies. Its early product is used for that defined workflow. The company then develops ways to connect more participants and starts describing itself in an investor deck as a platform for the entire case lifecycle.

That future direction may be credible. It is still different from saying that every agency can use an integrated case lifecycle platform today. A buyer hearing the broader description would need to know which workflows are currently supported, which integrations are in production, what participation by other agencies is required, and which features remain on the roadmap.

Those are operational and governance questions, not objections to ambition. The National Institute of Justice’s technology adoption and implementation guide asks criminal justice decision makers to consider technical, operational, and governance factors together. A vendor’s growth story should leave room for an accurate explanation of those factors in the current product.

The problem may show up as a mismatch in nouns. One document says “evidence transfer.” Another says “justice platform.” A third promises “connected case management.” Those phrases may describe stages of a coherent strategy, or they may refer to materially different products. The company needs to explain the relationship. Otherwise, each reader supplies their own interpretation.

Separate present capability from planned expansion

A useful message architecture can hold both the current offer and the company’s direction. It should make the boundary between them easy to see.

For the hypothetical vendor, the central explanation might begin with the workflow it serves today: helping authorized participants move evidence through a defined exchange and maintain a record of that activity. The broader direction could then explain how the company intends to connect additional workflows or agencies. Any statement about that direction should identify what has been delivered, what is being piloted, and what remains planned.

The investor presentation can use that foundation to explain why the initial workflow offers a path into a larger market. The buyer materials can use it to show what is available, what has been demonstrated elsewhere, and what a specific agency would have to do to implement it. The audiences hear different aspects of the same strategy, with evidence appropriate to each claim.

The distinction matters inside the company, too. If marketing describes a capability as generally available while product calls it a pilot and implementation treats it as custom work, the issue cannot be solved with a better tagline. Those teams need an agreed account of the capability, its limits, and the conditions under which it can be delivered.

That account should include more than product status. A growth claim may depend on a repeatable implementation model, support capacity, an integration partner, a data-sharing arrangement, or a customer segment the company has not yet served. The stronger the expansion claim, the more useful it is to state what has been proven and what is still an assumption.

Trace one claim across the materials

Start with a consequential growth claim. If the investor deck describes a path from one agency workflow to a statewide network, examine what that path assumes about the product, customer participation, and the company’s ability to deliver it.

For that claim, ask:

  • Which part of that network exists in the product today?
  • What evidence supports the claim that the model can be repeated in other agencies or jurisdictions?
  • What integrations, agreements, staffing, or policy decisions would expansion require?
  • Do the website, demo, proposal, and implementation plan describe those conditions consistently?
  • Can the team distinguish a current capability, a committed development effort, and a longer-term goal?

The answers may reveal an honest sequencing problem. The investor deck could be describing a destination while the website is still anchored to the starting point. Or the website may have adopted the platform language before the product and delivery model can support it. Either way, the correction is more precise than making every document sound identical.

Start with what the company can stand behind. Define the current offer, the problem it solves, the customers and workflows it serves, and the evidence available for its results. Then describe the expansion path in terms the company can qualify and update as the business changes.

For a growing public safety technology company, that work protects more than the tone of its marketing. It gives investors a clearer account of the growth thesis, gives buyers a reliable account of the present offer, and gives internal teams a shared basis for what they promise. The story can move forward as the company does, provided the claims move at the speed of the evidence.

FIELD NOTES

Get new essays in your inbox.

Research-backed writing for public safety and justice system technology leaders.

Heidi Bonner, PhD leads Word Sleuth Agency, helping public safety and justice system technology companies realign their messaging with the business they have become.