Skip to content

About

We built the wrong thing first. Then we built this.

Small teams have a superpower: everyone knows everything. The customer calls, the competitor moves, the half-formed idea from yesterday's standup. Decisions are fast because the full picture is in the room. Then you grow, and that superpower disappears.

We know, because we lived it. We started the way most founders do: we built a product and hit the wall. Adoption was slow, the fit was not there, we had to pivot.

To test the next ideas faster than we could build them, Steve built a machine. We called it Not Worth Building. It read the internet for what customers were actually saying about an idea, found the competitors, checked the positioning, did everything you do before you commit engineers. Most of our ideas did not survive it.

After enough conversations with other founders, we noticed the obvious: the machine was the better product. Not Worth Building became Quack Stack.

Working with teams who make product decisions every day, not just once at the start, turned it into what it is now: a disciplined way to decide what to build, with the evidence attached and the why kept. We use it every day to build it.

Case study

Twelve people. No product manager. One record of why.

One of our design partners builds an AI agent for small trade businesses. When the team grew from six to twelve, the founders noticed the thing every growing team notices: "we're already starting to lose some efficiency," and "we like to introduce new shiny things which are not necessarily good for our clients." Nobody owned product. One co-founder held the vision; the designer did the research and the messaging.

Quack Stack now reads their call transcripts and support signals every night. The co-founder checks the positioning and the claims the team has committed to. The designer works the board: what the evidence says is worth building, with the quotes attached.

The why is no longer in one head.

customer conversations
1,247
bets
122
themes
13

As of 29 September 2026

Quack has read 1,247 of the team's customer conversations: 1,192 phone calls, 40 WhatsApp chats and 15 interviews. It turned what it read into 122 bets worth weighing. 28 were set aside with the reason written down; the rest sit in 13 themes the team works through, each one traced back to who said it. Not a bigger pile of evidence: a shorter list of decisions.

The team

Patricia Klimek, represented by the Quack Stack duck with long blonde hair

Patricia Klimek

CEO

Former BCG and private equity. Deep strategy and go-to-market expertise across the UK and DACH regions. Runs AI adoption workshops with teams who are figuring out what this all means for how they work.

Steven Henty, represented by the Quack Stack duck with glasses

Steven Henty

CPTO

Product and engineering leader based in Spain. Over a decade leading distributed teams globally for US clients. Spent 20 years watching the handoff between "what to build" and "building it" break in new ways. Built Quack Stack to fix it for the AI era.

Quack, the Quack Stack duck, facing front

Quack

Reads everything. Shows the evidence.

Reads everything your customers said while you were asleep, and has opinions about it. Calm, a little professorial, a know-it-all in the kindest way. Obsessed with evidence: Quack will not tell you what to build, but will tell you, quotes attached, when what you decided stopped being true. You decide. Quack keeps the receipts.

Want to see it on your roadmap?

Book a call