Why we built this
Before we designed anything we read 722 public Reddit posts and comments from people who capture things at trade shows, lectures and conferences. This page is what we found, including the parts that argued against building it.
Secondary analysis of public posts. Not a user study. Not affiliated with or endorsed by Reddit. Statements on this page are rewritten, not verbatim quotes.
- 722posts and comments analysed
- 38global queries × 3 sort orders
- 12pain themes identified
- 4themes we chose not to build
How loud a complaint is has almost nothing to do with how much it hurts.
Click a row to see what we concluded and whether it made it into the product.
| ID | THEME | INTENSITY | IN PRODUCT |
|---|---|---|---|
Lowest mention count, highest emotional charge in every instance. Low frequency, high intensity — this is the bullseye the product is built around. Mentions in the 722-item pool: 5 · 0.7% | |||
Capture friction threshold is 5–10 seconds. Cited independently by three people. This is a hard design constraint, not a nice-to-have. Mentions in the 722-item pool: 19 · 2.6% | |||
Open space: no tool covers photos, audio, the link between them and a forwardable report at once. This is the gap we build into. Mentions in the 722-item pool: 18 · 2.5% | |||
Manual structuring does not survive past day three of a show. Automatic filing at write time is the answer. Mentions in the 722-item pool: 22 · 3% | |||
Highest mention count in the pool — and a mature CRM / lead-retrieval market already. We integrate downstream rather than compete here. Mentions in the 722-item pool: 89 · 12.3% | |||
A real pain, but free tools like Adobe Podcast Enhance are dissolving it. Directional mic addresses it; we don't lead with it. Mentions in the 722-item pool: 45 · 6.2% | |||
Real but thinly expressed. Export handles it; not worth a headline. Mentions in the 722-item pool: 13 · 1.8% | |||
Low frequency, but blocking once triggered. Fully offline storage and no account is the answer — and it must be documented, not implied. Mentions in the 722-item pool: 6 · 0.8% | |||
Almost nobody raises it in a trade-show context (0.6% of the pool). We build it properly but do not lead the homepage with it. Mentions in the 722-item pool: 4 · 0.6% | |||
False pain in this context — the complainers are professional photographers asking about settings, not our users. Mentions in the 722-item pool: 38 · 5.3% | |||
Sample too small to support any conclusion. Parked. Mentions in the 722-item pool: 3 · 0.4% | |||
Second-highest mention count and the wrong audience entirely — professional video crews asking about equipment. Removed from the requirement pool. Mentions in the 722-item pool: 51 · 7.1% | |||
- T4★★★★★CORECan't tell who the photo was of
Lowest mention count, highest emotional charge in every instance. Low frequency, high intensity — this is the bullseye the product is built around.
Mentions in the 722-item pool: 5 · 0.7%
- T8★★★★☆CORENo time to take notes while moving
Capture friction threshold is 5–10 seconds. Cited independently by three people. This is a hard design constraint, not a nice-to-have.
Mentions in the 722-item pool: 19 · 2.6%
- T11★★★☆☆COREExisting tools don't fit, constant switching
Open space: no tool covers photos, audio, the link between them and a forwardable report at once. This is the gap we build into.
Mentions in the 722-item pool: 18 · 2.5%
- T5★★★☆☆COREMaterial piles up, sorting costs too much
Manual structuring does not survive past day three of a show. Automatic filing at write time is the answer.
Mentions in the 722-item pool: 22 · 3%
- T6★★★☆☆NOFollow-up breaks down, leads go cold
Highest mention count in the pool — and a mature CRM / lead-retrieval market already. We integrate downstream rather than compete here.
Mentions in the 722-item pool: 89 · 12.3%
- T1★★★☆☆PARTIALRecordings unusable, hall noise
A real pain, but free tools like Adobe Podcast Enhance are dissolving it. Directional mic addresses it; we don't lead with it.
Mentions in the 722-item pool: 45 · 6.2%
- T7★★☆☆☆PARTIALWriting the recap for the boss
Real but thinly expressed. Export handles it; not worth a headline.
Mentions in the 722-item pool: 13 · 1.8%
- T10★★☆☆☆MUSTPrivacy and recording consent
Low frequency, but blocking once triggered. Fully offline storage and no account is the answer — and it must be documented, not implied.
Mentions in the 722-item pool: 6 · 0.8%
- T12★☆☆☆☆BUILTAI hallucination, can't trust summaries
Almost nobody raises it in a trade-show context (0.6% of the pool). We build it properly but do not lead the homepage with it.
Mentions in the 722-item pool: 4 · 0.6%
- T3★☆☆☆☆NOPhotos come out badly, venue lighting
False pain in this context — the complainers are professional photographers asking about settings, not our users.
Mentions in the 722-item pool: 38 · 5.3%
- T2★☆☆☆☆NOTranscription quality collapses
Sample too small to support any conclusion. Parked.
Mentions in the 722-item pool: 3 · 0.4%
- T9☆☆☆☆☆NOWhich gear should I buy
Second-highest mention count and the wrong audience entirely — professional video crews asking about equipment. Removed from the requirement pool.
Mentions in the 722-item pool: 51 · 7.1%
Counts recomputed from the 722-item evidence pool (one item can hit several themes). The source spreadsheet ships these two columns as uncached formulas, so they are recalculated here rather than left blank or zeroed.
You can't tell who the photo was of.
Lowest mention count in the entire pool. Highest emotional charge in every single instance. Every person raising it had invented their own workaround — numbered cards, voice memos after each booth, renaming files in the taxi.
Low frequency, high intensity. That is the shape of a problem people will pay to remove, and it is the one thing the A2 Pro is built around.
I made everyone hold a numbered card for one shot before the real photos, just so I could match them up later.
The original posts.
Usernames and avatars removed. Click any card to open the original thread on Reddit.
Every line below is a rewritten statement, not a verbatim quote, and none of these people have used or endorsed NoteCapt. Each links to the original public post so you can read it yourself.
I came home with four hundred photos of booths and products. Not one of them tells me who I was talking to.
OPEN THREAD →
A week later I had a stack of names and no memory of who was who.
OPEN THREAD →
People don't forget the name. They forget the conversation — what was said, and why it mattered enough to follow up.
OPEN THREAD →
The photos survive. The context dies within forty-eight hours.
OPEN THREAD →
I need to find people by how I met them, not by their name — because the name is exactly what I've lost.
OPEN THREAD →You cannot take real notes and hold a real conversation at the same time. One of them always loses.
OPEN THREAD →
If capturing it takes more than ten seconds, nobody does it. You just tell yourself you'll remember.
OPEN THREAD →
We recorded the conversations at our booth so we'd actually know what was said when we followed up. The hall was too loud to hear any of it back.
OPEN THREAD →The exhibit hall floor swallows everything. What we got back wasn't usable — we could only read it, never listen to it.
OPEN THREAD →
The spreadsheet I started on day one was dead by day three.
OPEN THREAD →Two of us worked the floor. Our notes never merged — we scanned the same vendor twice without knowing.
OPEN THREAD →
Sorting the badge scans and the business cards takes days. The show took three.
OPEN THREAD →
The show ended at four. I was still backing up and cutting footage at two in the morning, because the recap plays at nine thirty.
OPEN THREAD →Every tool is either locked to somebody's platform, or it's a blank spreadsheet where you do all the typing yourself.
OPEN THREAD →
Show floor Wi-Fi is never what they promised. Whatever I use has to work with no signal at all.
OPEN THREAD →
I made everyone hold a numbered card for one shot before the real photos, just so I could match them up later.
OPEN THREAD →Rewritten from public posts on Reddit. Not testimonials — these people have not used NoteCapt.
Four things the data told us to walk away from.
The most-mentioned theme in the whole pool is one we chose not to enter.
- T6CRM and lead retrieval
The single most-mentioned theme in the pool — and a mature market with entrenched players. We hand off to HubSpot and Salesforce rather than compete with them.
- T9Camera and recorder gear advice
Second-highest mention count, entirely the wrong audience: professional video crews asking about equipment. Removed from the requirement pool.
- T3Better photos in bad lighting
Judged a false pain in this context. The people complaining are photographers asking about settings, not knowledge workers losing context.
- T12AI hallucination as the headline
Only 0.6% of the pool raised it. We build zero-hallucination properly — but leading with it would mean educating people about a problem they haven't hit yet.
The landscape, by mention count.
Method
38 global queries × 3 sort orders. Three exclusion gates: narrative subs, serial posters, off-context threads. Comments pulled on the 450 most relevant threads. Proximity scored on trade-show terms against capture terms. Narrowed to target-audience subs → 722 records.
What this is not
Mention counts measure how many people posted about something online, not how much it hurts. Reddit skews toward English-speaking, technical, self-selecting users. Two methodology revisions were needed after the first pass scored purely on keyword counts. We are not claiming statistical representativeness.
The parts that argue against us
Reproduced from the research notes without editing. A page that only contained the findings supporting the product would not be worth reading.
- "Records it clearly" is being dissolved
- The author of the r/videography hall-recording post came back with an update: a low-gain lapel mic plus Adobe Podcast Enhance worked extremely well. Noise suppression is now commodity — free from Adobe, built into phones, built into devices like Plaud. The positioning should move from "records it clearly" to "you can find it again afterwards".
- "Takes sharper photos" has no support
- Of 39 photo items, the overwhelming majority are professional photographers asking about settings, not ordinary attendees complaining about blur. The one buyer who said half his photos were blurry cared about them being unsorted — the app he built himself has no image enhancement either. Removed from the value proposition.
- A post proposing the same solution got no response
- The 2025 r/sales post describing almost exactly this product — record the conversation, transcribe, summarise, next step — got 0 upvotes and 0 comments. In the same period, "I cannot remember who I met" got 24 upvotes and 94 comments. The difference is that one sold a solution and the other described a pain.
- Willing to use is not willing to pay
- A commenter on r/indiehackers said it directly: conference CRM is a classic category where plenty of people say they would use it and far fewer actually pay.
- The vertical communities are tiny
- r/tradeshows has 2,464 subscribers and r/eventprofs has 668, while r/sales has 590,000. Trade show professionals do not gather on Reddit, so the sample is inherently thin — and online acquisition through these channels may be poor.
- No Chinese-language sample
- Reddit only covers English-speaking communities. Buyers at domestic Chinese trade shows barely post there at all. Whether that scenario is structurally the same has to be verified through other channels before anything here is extrapolated to it.
- Do not cite the 75% figure
- One post claims 75% of leads go cold within 72 hours of a show. It is vendor content marketing with no source. It can inform the narrative; it cannot be cited as a fact.
If this research is why you're here, we'll send you one email when we launch.
Secondary analysis of public posts. Not a user study. Not affiliated with or endorsed by Reddit. Statements on this page are rewritten, not verbatim quotes.