Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / Bootstrapped Founders Use Customer-Generated Documentation
Transcript
- Lucas: There's this moment every bootstrapped founder knows — you've built something people want, customers are signing up, and then you realize: they have no idea how to use it. So you sit down to write documentation, and two weeks later you've got a half-finished knowledge base that reads like a software manual from 2005. Luna: Right. And the problem is, you're a founder, not a technical writer. The docs either come out too jargon-heavy or too vague. Lucas: Exactly. So today I want to talk about a different approach — one that a handful of bootstrapped SaaS companies have turned into an actual growth engine. It's customer-generated documentation. Not crowdsourcing your help articles from random users, but systematically letting your best customers write the docs for you. Luna: I've seen a few companies do this. Close.com — the CRM for sales teams — they're a good example. They're bootstrapped, profitable, and they let their power users contribute directly to their knowledge base. Lucas: Close is exactly the case I want to anchor on. They've been running this for a few years now. The way it works: any user can submit an edit or a new article to their documentation. It goes through a lightweight review by the team, and if it's accurate and helpful, it goes live with the contributor's name on it. Luna: And they track which articles get the most views. The community-authored ones actually perform better on search, because they use the language that people actually type into Google. Lucas: That's the key insight. Customers describe features differently than developers do. A developer might write 'configure lead scoring thresholds' — a customer writes 'set up automatic lead prioritization so your best prospects don't get lost.' Which one sounds like a real search query? Luna: Yeah, the customer version every time. And it's not just SEO. Close found that articles written by customers had a 30 percent lower bounce rate than their internal ones. Lucas: Makes sense. If you land on a page and it sounds like someone who actually uses the product, you're more likely to trust it and keep reading. But let's talk about the mechanics, because this isn't just opening a wiki and hoping for the best. There's a real process behind it. Luna: What's the first step? How do you even get customers to volunteer to write docs? Lucas: You don't ask them out of the blue. The pattern I've seen work — and Close did this — is to start with your support tickets. Identify the questions you answer over and over. The top 20 or 30 questions that make up maybe 60 percent of your support volume. Then go to the customers who ask those questions most intelligently — the ones who clearly understand the product — and say, 'Hey, you asked about X. Would you like to write a short guide on how you solved it?' Luna: So you're recruiting from your most engaged users. The ones who already care enough to ask good questions. Lucas: Exactly. And you make it easy. Give them a template — a simple structure: what's the goal, step-by-step instructions, a screenshot or two. You're not asking for a novel. One page, maybe three hundred words. That's it. Luna: And they get recognition. Their name on the page, maybe a badge in the community. For power users, that's often enough motivation. Lucas: Right. No payment. This is not a gig. It's a contribution. And bootstrapped founders love that because it's essentially free content that also builds customer loyalty. But here's the part that scares most founders: accuracy. What if a customer writes something wrong? Luna: That's the big risk. A bad doc can lead to product confusion or even data loss if it's about something like importing contacts. Lucas: So you need a review layer. Close has a small internal team — sometimes just one person — who checks every submission before it goes live. They're not rewriting it, they're verifying: does this actually work? Is the screenshot current? Does it match the latest UI? If it's good, they publish it. If not, they send it back with notes. Luna: And what about versioning? As the product changes, old docs go stale. Lucas: That's the second piece. You need a system to flag articles that haven't been reviewed in, say, six months. Close tags them as 'needs review' and sends an email to the original contributor: 'Hey, your article about workflow automation was last updated in January. Has anything changed?' Often the contributor will update it themselves. Luna: So the community maintains it. That's clever because it scales without adding headcount. Lucas: Exactly. And the numbers bear this out. Close's knowledge base now has over a thousand articles, and roughly 40 percent of them were originally written by customers. Their support ticket volume as a percentage of active users has dropped significantly — they've published a few case studies showing a 30 percent reduction in tickets over two years. Luna: That's a huge efficiency gain for a bootstrapped team. Fewer tickets means fewer support hires, or more time for the existing team to work on churn reduction and upsells. Lucas: And it compounds on the SEO side. Customer-written docs naturally contain the phrases that prospects search for. Close found that their community docs drive about 25 percent of their total organic traffic, and those visitors convert at a higher rate because they're reading content that feels authentic. Luna: I want to push back a little though. This works for a product that's mature enough to have power users. If you're a brand new SaaS with twenty customers, you probably don't have anyone who can write a doc yet. Lucas: Fair point. I'd say this is a strategy for when you have at least a few hundred active users and a clear set of recurring support questions. Before that, you're better off writing the docs yourself or using a tool like Tettra that lets you draft quickly. But once you hit that inflection point — it's a real lever. Luna: What about products that are very technical, like developer tools? Can this work for an API company? Lucas: Actually, developer tools might be the best fit. Developers are used to contributing to documentation — look at open source projects. A bootstrapped API tool called JSON Schema Validator — they have community-contributed examples and tutorials. The key is to separate the reference docs — which should stay internal and precise — from the how-to guides and use cases, which are perfect for customer contributions. Luna: So the reference docs stay curated, but the 'how do I actually do X' content gets opened up. Lucas: Right. And you can incentivize contributions with things like early access to new features or a 'documentation contributor' badge on your community forum. No cash needed. Bootstrapped all the way. Luna: Let's talk about a potential downside. What if a customer writes a doc that's factually correct but poorly written? Like, grammatically messy or hard to follow. Do you fix it or reject it? Lucas: That's a judgment call. The philosophy at Close is: if it's accurate, publish it with light editing. They'll fix typos and rephrase for clarity, but they don't rewrite the voice. They want it to sound like a customer. A slightly imperfect sentence can actually be more relatable than perfect corporate prose. Luna: I like that. It's the same reason user reviews are more persuasive than marketing copy. There's a built-in authenticity. Lucas: Exactly. And it creates a feedback loop. When customers see other customers contributing, they think 'I could do that.' The more docs you have, the more contributions you get. It's a network effect on your knowledge base. Luna: Are there tools that help manage this? Or are most teams building their own workflows? Lucas: Some use a wiki platform like Confluence with a community add-on. Others use a dedicated knowledge base tool like Helpjuice that allows guest contributions. Close actually built a custom layer on top of their existing docs — they use a static site generator and accept pull requests on a private GitHub repo. That's more technical, but it gives them full control. Luna: Right. And they're a bootstrapped company, so they have the engineering talent to set that up. For non-technical founders, something like Helpjuice or even a simple Notion page with a submission form could work. Lucas: Absolutely. The tool matters less than the process. You need a clear way for customers to submit, a review workflow, and a feedback loop. Start with just one or two power users, get a couple of articles live, and see if the traffic and ticket reduction follow. Luna: I'm sold on the concept, but let's talk about measurement. How do you know if it's working? Lucas: Three metrics. First, support ticket deflection — are the articles that rank highest also the ones that reduce tickets? Second, organic traffic to documentation pages — you should see steady growth. Third, contribution rate — how many unique customers submit at least one article per quarter. If that number is trending up, your community is engaged. Luna: And what's a reasonable target for a small bootstrapped SaaS? Twenty contributing customers a year? Fifty? Lucas: I'd say ten is a good start. If you get ten high-quality contributions in the first year, you've got a solid foundation. After that, the network effect kicks in. Close has hundreds of contributors now, but they started with a handful. Luna: I want to come back to the authenticity angle because I think it's underrated. When a prospect reads a doc written by a user, they're essentially getting a peer recommendation. It's a subtle form of social proof woven into your product content. Lucas: Exactly. And it's cost-effective. Every community doc is an asset that keeps paying dividends. It drives traffic, reduces support load, and builds community. For a bootstrapped founder, that's a triple win. Luna: And you're not giving up equity or paying recurring costs. Just investing a bit of time to set up the workflow. Lucas: Precisely. And that's the bootstrapped philosophy in a nutshell — find a way to turn your customers into contributors, and let the product's community become part of the product itself. Luna: By the way, speaking of things that keep the show ad-free and independent — listener support really does make a difference. A couple of dollars a month helps cover hosting, transcription, and the research that goes into episodes like this one. Lucas: Yeah, it's true. If these conversations are useful for what you're building or running, you can head over to buy me a coffee dot com slash fexingo. Small contributions genuinely add up and let us keep doing this without sponsors or ads. Luna: Exactly. And now, back to documentation. One question I had — how do you handle translations? If your product is used globally, customer-generated docs could be in multiple languages. Lucas: That's a great point. Some bootstrapped companies start with English only and then let the community translate. There are tools that integrate with Crowdin or similar platforms. But honestly, for most small SaaS products, English-first is fine. You can add a 'contribute in your language' call to action later. Luna: Makes sense. Let's wrap with a concrete takeaway. If a founder listening wants to start this week, what's the one thing they should do? Lucas: Go through your last fifty support tickets. Pick the top five questions that come up repeatedly. Then find the customer who asked each one most clearly — the one who almost wrote a doc in their ticket. Email them: 'You had a great question about X. Would you like to turn your solution into a one-page guide for other users? We'll credit you and link to your site.' Start with one article. See what happens. Luna: Low risk, high potential. I like it. Lucas: And that's how you turn your customers into your documentation team — without a single VC dollar.