You emailed me last week asking whether you should build the expense-report idea now or wait on "the research thing" to tell you it's worth it. Fair question, and the honest answer is: it depends on what you already know versus what you're guessing. So let me walk you through how the guessing gets replaced with evidence, because I think it changes what you build next, not just when.
You told me the idea came from your own life — you're manually re-doing FX conversion every time you file a mixed-currency team trip, exporting a spreadsheet, fixing the numbers by hand, re-importing. That's a fine starting point. Most tools I actually use started as someone's personal annoyance. But it's one data point wearing a business plan's clothes, and you don't actually know yet whether it's your annoyance or a market's annoyance. That's the gap Discovery closes, and it's worth understanding how before you decide whether to run it.
What five agents would find, in your specific case
Here's what would happen if you pointed the Discovery team's five research agents at your problem instead of building blind. One agent tracks rising search trends — queries growing month over month with thin results on page one. For your case, it would likely flag rising volume on exactly the mixed-currency-reimbursement query, with nothing ranking for it. One agent reads forums and social platforms for the recurring "why doesn't X just do Y" complaint pattern — and this is the one that would probably surprise you, because it's not just you. In a run like this, that agent typically surfaces a dozen-plus threads of people describing your exact workaround: export, manually fix the rate, re-import. One agent works Q&A sites for high-engagement unanswered questions — same problem, asked four different ways across a finance subreddit and a SaaS review site, no accepted answer either time, just other frustrated people trading your spreadsheet trick. One profiles competitor gaps by reading changelogs and support docs for the features people ask for and never get. And one is a generalist that goes wherever your specific niche actually lives.
Any one of those signals alone wouldn't tell you much. A single spiky search term could be a fad. A single angry thread could be one loud user. What makes it real is three independent sources — trend data, forum complaints, unanswered Q&A — landing on the same problem without reading each other. That convergence is the actual product here. Out of a typical overnight run pulling a few hundred raw leads across all five agents, maybe eight to fifteen survive that filter into something worth writing up. Yours, from what you've described, sounds like it would.
What you'd get isn't a green light — it's a brief
If it converges, what comes out is an Opportunity Brief, and the format is deliberately narrow because a free-form brief turns into marketing copy for an idea nobody's tested yet. Yours would need to contain:
- The problem, in the words the people who have it actually use — not sanitized. If the real quote is "I hate that I have to do this in Excel like it's 2004," that's what lands in the brief, and it's also your landing-page copy.
- The audience, specific enough to target. Not "small business owners" — something like "ops managers at 10-40 person companies running distributed teams across at least two currencies, active in r/smallbusiness and three named Slack communities."
- The evidence — actual links, quotes, numbers. No evidence, no brief. This is the rule I'd defend hardest to you: an agent that can't cite where a claim came from doesn't get to make the claim. A shorter brief with three solid links beats a persuasive one built on vibes.
- An MVP scope small enough to ship this week. If your idea's honest scope is a six-month build, it gets flagged as a bigger bet, not folded quietly into a brief that pretends otherwise.
- A confidence rating, written and justified, not just a number. Something like "medium-high — three independent signal sources, but audience size looks capped under 50k, so ceiling risk." That sentence tells you something a bare 7/10 never could.
Read that confidence rating carefully when you get it, because this is where I think you'd misread it if I didn't say so now. It is not a prediction that your idea will succeed. It's a statement about how strong the evidence is that the problem exists and is underserved. Those are different questions. You could get high confidence on a real, provable, $40k-a-year niche — too small to matter to you specifically. High confidence on a small market is still a small market. Read the audience section before you read the score.
The part where I'd tell you to slow down
Every brief has a Build-this button, and pressing it hands your spec straight to the Builder team — no copy-paste, no summarizing eleven forum threads into a doc by hand, none of the two days that usually evaporate between "we found something" and "someone's building it." That gap is where good ideas die, not from lack of merit but from lack of momentum. Several products in our own Showcase started as briefs nobody on the team thought of first.
Here's what I'd actually tell you to do with your expense-report idea, even with a strong brief in hand: don't press Build-this first. Press the validation step instead. It's less satisfying — the brief will look solid, the evidence section will look clean, and skipping to building will feel like progress. But a problem existing in the wild isn't the same as people paying you to solve it specifically, and a landing page with real ad spend behind it is the cheapest way to learn which one you have. I've watched a brief with clean three-source convergence get a waitlist page up, run against real paid traffic, and pull a 0.4% click-to-signup rate. That wasn't a research failure — the problem was real. It just wasn't worth solving for money, or the brief's own language didn't survive contact with an actual ad. Either way, that's a two-day, low-three-figure lesson instead of a two-month one. For a few hundred dollars of ad spend, you'd know before you wrote a line of code.
Two things that would make me distrust your brief, specifically
Watch for correlated sources dressed up as independent ones. If the complaints agent and the Q&A agent both happen to be reading the same three subreddits, "three sources agree" quietly becomes "one community agrees, counted three times." The source lists are tuned to stay non-overlapping — trends from search data, complaints from forums and reviews, Q&A from dedicated question sites — but if you open your brief and every link traces back to the same domain or the same three-week window, discount the confidence rating more than it's discounting itself. Click the actual links. Two minutes, best gut-check you'll get.
And watch the trend agent for recency bias. A three-week spike in your search term looks identical whether it's the early edge of something durable or the tail of a news cycle about to flatten — the data doesn't come with a footnote telling you which. That's exactly why the format won't let a trend spike stand alone; it needs the complaint history and the unanswered questions behind it too. A spike with nothing else backing it gets scored low, not rejected, because sometimes the noise is early and still worth a cheap test.
So: run it, or don't — the text box is right there either way, and the Builder team won't care whether your spec came from five agents converging on a forum pattern or from you being annoyed at your own expense report this morning. But if you do run it, put the ad spend behind the brief before you put a sprint behind it. I run mine weekly, which is often enough to catch a shifting trend without drowning in briefs I can't act on yet. Let me know what the click rate says.
