Product-market fit, introvert sales, and hiring at Signwell

Executive overview

Most founders treat product-market fit as a single milestone to cross. It isn't. Every customer segment and use case has its own PMF curve — and for horizontal products, use cases cut across verticals in ways segment-based thinking misses entirely.

Moving upmarket means fewer data points, which forces deeper qualitative work with each customer. Good decisions compound over time through pattern exposure, self-awareness, and genuine openness to feedback.

Staying disciplined about what you won't do is as important as choosing what you will.

Product-market fit is a continuum, not a binary

• Signwell had strong PMF with individual users long before it had it with teams of 50–100.
• The API and web app are separate products with separate PMF curves — each use case within them has its own curve.
• For horizontal SaaS, verticals often matter less than use cases: HR, education, and nonprofits all share a "batch documents to many recipients" workflow regardless of industry.
• Use cases also shape onboarding, time-to-value, and how you reach and sell to customers.
• Audit your customer list by use case, not just revenue — identify best and worst performers and what they have in common.
• Signs of PMF: conversion improves, churn drops, growth feels like being pulled rather than grinding.

Deciding with less data as you move upmarket

• Higher-ticket customers mean lower volume — replace quantitative signals with qualitative depth.
• Talk to customers post-sale: what triggered the buying process, who was involved, what they worried about.
• Patterns emerge faster than expected when conversations go deep enough.
• Alongside market size, ask how well you can actually reach and sell to a segment — a large market you can't access is not a real opportunity.
• Signwell deprioritised real estate despite its size: no existing distribution advantage, no expertise in how that segment buys.

Improving decision-making as a skill

• Decision-making quality is learnable — it is not a fixed trait.
• Observe how strong founders reason through decisions, not just what they decide; read their blogs, listen to their frameworks.
• Know your own failure mode — impulsiveness, over-analysis, or confirmation bias — and counteract it deliberately.
• Seeking feedback only to ignore it does not help. True openness means updating when smart people consistently say the same thing.
• Target range for experienced founders: roughly 70–80% accuracy on major decisions; coin-flip rates are insufficient.
• Once a decision is made, commit fully — fighting it afterwards wastes energy and worsens execution.

Doing sales as an introvert

• Do it because the business requires it, with the explicit goal of eventually hiring someone who genuinely enjoys it.
• Reframe the activity: treat sales as a puzzle to solve, not a chore to endure.
• Once committed, stop second-guessing — go in with full energy; dread makes outcomes worse.
• Learn actively: find people doing it well, seek specific advice, hire a domain advisor if needed.
• "Good enough" is the target — you don't need to become exceptional at something that isn't your core skill.

Hiring: being pickier than average

• Most companies hire after reviewing three to four candidates; waiting for candidate 15 or beyond is a real differentiator.
• For new role types where you lack expertise (e.g. first sales hire), bring in an advisor with direct domain experience to help evaluate.
• Use the Who scorecard method: define what a great hire looks like before you start, then score every candidate against those criteria — don't let overall likeability override specific gaps.
• Keep a running bookmark list of impressive people you encounter (on social, at events), even when not actively hiring.
• Identify roughly three core skills for any role. Some are easy to evaluate upfront (portfolio, written exercise); others — like hitting deadlines — can only be assessed through a trial project.

Interviewing for what actually matters

• Resume pedigree (company names, tenure, seniority title) is among the least predictive signals — don't let it anchor the interview.
• Give candidates a skills exercise that mirrors the actual job: a coding problem, a support scenario, a document task in the real product.
• For communication: evaluate written application quality; include a feedback-and-revision step to observe how they respond to pushback.
• Ask "what would your former manager say you could improve?" — push past the polished first answer until you get a specific example.
• Hard questions don't require harsh delivery: "your churn is 12% — how are you thinking about that?" surfaces the same information without distortion.