What do you use today instead of DocCharm (https://doccharm.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make DocCharm better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

Sherry Kuhlmanneutral

Right now, we manually update our help center articles. We use Jira tickets and a shared Google Doc to track changes, which is very time-consuming, especially after product launches. DocCharm sounds promising because it seems to automate the initial draft creation, which would save us a lot of manual effort. The biggest concern would be ensuring the AI-generated content is accurate and aligns with our brand voice without significant editing. Also, understanding how well it integrates with our existing Jira workflow would be key. If it truly streamlines the process and maintains quality, I could see paying around $150 per month for it.

Simulated interest: 70/100

Guy Hettingerneutral

Currently, I manage all customer-facing documentation using Intercom Articles, Figma for designs, and a detailed spreadsheet to track product changes against compliance updates. DocCharm's promise of automatically drafting updates based on product changes sounds incredibly appealing, given the hours I spend manually keeping our help pages current with our weekly releases. The key for me would be the accuracy of these drafts – if they truly capture the nuance of fintech compliance and product changes without extensive editing, that would be a significant improvement. My main concern is ensuring it integrates seamlessly without requiring a substantial engineering effort, as I only have limited support from that team. The ability for it to flag stale articles proactively is also a strong point. Given my current workload, anything that saves me time here is valuable, but I'm cautious about adding complexity or cost without clear ROI. I'd be willing to pay up to $150 per month, assuming the 'Starter' plan's article limits are sufficient for our needs.

Simulated interest: 75/100

Agrata Naikneutral

Right now, I’m managing our help docs in Notion and a messy spreadsheet. It’s a nightmare—every time we release a feature, our docs get old fast. I’ve tried tools like Conceito and custom doc sites, but nothing sticks. DocCharm sounds promising because it hooks into our product updates and drafts changes for me. The biggest pain point is that I have to review support tickets twice a week because our docs aren’t reliable. What would make DocCharm better? If it actually cuts down on repeat tickets and keeps our content up to date with minimal fuss, I’m sold. The approval step is great—I’m not letting automation go live without my say. The worst part? If it’s another tool I have to manually sync, or if my team resists using it. My team’s reluctance is huge. Maximum I’d pay? $300/month. But only if I see hard numbers on how it reduces support time. Right now, I’d sooner hire a freelance writer for $500 a month and make her fix docs manually.

Simulated interest: 65/100

Aaron Neimkeneutral

Currently, I maintain our documentation manually, pulling updates from GitHub releases, Jira, and QA screenshots. The biggest challenge is keeping it synchronized with frequent code changes, especially with a small team. DocCharm's promise of automatically drafting updates sounds incredibly appealing, as it could save significant time and reduce the risk of outdated information. However, I'd need to understand how well it truly grasps the nuances of our specific API changes. The pricing isn't entirely clear for my team size; the 'Starter' plan at £100/mo seems affordable, but I'm unsure if it covers our volume. If it can genuinely streamline my workflow and reduce those synchronization headaches, I might consider paying up to $200 per month.

Simulated interest: 70/100

Pulchérie Boyerneutral

Currently, I rely on our internal team, assigning article refreshes to one writer and two account managers after each product launch or policy change. We manage this process manually, primarily within Help Scout. DocCharm's promise of automatically drafting updates when the product changes is very appealing, as keeping our documentation perfectly synchronized is a constant challenge. It sounds like it could significantly reduce the workload on my small team and prevent outdated articles from causing customer frustration. The biggest unknown for me is how well it integrates with our specific HR software and the technical effort required from our engineering team for the initial setup. Regarding pricing, the "Starter" plan at £100/mo is listed, but a USD equivalent would be needed for comparison. I could potentially consider a plan around $100 per month.

Simulated interest: 70/100

Jordan Gusikowskineutral

Currently, I'm using a detailed spreadsheet, Intercom macros, and staging screenshots to keep our help center and FAQ updated with monthly feature releases and checkout flow changes. The biggest pain point is manually tracking all these updates and ensuring accuracy. DocCharm's promise of automatically drafting updates based on product changes sounds like a significant improvement. It could potentially save me a lot of time and reduce the risk of outdated information. However, I'd need to understand how it integrates with our specific development pipeline and how much manual oversight is truly required. The pricing isn't entirely clear to me, as it's listed in pounds; if it were $100 per month, that might be acceptable for the Starter plan, but I'd need to confirm the currency. The main thing that would keep me on my current system is a lack of confidence in the automation or if it required extensive technical setup beyond a simple engineer favor.

Simulated interest: 70/100

Chandraprabha Nambeesanneutral

Currently, my team and I manually update our help articles in Confluence and Notion after each sprint. It's a time-consuming process where we gather screenshots and wording from engineers and the support analyst. DocCharm's promise of automatically drafting updates based on product changes sounds incredibly efficient. The ability to approve rather than create from scratch would save significant time. I'm hesitant because I'm unsure how accurately it would capture the nuances of our specific product or if the AI can truly match our brand voice. The pricing seems reasonable at £100/mo for the Starter plan, but I would need to see how many products and articles are covered in that. My maximum acceptable price would be around $200 per month.

Simulated interest: 60/100

Virgil Ritchieneutral

Currently, we manage drafts in Google Docs and then publish to Zendesk Guide after QA. The constant churn of API changes means a lot of manual updating, which can be a bottleneck. DocCharm's promise of automatically drafting updates for API changes is intriguing, as it could save significant time and reduce the chance of outdated articles. However, I'd be concerned about the accuracy of the AI-generated drafts and the potential need for extensive editing. The integration process also seems like a hurdle, requiring an engineer's involvement, which isn't always straightforward. I'd need to see how it truly handles complex API behavior shifts. I'd be willing to pay up to $150 per month for a solution like this, provided it significantly reduces our manual workload and improves documentation accuracy.

Simulated interest: 60/100

Loes van de Venneutral

Today, I'm manually updating our Zendesk knowledge base based on release tickets and input from product designers. It’s a constant struggle to keep everything current with our rapid product changes, and sometimes content falls behind. DocCharm’s promise of automatically drafting updates sounds incredibly appealing, especially the idea of it noticing changes and preparing articles before tickets even come in. The main concern would be how seamlessly it integrates with Zendesk and the accuracy of its AI drafts – would I spend more time fixing than if I just wrote it myself? The pricing isn't entirely clear from what I see; the £100/mo for the Starter plan is roughly €117, which is a significant chunk of my monthly income. I would need to see how it translates to USD and if it fits within a reasonable budget for our small team, but I'm tentatively looking at around $150 per month.

Simulated interest: 60/100

José Eduardo Saldivar Garzapositive

Actualmente, mi equipo maneja las actualizaciones del centro de ayuda con una hoja de cálculo compartida y un CMS. Una persona de mi equipo dedica tiempo a tomar capturas de pantalla después de cada cambio de producto, lo cual es un proceso lento y repetitivo. DocCharm promete automatizar este flujo de trabajo, lo cual sería una gran mejora. La idea de que las actualizaciones se redacten solas y solo necesiten mi aprobación es muy atractiva, ya que liberaría a mi agente de esa tarea tediosa. Me preocupa un poco cómo funciona la conexión inicial con la ingeniería, pero si es realmente un 'favor de una sola vez', está bien. El precio de £100/mes parece razonable para el plan básico, que cubriría hasta 3 productos y 150 artículos. Para mí, eso se traduce en unos $125 USD por mes.

Simulated interest: 85/100