Stan Callewaert

Stan Callewaert's public voice centers almost entirely on one problem: the enormous gap between how fast people can speak and how slowly they can type into clinical software, and what closes that gap for healthcare workers. His clearest illustration of this comes from following home nurses on shift, where he clocked their typing at "about 30 words per minute" against speech at "up to 150 words per minute" . That single measurement functions as the core justification for Squire's existence in his telling, not an abstract efficiency argument but something he witnessed directly in the field.

A consistent theme across both sources is Callewaert's insistence on going slow before going wide. On the SuperHero Conversations podcast, he described keeping Squire's product deliberately invite-only, meeting each GP one-on-one and returning every three weeks to iterate on feedback before pushing for scale ². This is not framed as caution for its own sake but as a mechanism for getting the product right in a domain, medical documentation, where accuracy and trust matter more than growth optics. The same discipline shows up in how he talks about hardware: the microphone matters early because it affects iteration quality, but Squire has no intention of building its own mics long-term, since he expects hardware to fade in importance as Squire becomes "a pure software product" ². That distinction between what needs craftsmanship now versus what will become commoditized later is a recurring piece of his strategic thinking.

Market framing is the other pillar of his stated position. He describes Squire's position as being in "a blue ocean, certainly in Europe," explicitly contrasting this with the more crowded American landscape for similar AI medical-transcription tools ². But he pairs this optimism with urgency rather than complacency, adding that the European market "is going to become very competitive, so speed will be very important to us" ². This is a notable tension in his thinking: he wants deliberate, one-by-one product iteration with GPs, yet he frames the overall race in terms of speed. The resolution, as far as the sources show, is that speed applies to expansion and market capture, while care applies to the product loop itself.

By 2026, his language shifts from methodology to impact, evidenced by the Wit-Gele Kruis integration announcement. Here he emphasizes the practical, almost mundane mechanics of the win: home nurses can now "simply talk to their tablet to fill in patient information directly in the software they were already using," bypassing "dropdown menus, date pickers and typing out text fields" . The phrasing is deliberately unglamorous, focused on friction removed rather than technology celebrated, which matches his product philosophy of integrating into existing workflows rather than replacing them.

The forward-looking note he strikes is expansive but grounded in the same operational terms he uses throughout: "This is only the beginning" and looking forward to impact on "thousands of home nurses all over Europe" . Read alongside the earlier podcast comments about speed and competitive urgency ², this reads less like generic founder optimism and more like a continuation of a stated plan, prove the product tightly with a small group, then scale quickly once the loop is validated, because the market window in Europe will not stay open indefinitely ².

The concrete takeaway from Callewaert's public statements is a fairly disciplined founder playbook: identify a measurable, visceral inefficiency (speech versus typing speed) , validate it through direct observation in the field , build with a small invite-only group before scaling ², treat hardware as a temporary means rather than a product line ², and move with urgency once you believe you are early in an uncontested market ². His own words suggest someone who separates the pace of product development from the pace of market expansion, deliberately slow on the former, deliberately fast on the latter, and who anchors big claims about impact in specific, witnessed detail rather than abstraction.