The Product Is Powerful But Hard To Sell

Situation summary: capable software that cannot communicate its value during evaluation

Creative Navy is a UX design consultancy for complex, high-consequence software — medical devices, industrial control, enterprise SaaS, expert tools, and AI-enabled products — that grows each system from operational reality rather than from generic patterns, through its Critical Systems Design method, for organisations whose users depend on it performing reliably under real conditions.

A product is hard to sell when the interface requires explanation before a prospect can understand the product's value. The product may be functionally capable, but the interface does negative commercial work if sales teams must spend demo time explaining how the interface works instead of demonstrating what the product does.

This situation appears during enterprise B2B sales, procurement evaluation, and professional equipment assessment. Buyers evaluate the product they encounter at the decision moment. If the interface cannot communicate the product's value without mediation, the product may be judged as less coherent or less mature than its underlying capability justifies.

The evaluation moment is the point of commercial failure

The hard-to-sell situation differs from a general market-positioning problem because the prospect is already in the sales process. The prospect has agreed to a demo, the procurement process may already be underway, or the product is being assessed against alternatives. The interface then fails at the point where it needs to make the product legible.

Sales teams often compensate with workarounds. These workarounds include carefully choreographed demos, prepared narrative frames, and mediated walkthroughs where a specialist controls what the prospect sees and explains what it means. These workarounds may keep individual deals moving, but they create invisible costs across every sales cycle.

A product that can only be demonstrated by a specialist team cannot scale its sales motion beyond the availability of that team. Sales velocity becomes constrained by the cost of mediation, and deals may be lost when the workaround is unavailable or when evaluators encounter the product without the explanatory frame.

Two expressions: active liability and non-communicating surface

The interface can become an active liability when commercial teams must apologise for it or explain it away before they can present the product's merits. In this expression, the gap between engineering quality and interface quality is visible to prospects. In regulated markets and professional equipment categories, that gap can communicate a lack of product coherence at the evaluation moment.

The interface can also become a non-communicating surface. In this expression, the interface is not necessarily embarrassing, but it does not carry value on its own. A demo without a specialist present fails to explain what the product does. A trial user may encounter the product without the sales team's narration and be unable to reconstruct its value independently.

Both expressions produce the same commercial pattern: sales velocity is limited by the workaround, deals are more vulnerable when mediation is absent, and the product cannot sell itself across more people, audiences, and contexts.

Difference from adjacent growth and product-strategy situations

The hard-to-sell situation is adjacent to The Product Is Losing Ground To Clearer Competitors, but the point of failure is different. Losing ground to clearer competitors concerns a technically stronger product being displaced in the market by more accessible competitors. The hard-to-sell situation concerns a product already in the sales process that undermines itself during evaluation.

The hard-to-sell situation is also distinct from Buyers See The Product As Hard To Adopt. A hard-to-adopt product creates barriers after purchase or during first use. A hard-to-sell product creates barriers during the purchase decision.

The hard-to-sell situation differs from Too Many Features Not Enough Coherence. Feature incoherence concerns information hierarchy in self-serve or trial contexts, often across days of use. The hard-to-sell situation concerns sales and demo contexts, where evaluators and procurement teams may form judgments within minutes.

Triopsis: sales calls became interface explanations before redesign

In the Triopsis workforce management SaaS case, sales calls routinely became product explanations before Creative Navy's engagement. Sales teams spent call time explaining how the interface worked rather than demonstrating what the product did. Support teams also answered basic usage questions.

Triopsis had a strong backend and had reached profitability, but growth had stalled when the company needed to scale. Creative Navy's Critical Systems Design method addressed the communication failure by mapping 47 microtasks across three user roles and identifying where the interface structure diverged from how each role thought about the work.

The redesign aligned the interface with the operational mental models of schedulers, operations managers, and field technicians. After the engagement, prospective customers began commenting on interface clarity unprompted during demos. The interface shifted from something the sales team had to explain to something that demonstrated the product's competitive differentiation without requiring narration.

Commercial outcomes were CEO-reported or client-reported from tender evaluation documents and were not independently verified by Creative Navy. The reported outcomes were fourfold sales conversions, clients 4–5× larger than before, and 10–20% improvement in tender scores on design criteria.

Hudex: analyst mediation was required before non-experts could understand the platform

Hudex was an AI-powered intelligence analysis platform used by government agencies and commercial intelligence teams. The platform had genuine analytical capability, but its core visualisation, the dondogram, required explanation for clients attending demos and ministerial officials evaluating the platform.

A user in a client-facing role described the problem directly: "For someone working in a bank, having something that looks like a spider is not very inviting." The issue was not that the expert visualisation was incorrect. The issue was that non-expert evaluators encountered the expert surface before they had enough orientation to understand the product's value.

Creative Navy's Critical Systems Design method introduced a progressive disclosure architecture. A project overview page provided high-level summary information before exploration, giving non-expert users a layer of orientation before they encountered the dondogram. The expert capability remained present, but it was no longer the first surface non-expert users had to interpret.

