/ in-product micro-interviews, fired by real signals

In-product user research for people who stopped doing it.

No recruiting. No scheduled calls. No panel. When someone struggles in your product, Margin asks one question — then hands you a direction in their own words, on the board where you already work.

/ See a real synthesis / Read how it works

SHIPPED: Built in 30 days for World Product Day 2026
STACK: Next.js · Claude Code · Cursor · PostHog · Sentry · Novus.ai
PRICING: Free to start · $19/mo founding for the first 100

/ 01 — the problem

They said it was great. Then they quietly stopped opening it.

Your dashboard shows you the cliff — forty-seven percent gone by step three — every day, in seven views, with progressively prettier charts. What it never shows you is the reason. The reason left without a word.

You meant to do the interviews. You wrote it on a Notion page in March. After the launch there’s the next launch. And people are too polite to tell you on a survey — by the time churn tells you, they’re already gone.

Margin is the tiny tool we built because we got tired of pretending we knew what our users felt.

Every cliff in your dashboard is a person who left without saying why. We never built anything to ask.

/ 02 — the product, working

Asked in the moment. Synthesized in your users’ own words.

A real user got stuck on Ledger's blank decision form. Margin asked one question, four people answered, and by morning it had a theme and a direction. This is that exact loop — the same data you can open on the demo.

one question, in the product

ledger · /new

margin · dwell_anomaly

Stuck on the blank page? What were you about to write down?

esc to dismiss⌘ + enter

the direction it becomes

margin · dwell_anomaly · /new

acting on it

I couldn't tell what counts as a decision worth logging.

we asked

“Stuck on the blank page? What were you about to write down?”

“I opened the form and just stared at it. Is a decision like 'which database' or like 'what to have for lunch'? I didn't want to get it wrong.”

direction

Try pre-filling the blank form with one real example and a quiet 'too small? log it anyway' line.

4 replies · 4 people · last 7 days

→ linear LED-142 · 2d ago

/ See the other three on the live demo →

/ 03 — the loop

Four steps. Then it runs without you.

01 / catch

Something breaks for a user, quietly.

A rage click. A dropped checkout. A Sentry error. A funnel hiccup in PostHog. Margin watches the moments analytics gives up on — its own, and whatever signal source you already pay for.

02 / ask

Margin asks them — politely, in your product.

One sentence. Twenty seconds. Their words, not a form. They reply or they don’t. Either way, you didn’t get in their way.

03 / synthesize

Replies become a direction.

Margin reads every reply, finds the three people saying the same thing, and drafts one theme, one verbatim line, and one suggested next step — in your users’ voice, not ours. You decide if it’s right.

04 / land

The direction shows up where your work already lives.

A draft Linear issue waiting Wednesday morning, or a weekly email — wherever you already work. You accept, edit, or archive, then you ship. The loop runs again, on the next thing you didn’t know.

/ from the build

We built this on ourselves first.

Margin has been running on Ledger — a tiny decision logger we shipped — for the length of this build. The demo is sample data, but the loop is the real one: a signal fires, the question goes out, the replies cluster, a direction lands in our Linear on Wednesday morning.

We read the first one and thought we could have guessed that, and we didn’t.That’s the whole product.

/ See what it surfaced →/ Why we built this →

/ 04 — pricing

Priced to sit next to Cursor and Linear in your stack.

Metered on what Margin hands you — replies collected, directions synthesized — never on seats. Start free on your own product; pay when it earns its place.