How Northstar Notes Found Market Pull Before Building the Product
Brief ready
Regenerate only when room inputs or profiles change.
START HERE
Opening move
What were you doing right before Northstar Notes, and what problem kept popping up that you couldn’t ignore?
Let Evan tell the weird moment, then immediately pin it down to buyer language, next-step behavior, and the artifact he used.
HOST FRAME
A founder/operator teardown of how Northstar Notes proved real demand before building: the exact buyer language that signaled budget, what the first prototype proved in the first 60 seconds, how early interest became...
A founder/operator teardown of how Northstar Notes proved real demand before building: the exact buyer language that signaled budget, what the first prototype proved in the first 60 seconds, how early interest became paid pilots, and the scripts, artifacts, and thresholds Evan would reuse.
Teams are under pressure to ship fast, but product-first building often misses real demand.
Secondary layer
Full Prep Brief
Room snapshot, context, supporting notes
Secondary layer
Full Prep Brief
A founder/operator teardown of how Northstar Notes proved real demand before building: the exact buyer language that signaled budget, what the first prototype proved in the first 60 seconds, how early interest became paid pilots, and the scripts, artifacts, and thresholds Evan would reuse.
Keep it humane but not inspirational. No product tour. Keep pulling the guest back to scripts, artifacts, thresholds, buyer behavior (forwarding, approvals), and what made people pay.
WHAT SHAPED THIS BRIEF
Room goal
Prove pull before building, then convert to paid pilots without turning into generic inspiration.
Host constraint
Not a product tour; keep returning to scripts, artifacts, thresholds, buyer behavior, and money.
Guest strength
Technical founder who learned sales through uncomfortable discovery; can share failed pilots and pricing anxiety.
High-signal moment
Buyers began forwarding internally—use as a proxy for internal championing and budget routing.
Must-cover beats
Killed idea, exact budget-language, first 60 seconds of prototype, pilot structure, 14-day playbook close.
Safety boundary
No named customers, no private pipeline metrics, no proprietary scoring logic; anonymized workflows only.
WHAT TO KNOW BEFORE YOU ASK
Briefing cues, not source review
The episode is about market pull mechanics: how to detect budgeted pain, prove value with a minimal prototype (often manual), and convert intent into paid pilots with clear acceptance criteria.
- Ask for anonymized workflows, not customer names.
- Avoid proprietary scoring logic and private pipeline metrics; ask for decision rules and artifacts instead.
- Push for exact phrasing buyers used that implied budget and urgency.
IF TIME IS TIGHT
Protect the strongest thread first
Must cover
- The weird early moment + the exact buyer phrase that implied budget
- The first 60 seconds of the prototype: what they saw and what they did next
- What was manual vs automated in early demos
- How Evan converted interest into a paid pilot (scope, timebox, acceptance criteria, price framing)
- The killed idea and the concrete kill signal
Optional if it opens up
- Pricing anxiety story, framed as the decision rule he used to set the first pilot price
- Founder-led sales learning curve: one uncomfortable script he had to learn
- One failed pilot that taught a boundary (who not to sell to)
Cut if short
- Any growth/ARR color
- Deep technical architecture details
- Long segment on category landscape or competitors
Human Story Thread
Use this if you want a warmer opening.
Use one compact personal beat to make the tactics stick: Evan learning sales through discomfort. Keep it tied to the artifact or script he had to practice.
- The uncomfortable discovery call he almost didn’t do
- The moment he realized ‘being technical’ didn’t excuse avoiding the ask
- A small win: a buyer forwarded something internally and it changed his confidence
Opening question
What part of early sales felt most unnatural for you, and what did you do to get reps anyway?
Follow-ups
- What script did you write for yourself to get through it?
- What did you change after the first time it went badly?
Conversation Plan
Questions and flow for your conversation
Keep it tight: get one vivid moment, one exact buyer quote, one early artifact (email, DM, doc).
A strong answer includes
A verbatim-ish buyer phrase like we already spend for this, we need this before next quarter, legal/procurement needs it, can you pilot this.
Ask for example
What did you deliberately leave out at that stage because it didn’t affect buying?
Safe pivot
Let’s anchor this in a single artifact from that week—what did the buyer actually see?
Transition
Zoom into the first demo minute and what the buyer did next.
If short on time
Anything about the broader vision or category.
Follow-up ladder
- What’s the earliest artifact you had that wasn’t a product—doc, email, loom, anything?
- What did you deliberately leave out at that stage because it didn’t affect buying?
- What’s the one feature people assume mattered that actually didn’t move buying at all?
Transition block - no questions
Make it concrete: screens, steps, time-to-value, and what was manual behind the curtain.
A strong answer includes
A clear sequence: input, output, one surprising insight, and an immediate buyer action (forward, meeting, asks for terms).
Ask for example
What was the exact phrasing that signaled budget or urgency?
Safe pivot
Can you replay the conversation up to the one sentence that changed your confidence?
Transition
Bridge to what failed and what he killed, using the same evidence lens.
If short on time
Engineering details that don’t change the buyer behavior.
Follow-up ladder
- What did the buyer say next that made you book the next meeting?
- What was the exact phrasing that signaled budget or urgency?
- If someone said that today, what’s your rule for believing them versus labeling it polite interest?
Transition block - no questions
Keep it honest but useful: what repeated, what changed, what rule he adopted.
A strong answer includes
A repeatable pattern like no internal owner, no workflow, no budget line, or outcomes too squishy to measure.
Ask for example
What parts were manual behind the scenes, and how long did it take you to deliver one result?
Safe pivot
If we paused the video at second 30, what’s on the screen and why does it matter?
Transition
Turn to the conversion mechanics: how paid pilots were framed and closed.
If short on time
Long storytelling without the decision rule.
Follow-up ladder
- What did they click or ask for immediately after that?
- What parts were manual behind the scenes, and how long did it take you to deliver one result?
- What output made people forward it internally, and who did it get forwarded to?
Transition block - no questions
Pull out the pilot one-pager: scope, timeline, acceptance criteria, price framing, and the close motion.
A strong answer includes
Concrete terms: 2–4 week timebox, success metrics, who attends, what deliverable, and what happens if it works.
Ask for example
What were the acceptance criteria, and who had to agree to them?
Safe pivot
Let’s reduce it to three bullets from the pilot one-pager: scope, timeline, success criteria.
Transition
Land the plane with a 14-day playbook founders can run.
If short on time
Any negotiation war stories that don’t teach a move.
Follow-up ladder
- What did the pilot include and exclude?
- What were the acceptance criteria, and who had to agree to them?
- What was the most common objection, and what exact line moved it forward without discounting into oblivion?
Transition block - no questions
Force specificity: week 1, week 2, artifacts, thresholds, and a stop rule.
A strong answer includes
A checklist: number of calls, the exact ask, the prototype promise, pilot doc bullets, and a kill threshold.
Ask for example
What was the pattern you saw across multiple conversations that you couldn’t argue with?
Safe pivot
Name the repeated sentence you kept hearing that you wish you’d believed sooner.
Transition
One sentence: what to do tomorrow morning.
If short on time
Philosophy; keep it executable.
Follow-up ladder
- What did you try that you’d now skip entirely?
- What was the pattern you saw across multiple conversations that you couldn’t argue with?
- If a listener is on that same path right now, what’s the threshold they should use to stop in the next two weeks?
Transition block - no questions
ADDITIONAL QUESTIONS
“As we go, I want to stay on what prospects said and did, what you showed in the first prototype, and what got you to paid pilots—not a product tour. Sound good?”
“Tell me the first weird moment where you realized this problem was real, not hypothetical.”
“Walk me through the first 60 seconds of the earliest prototype—what did the user see, and what was the first reaction?”
“When you decided to charge for a pilot, what did you say on the call to ask for money?”
“What was the last idea you killed right before Northstar Notes, and what was the signal that made it a clear no?”
“If you had to restart from zero, what would your first 14 days look like—week one and week two?”
Supporting Context
Participants
Maya Rahman
Host
Role in this conversation: keep the room tactical, paced, and useful for SaaS founders, startup operators, product marketers, and founder-led sales teams..
Evan Park
Guest
Evan can talk about failed pilots, fast prototypes, pricing anxiety, and the moment buyers started forwarding the product internally. Perspective: Technical founder who learned sales by doing uncomfortable customer discovery.
Rina Cole
Producer
Rina wants a strong first eight minutes and a clean close that gives founders a week-by-week next step. Perspective: Protects pacing and makes sure the episode does not become a product demo.
Conversation Threads
- Importance of exact buyer phrasing as the strongest pull signal
- Value of fast prototypes that reveal one core metric in the first minute
- Paid pilots as the pivotal step between interest and revenue
- Manual early work is acceptable if it exposes repeatable product requirements
- A short, prescriptive 14-day playbook is useful for listeners
Conversation Arc
Pin the episode frame so it doesn’t drift into a demo
Set expectations: evidence of pull, not feature walkthroughs.
The weird early moment + the budget-phrase
Get a human hook, then convert it into a falsifiable market signal.
Prototype in 60 seconds: the time-to-value walkthrough
Extract the core demo sequence and the immediate buyer behavior that proved pull.
From interest to money: the paid pilot ask
Turn vague demand into a repeatable closing motion with terms and thresholds.
Kill the last idea: the stop rule
Keep the story honest and teach a market-test boundary founders can use.
Watchouts
Customer identification
Named accounts or recognizable details can break trust and create defensiveness.
Safer: Keep it anonymized: describe the role, company size, and workflow without names or distinctive facts.
Proprietary scoring or model logic
Invites secrecy and vagueness, and derails into technical explanation.
Safer: Ask for decision rules and outputs buyers cared about, not how the model worked.
Pipeline metrics and private contract terms
Can pressure the guest into evasive answers or sensitive disclosures.
Safer: Ask for ranges and structures: timebox, acceptance criteria, who signs, and what changed hands conceptually.
Accidental product tour
Audience wants pull mechanics, not features.
Safer: Keep returning to buyer behavior: what they did next, what they paid for, and why internally.
Deeper Context Notes
Show deeper context notes
Key terms
- Paid pilot
- A time-boxed, paid trial with defined scope and success criteria.
- Prototype
- A fast proof of value, often partially manual, designed to elicit buyer behavior before full build.
- Buyer forwarding
- A prospect sends your demo or output to colleagues; a signal of internal buy-in and budget routing.
Angle coverage
Customer language & budget signals
Interest is cheap; budgeted pain shows up in specific wording and next steps.
Ask toward: Have Evan repeat the exact line that made him think there’s money behind this.
Prototype in 60 seconds
The first minute reveals the true value prop and shortest path to proof.
Ask toward: Walk through what the user saw, clicked, and reacted to in minute one.
Manual scaffolding vs automation
Founders need to know what was ‘Wizard of Oz’ and what was real.
Ask toward: Ask what was manually assembled, how long it took, and what he refused to automate yet.
Read-only demo
Refine controls are available in your own rooms
Create a room to edit, regenerate, and export
Read-only demo