An internal tool can't sell itself to strangers

Picture an operations team that builds a warehouse management tool integrated with its own processes. It runs well for three years.

Then someone at the company says: “Why don't we sell this to other people?”

That question sounds reasonable. But the next step is usually to build a website, write a few lines describing the features, and wait. Nothing happens.

Not because the product is weak. But because the language of an internal tool and the language of a commercial product are two entirely different things.

Why an internal tool loses its voice outside the company

Internal tools are built in an environment that already has context. Users know what the company does, know the problem being solved, and know why the tool exists.

External customers have none of that. They meet the product for the first time, with no one to introduce it and no shared history.

What they need to see in the first few seconds is: what problem this solves, for whom, and why it can be trusted. Internal tools usually can't answer these three questions, because they never had to before.

Positioning is something you do to the buyer's mind, not something you do to the product.

Al Ries & Jack Trout, Positioning: The Battle for Your Mind

The problem is not the features. It is that the product has no place yet in the minds of new buyers.

The three most common positioning gaps

After working with many businesses taking internal tools to market, Sinh Vũ has seen three gaps appear in almost every case.

The first gap: the audience is too broad or too vague. When you build for your own team, you know exactly who uses it.

Once outside, the answer is often "small and medium businesses" or "companies that need better management." That's not an audience, it's a generic description.

The second gap: the problem is described through features, not through the buyer's perspective. "Cross-platform integration, automated reports, friendly interface" is a technical description.

Buyers don't think in features. They think in terms of the problem that keeps them up at night.

The third gap: no trust signals (that is, the proof customers need before they pay). For people inside the company, the tool's credibility comes from seeing it run every day.

Outsiders don't have that experience, so they need something else to trust.

Repositioning starts with the new buyer

The first step isn't rewriting the website. The first step is to define clearly: who will pay for this product, and which problem is keeping them awake at night.

The specific questions Sinh Vũ usually starts with:

• Which industry and which roles do your internal users come from?
• What was the biggest problem they faced before having this tool?
• Who decides to buy, who actually uses the product, and are those two roles the same?
• Are there other products they currently use to solve a similar problem?

The answers to these four questions will show where the product should sit in the buyer's mind, and what it needs to say so they stop instead of clicking away.

From describing features to positioning language

Once you know who the buyer is and what problem they face, the next step is to translate the product into that person's language.

This is the part many product teams skip, thinking "customers will understand once they see the features." In reality, customers don't have the time to translate for themselves.

Positioning language includes:

• Core positioning statement: this product helps [who] do [what] that previously [specific problem or difficulty].
• Product category name: what kind of product you call this, so customers know what to compare it with.
• Short proof: two to three sentences from real users, about specific results rather than general feelings.
• The one point of difference: something the product does that other options don't do, or clearly do worse.

A brand is not a logo. A brand is how users feel when they think of your product.

Marty Neumeier, The Brand Gap

Trust signals: what strangers need to see

With a SaaS product (software delivered online, paid monthly or yearly), customers have to pay before they truly know whether it works well for them.

The trust barrier is therefore much higher than for consumer goods.

Trust signals are not a nice logo or professional colors. They are specific things customers can verify:

• The names of real customers currently using it, along with their industry and size.
• A specific result figure, with a clear note on how it was measured.
• How long the product has been in operation and the current number of users.
• A refund policy or free trial, so customers can see you are confident in your product.

Consistent language across every touchpoint

Once your positioning is clear, the next challenge is keeping that language consistent everywhere customers come into contact with your product.

Website, partner introduction materials, customer care emails, in-app notifications, social media posts: all of them need to tell the same story, short or long, whatever the channel.

When every channel speaks in its own way, new customers can't form a clear picture of what the product is. They may try it, but it's hard for them to remember and hard to recommend to others.

This is why many internal products win a few customers through direct relationships after going external, but fail to grow: the positioning isn't clear enough to travel beyond your circle of acquaintances.