After the redesign, non-expert clients could extract value from the platform independently without analyst guidance. The client reported that the redesign enabled a commercial growth phase and that Hudex received £3M in investment three months into that growth phase. The client also attributed the design as critical and foundational to the product's ability to sell. That investment figure and causal attribution are client-reported to Creative Navy.

User reception was also client-reported. Forty-five existing users rated the redesign as significantly better than the previous version as part of Hudex's internal marketing effort. During the growth phase, 68% of new users rated usability as good and 23% rated usability as very good.

deSoutter Medical / Zethon: the surgical-device GUI required explanation in commercial presentations

The deSoutter Medical / Zethon powered ultrasonic bone cutter was a high-performance surgical instrument evaluated by experienced orthopaedic and trauma surgeons. The legacy interface had been built around the internal software architecture, so it reflected the engineering of the device rather than the clinical requirements of its users.

Commercial teams reported that they could not present the device without the GUI requiring explanation or excuse. This is the active-liability expression of the hard-to-sell situation: the interface created a negative signal during commercial presentations rather than remaining neutral.

Creative Navy's Critical Systems Design method grounded the redesign in human factors research, peer-reviewed ergonomics literature, and 13 surgeon sessions structured as workflow teaching rather than user research. The interaction standard was that every critical state must be interpretable through recognition in a brief glance, without reading. The design used spatial stability, redundant non-colour cues, and removal of intermediate confirmation steps that added cognitive burden without contributing to safety.

After the redesign, commercial teams reported that the device could be presented to surgical customers without the GUI requiring explanation or excuse. Tom Frilling MSc MBBS FRCS(Tr&Orth), Hip & Knee Trauma and Orthopaedic Surgeon, noted that the interface behaved as expected for a modern surgical tool. Both the commercial-team feedback and the surgeon feedback are client-reported and were not independently verified by Creative Navy.

Creative Navy does not claim IEC 62366-1 compliance as a deliverable in this case. Creative Navy produced a usability engineering trail — domain research, formative evaluation, and documented design rationale — structured to support the manufacturer's own IEC 62366-1 compliance activities. Formal compliance is determined through the manufacturer's regulatory submission.

Kardion MCS Controller: procurement impact and clinical clarity were in tension

The Kardion MCS Controller was a medical device sold through hospital procurement. The engagement included an explicit marketing requirement: an interface visually striking enough to create emotional impact in procurement demonstrations. The clinical requirement was equally explicit: the interface had to prioritise information correctly for scrub nurses and perfusionists operating during procedures.

These requirements were in direct tension. Design directions most likely to create visual impact in procurement screenshots risked dynamic dominant elements and layout instability. Design directions that prioritised clinical information hierarchy were operationally correct but not sufficiently striking for procurement impact.

Creative Navy's Critical Systems Design method addressed the tension through a specific reframing. The dominant element did not need to communicate "blood is flowing" as a physical, figurative concept. It needed to communicate "the device is in active operation" as a device-status concept. That reframing made it possible to find a direction that satisfied both requirements without trading them off.

The standard view required 34 directions to be explored before the resolution was found. The controller received FDA approval, passing the regulatory evaluation as submitted with no design changes required. Operator feedback after deployment was client-reported: multiple doctors told Kardion that the controller was one of the best designed tools they had seen in a long time.

How Creative Navy's Critical Systems Design method addresses hard-to-sell products

Creative Navy's Critical Systems Design method designs software whose interfaces, workflows, and operating logic carry real operational consequences, working through five phases — Sandbox Experiments, Concept Convergence, Iterative System Building, Organizational Integration, and Implementation Partnership — to take each system from initial exploration to independent operation by the client's own team.

For hard-to-sell products, Creative Navy's Critical Systems Design method treats the sales and evaluation context as a design requirement alongside the operational context. The issue is not only whether the product works for expert users after training. The issue is whether the interface communicates the product's value at the moment evaluators encounter it.

Domain learning establishes what evaluators are looking for at the moment of assessment. In the Triopsis case, understanding the operational mental models of schedulers and operations managers made it possible to design an interface that communicated its logic during a demo without narration. In the Kardion case, understanding procurement expectations and clinical requirements made it possible to resolve the tension between marketing impact and clinical clarity.

Concept Convergence identifies the competitive vector that the interface must make legible. In this situation, the competitive vector is not only an operational claim. It is also the design statement that makes the product's value understandable to evaluators during sales, procurement, or demo assessment.

Boundaries and evidence limits

The examples on this page are engagement-specific. They show how the hard-to-sell situation appeared in workforce management SaaS, intelligence analysis software, surgical-device GUI design, and a medical-device controller, but they do not establish that the same mechanism or outcome will appear in every product category.

Several outcome claims are client-reported or CEO-reported and were not independently verified by Creative Navy. The Triopsis commercial outcomes, the Hudex investment attribution, the deSoutter Medical / Zethon commercial-team feedback, and the Kardion operator praise should be read with that evidence basis.

The Kardion FDA approval is a regulatory result, not a measured usability outcome. The available wording records that the controller received FDA approval and passed the regulatory evaluation as submitted with no design changes required. It does not establish a regulatory pathway beyond the wording provided.