Think about your own work or business in this area: Show HN launch (10 pts, 2020-10-19): the product – Knowledge base and wiki for teams. Site shows pricing/signup. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.
10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations
Simulated interest
AI synthesis, not measured demand
Suggested price range
No numeric price estimates in the answers. Ask a pricing follow-up to collect them.
Response sentiment
What this panel suggests
Respondents mostly describe a practical knowledge-management problem rather than a lack of interest in the category: their work is slowed by fragmented documentation, scattered versions, and the need to repeatedly hunt across tools like Google Docs, Notion, Confluence, spreadsheets, Slack, SharePoint, and Teams. The most consistent pain is time loss from manual cross-checking and rework, plus onboarding friction when people must keep re-explaining processes because the right information is hard to find or may be outdated. A second major theme is governance: even where a wiki or documentation stack already exists, teams struggle to get people to use it consistently and to keep content current. That creates skepticism about whether a new knowledge base will solve the real issue if it does not fit existing workflows. Overall sentiment is mixed and mostly neutral, with some negative reactions driven by implementation concerns. WTP is not established here, so this batch is better read as evidence of pain points and objections, not pricing intent.
Recurring themes
“Our biggest hurdle right now is definitely information silos.”Read Myrtle Mann’s response →
“I spend hours each week manually cross-referencing everything to ensure accuracy, which is a massive drain on my time – easily 5-7 hours weekly.”Read Marvin Fadel’s response →
“my biggest problem is getting my 30-person consultancy to consistently *use* the documentation infrastructure we've painstakingly set up in SharePoint and Teams.”Read Grady Stoltenberg’s response →
Objections to investigate
- Integration with existing workflows
- Uncertainty about migration effort
- User adoption resistance
Use these findings to plan customer interviews or experiments. How to interpret AI research
What the panel said
Click a name to open that persona’s full profile.
Myrtle MannnegativeOur biggest hurdle right now is definitely information silos. We're using a mix of Google Docs, a free Notion workspace, and shared Drive folders, and keeping everything consistent across them is a constant time sink. I spend hours manually updating and cross-referencing things, especially when new features roll out or policies shift, which happens weekly. It's not costing us direct dollars, but the inefficiency and potential for errors during onboarding or just general knowledge retrieval is a real drain on my time, which is already stretched thin.
Simulated interest: 70/100
Marvin FadelnegativeThe biggest problem for my team right now is the sheer fragmentation of our institutional knowledge. We've got formal playbooks in Confluence, but urgent fixes, temporary instructions, and nuanced edge cases are scattered across spreadsheets and endless Slack threads. I spend hours each week manually cross-referencing everything to ensure accuracy, which is a massive drain on my time – easily 5-7 hours weekly. This chaos slows down new agent onboarding and risks inconsistent client responses. We've tried just sticking to Confluence more, but the real-time nature of support means information inevitably bleeds out.
Simulated interest: 90/100
Annelie MadubukoneutralOur biggest challenge is the fragmented nature of our documentation. Key policy documents live in SharePoint, contractor information is scattered across Excel sheets, and useful guides are often duplicated in Google Docs for freelancer access. This means I spend a significant amount of time searching for information or re-explaining things, which easily adds up to several hours each week. It also increases the risk of outdated information being shared. We've tried creating unified folders, but it's a constant effort to keep everything in its place. A centralized knowledge base sounds appealing if it could truly consolidate everything and make it easily searchable for both the team and our freelancers.
Simulated interest: 70/100
Divaakar JhaneutralA knowledge base and wiki for teams, you say? The single biggest problem for us right now is exactly that – consolidating all our process notes, client setup steps, and internal FAQs. They're scattered across WhatsApp, Google Sheets, and Docs. It takes up so much time, easily a few hours a week, just hunting for information or ensuring everyone's on the same page. We've tried creating shared folders and standardized templates, but it's still clunky. I'm not sure how this product compares in terms of ease of use and integration with our current workflow, but the idea of a centralized, searchable hub is very appealing.
Simulated interest: 75/100
Bernard BlandaneutralKnowledge base and wiki for teams? We already use a mix of GitHub wiki and Google Docs. My biggest problem right now is the information silos that form between our developers and the non-technical folks like account managers and designers. Getting everyone on the same page, especially with complex technical details or client feedback that gets lost in translation, is a constant challenge. It costs us time in rework and clarification, and it definitely slows down onboarding new team members. We've tried standardizing templates in our Google Docs, but enforcing consistent updates across both platforms is the real hurdle.
Simulated interest: 30/100
Sylviane DurandneutralThe biggest problem is the sheer time spent locating the correct, most up-to-date version of a document or procedure. Our operations team frequently asks me where to find a specific form or checklist, and it often requires digging through multiple Google Drive folders, old PDFs, or even printed binders. This easily costs me several hours each week, which is valuable time I could be using for proactive organizational improvements or critical tasks. We've tried creating a more logical folder structure, but it's a constant battle with everyone's individual saving habits. The idea of a central, easily searchable knowledge base is appealing, but I wonder how it integrates with our existing paper system.
Simulated interest: 70/100
Manu van DongennegativeThe single biggest problem we face is information silos. Our process notes live in Coda, client onboarding is a mess of scattered Google Docs, and I maintain this behemoth spreadsheet for links and templates. It's costing us significant time – easily several hours a week per person – as the team hunts for the right document or template version. We've tried standardizing naming conventions, but it's not enough. The real cost is the friction it creates and the potential for inconsistent client delivery.
Teresa Santillán BahenaneutralThe biggest problem we have right now is how fragmented our client onboarding information is. It's scattered across spreadsheets, Google Docs, and even random Loom videos. It probably costs us at least 5-10 hours a week collectively just trying to track down details or clarify processes, which delays handoffs and can lead to errors. We've tried standardizing some of the documentation in Google Docs, but it's hard to keep consistent and easily searchable. I'm not sure if a knowledge base is the solution, but the idea of a central place for all this information is appealing. What kind of pricing are we looking at for a team our size?
Simulated interest: 60/100
Ahalya JoharneutralThe single biggest problem I face is maintaining consistent and accurate information across our training materials. Supervisors directly edit Excel sheets and shared folders, which often leads to conflicting procedures and outdated FAQs. This costs us significant time as I constantly have to reconcile these changes and re-train agents on the correct information. I've tried implementing stricter version control, but it's difficult to enforce with direct edits. I'm curious if a dedicated knowledge base would truly centralize this and prevent such inconsistencies. What kind of effort is involved in migrating existing, disparate documents?
Simulated interest: 30/100
Grady StoltenbergnegativeA knowledge base and wiki for teams? Frankly, my biggest problem is getting my 30-person consultancy to consistently *use* the documentation infrastructure we've painstakingly set up in SharePoint and Teams. It's not a lack of tools, it's the reluctance of team leads to adhere to templates and version control. This leads to outdated project plans being used, which costs us time in rework and, more critically, risks client dissatisfaction – a reputational hit I can't afford. We've tried implementing stricter protocols, but it's an ongoing battle.
Simulated interest: 0/100
Keep exploring.
Find your next question or see which topics divide AI panels.
What would you ask next?
Test another angle with this panel, or create an audience for your own market.