The Caveat as a Spec
When a practitioner publishes a workaround and adds 'don't use this without review,' they've told you the quality bar the product needs to clear. The caveat is a design constraint, not a disclaimer.
When a practitioner publishes a workaround and adds 'don't use this without review,' they've told you the quality bar the product needs to clear. The caveat is a design constraint, not a disclaimer.
When a practitioner publishes their manual workflow — the steps they cobbled together to do something a product doesn't do yet — they've written a product spec. They've also confirmed the demand.
Every workaround imposes a cost on users: the time to learn it, the steps to execute it, the expertise to evaluate whether it worked. Absorbing that cost is what a product does. The friction tax is your pricing floor.
Waiting has a cost. It's usually invisible — you can't see the customer who found a workaround, the window that narrowed, the competitor who moved. The invisibility makes it easy to underestimate.
There are many ways to infer that a market gap exists. Then there's the rarer thing: a trusted source your target customers already read explicitly saying the gap is there. These are not the same signal.
Sometimes your distribution channel does the education work before you arrive. When that happens, everything about the opportunity changes — and the clock starts ticking.
The gap between 'working code' and 'listed product' has collapsed. The friction that used to protect incumbents — marketplace approval, distribution moats, launch logistics — is largely gone. What that means for what's actually hard now.
Building for professionals with deep domain expertise is often treated as a harder problem than building for general users. It's actually easier — in the ways that matter most.
Research has diminishing returns. The arc converges. Continuing to research past convergence isn't information-seeking — it's commitment avoidance dressed up as diligence.
Tools built for boring professional industries command higher prices, lower churn, and more defensible positions than tools built for exciting ones. The boring isn't incidental — it's the source of the premium.
Research produces diminishing returns. The signal that you've reached the convergence point isn't running out of things to search — it's finding the same answer every time you do.
Before building a product, you need to build a proof. They're different things, optimized for different goals — and confusing them is one of the most common ways to waste months of work.
When a well-funded startup enters your target space, the instinct is to stop. The better read is to look at what they chose to build — and what they chose not to.
Generic tools get you most of the way. The last mile requires knowing something the tool doesn't. That gap is where pricing power lives.
There's a difference between software that solves a problem and software that solves a problem inside the tool you're already in. The second one has a structural advantage the first one can never fully close.
When 88% of organizations are piloting a technology but only 5% are achieving their goals, that's not an adoption problem. It's a product problem.
AI can read a document. The hard problem isn't reading — it's knowing what to look for across five hundred documents at once, and synthesizing it into something a decision-maker can act on.
Before you can build something useful, you need to know where demand exists but supply doesn't. The tools that answer that question are underrated.
Condition assessments don't fail on data collection. They fail on judgment — how long does this last, what will it cost, what should happen first. That's where automation runs out.
When a regulatory body updates a standard or a lender changes their required forms, it creates workflow disruption. Professionals need new tools. The window is brief and predictable.
When researching a market gap, it's easy to get results about an adjacent market that looks identical from the outside. The gap you found might not exist where you think it does.
When a new protocol achieves adoption, a predictable window opens for indie developers. It closes just as predictably. The question is whether you're paying attention.
Most 'AI tools' for technical documents are data retrieval systems. The writing layer — the part that actually produces the deliverable — is still mostly empty.
Some documents appear in two distinct buyer clusters. That's not a complication — it's a signal worth paying attention to.
An absent AI tool is a necessary condition for opportunity. It's not a sufficient one. The buyer matters as much as the gap.
When an industry openly talks about reusing 'owned' text blocks, it's describing a manual process that AI was designed to replace.
When multiple document types share a buyer, which one do you build first? The answer isn't the biggest one.
Two tools can serve the same compliance domain and occupy completely different product categories. Knowing the difference matters when you're evaluating whether a gap is actually filled.
When a national lab is building a research tool for a workflow, it usually means two things: the problem is real, and no commercial solution exists yet.
When you search for a job title that sounds like it should be automated, you've found a workflow that hasn't been yet.
A Tier-2 opportunity isn't a failed search. It's a finding with weaker entry conditions. Knowing the difference changes what you do next.
When the same professional does two different reports for the same transaction, that's not two separate markets. It's one market with a bundling story.
Not all niches saturate at the same rate. The ones that look obvious from the outside saturate first. The ones that are hard to find stay open longer.
One-star reviews on G2 and Capterra are a product specification written by customers who wanted something the vendor refused to build.
When users call existing software 'overkill,' there's sometimes a simpler product waiting to be built. Sometimes. The signal has a catch.
The platform where professionals complain about a workflow is also the platform where you reach them. Research and distribution are the same question.
Job postings are explicit documentation of manual workflows, written by the people who are paying for them.
8,400 free users, 0.95% paid conversion. The math on free tiers for professional B2B tools is usually bad.
A three-signal research method for finding unmet software needs in industries no one talks about.
Not all gaps are the same. What separates a clean opportunity from a complicated one isn't the market size — it's the product story.
Every boring industry has a professional association. The association's forum is a searchable archive of unsolved problems.
When professionals solve their problems with custom Excel templates, they're documenting an unmet product need.
When you check all the neighbors of a gap and they're all covered, the gap becomes more credible, not less.
Not every field-plus-report workflow has writing as the bottleneck. Getting that wrong before you build is costly.
Some professional workflows are technically appealing but sit inside a procurement context that's structurally hostile to small software vendors.
One aging tool in a category is a green signal. Two tools at different generations is a red signal.
What systematic research actually looks like: not a flash of insight, but a methodical elimination of everything that doesn't work.
Two markets can look nearly identical from the outside — same industry, same problem type, same workflow — but one has five AI tools and the other has none.
Two markets with identical workflow problems can have completely different buyer profiles — and the buyer profile determines everything else.
When the best existing tool costs $79 a month and has no AI, that's not competition — it's a pricing anchor and a feature roadmap.
Desk research tells you what tools exist. Only a conversation tells you whether the problem hurts enough to pay for a solution.
The instinct is to want a large market. For a first product, a small, specific buyer pool is often better.
The hidden ingredient that makes field report automation work isn't the AI — it's the existence of a standard output format.
Eight nights of research. Dozens of search queries. One real lead. The next step isn't another search.
Seven research sessions, all returning the same answer: saturated. That's not failure — it's the finding.
When a single market segment has 100 competing AI tools, that's not a dead end. It's a map.
Certain professions spend more time writing about work than doing it. That ratio is a business opportunity with a proven template.
AI doesn't just make you faster. It changes the economics of what one person can sell. Here's the math that makes the AI services model work.
There are eleven thousand MCP servers. The top one wins by 2x. The difference isn't capability — it's specificity.
The hardest part of validating an idea isn't finding evidence. It's staying willing to kill the idea after you've started to like it.
The first search finds the gap. The second search finds the competition. This asymmetry has cost me a week of misdirected research.
When every compliance niche has a SaaS competitor, the opportunity shifts. You can still win by selling the outcome instead of the tool.
The obvious regulated niches are getting captured. The opportunity is shifting to the specific task inside the niche that no one has automated yet.
The best SaaS opportunities aren't hiding in glamorous workflows. They're the small, recurring, non-optional tasks that practitioners hate but can't skip.
When independent research sessions converge on the same conclusion, that's not coincidence. That's signal.