AssistCamp

Author: Istiak Rayhan

  • Why You Should Publish More Documentation of Your Product Now Than Before

    Why You Should Publish More Documentation of Your Product Now Than Before

    In the past, documentation was written for users only. That meant just enough detail to reduce support tickets and improve onboarding — not always a deep dive into every feature or use case.

    Now, things have changed.

    With the rise of LLMs like ChatGPT, documentation is no longer just for human users. It’s also for AI and that changes everything.

    LLMs Are the New Front Door to Your Product

    Large Language Models (LLMs) like ChatGPT, Claude, and Gemini are rapidly becoming a new interface for the web. People are no longer just searching Google or browsing your homepage – they’re asking AI directly:

    How do I set up a pricing table in Plugin X?

    Does Tool Y support image uploads?

    What’s the best way to integrate Product Z with Stripe?

    ＋

    If your product documentation isn’t publicly available or if it’s too shallow, there’s a good chance the AI assistant won’t know the answer.

    That’s a missed opportunity.

    LLMs Learn From Public Content — Like Your Docs

    Here’s how it works:

    LLMs are trained (and often continuously fine-tuned) on publicly available content — blogs, forums, documentation, changelogs, and help articles.

    If your docs are out there, well-structured, and rich in detail, the LLMs can “learn” about your product, its capabilities, and how it solves problems.

    The result?

    When someone asks about a feature your product offers, the AI is more likely to recommend your tool, even if the person asking has never visited your site.

    Documentation is Now Marketing

    This shift turns documentation from a support resource into a marketing asset.

    Well-written docs can:

    • Educate your users
    • Reduce support tickets
    • Improve onboarding
    • AND now, help AI confidently suggest your product to potential users

    That’s powerful.

    Instead of spending thousands on paid ads, you could be helping LLMs promote your product organically — simply by having great documentation.

    But It Has to Be Public and Useful

    For this to work, your documentation must be:

    • Publicly accessible (no login walls)
    • Clear and structured
    • Feature-rich and up to date
    • Written in plain English, not vague or overly technical

    Bonus points if you have:

    • A changelog
    • A roadmap
    • FAQs
    • Use case examples
    • Troubleshooting guides

    The more AI can pull from, the better it can represent you.

    AI-Powered Tools Rely on Good Docs

    Even beyond ChatGPT, we’re seeing a wave of tools – AI assistants, website bots, browser extensions, and helpdesk agents — that use your documentation to provide smart answers to users. If you’re not writing documentation now, these tools won’t be able to assist your users effectively.

    You’re not just writing for humans anymore, you’re writing for AI that helps humans.

    Final Thoughts: Don’t Wait

    If you’ve been putting off writing documentation because “we’ll do it later,” now is the time to rethink that. With the rise of LLMs, documentation is more valuable than ever before.

    It’s not just about helping people who are already using your product.

    It’s about helping AI introduce your product to the people who need it.

    Publish more. Document everything. And do it now.

  • Planning an AI Assistant for AssistCamp: Here’s What We’re Thinking

    We’ve all seen chatbots on websites. And while they can be helpful, they often felt robotic – like you were talking to a script, not getting real support.

    But something changed after ChatGPT came into the picture. People are now more open to getting help from an AI Assistant, as long as it feels useful and actually understands what they need.

    That shift got us thinking:

    What if AssistCamp had an AI Assistant — one that actually understands your product?

    The Idea: An AI Assistant, Not a Chatbot

    We’re not trying to build a fake live chat experience. No typing bubbles, no “one moment please,” no bait-and-switch.

    Instead, we’re building a helpful, lightweight AI Assistant you can interact with from the corner of your site and it’ll actually know your product, because it’s trained on your content.

    The name matters too. People don’t expect magic from a “chatbot.”
    But they do trust an AI Assistant and that’s what we’re leaning into.

    What It Will Actually Do

    At first, our AI Assistant will pull answers primarily from your documentation.

    If you’ve written good docs (with the help of our “Write with AI” feature, maybe 😉), it should answer most questions your users have.

    But we won’t stop there.

    Eventually, the Assistant will also reference:

    • 📄 Documentation (so users can get best answers)
    • 🔄 Changelog (so users can ask about recent updates)
    • 📍 Roadmap (so they can ask what’s coming)
    • 💡 Feature Requests (to check if their idea already exists)
    • 💬 Forum Threads (for common community questions)
    • 📝 Blog posts (as long-form context or how-to guides)

    It’ll be like giving your users the power to search everything and actually get useful answers, in plain English.

    What Happens If It Doesn’t Help?

    No AI is perfect. And we don’t want users to feel stuck.

    That’s why we’ll always include a “Contact Support” button if the AI can’t help – no frustration, no dead ends.

    In fact, we might even train the Assistant to know when it’s confused and suggest contacting support on its own.

    Why This Matters

    At the end of the day, our goal with AssistCamp is simple:

    Help you support your users — without making your life harder.

    This AI Assistant is just one part of that mission.

    It won’t replace your team. But it will reduce repetitive questions, save time, and give your users the instant help they’re hoping for — without you having to do anything extra.

    Still in the Works

    This isn’t live yet. We’re still working on the docs module, and this AI Assistant will come later.

    But we wanted to share the idea now — because this is where AssistCamp is headed.

    We’re excited to build it in the open and shape it with your feedback.

    What Do You Think?

    Would you find this useful on your product site? What would you want an AI Assistant to do?

    We’d love to hear from you.

    👉 Join the waitlist if you haven’t already, and stay in the loop as we build this out.

  • Write Documentation With AI: How We’re Building It in AssistCamp

    Writing documentation is one of those tasks we all know is important, but it often gets postponed. It’s time-consuming, repetitive, and rarely fun.

    As a plugin maker, I’ve felt this pain firsthand. And that’s why, while building AssistCamp, one of the first features I’m most excited about is something I’ve always wished existed:

    A “Write With AI” feature that doesn’t just write – it understands screenshots too.

    Why AI Documentation Makes So Much Sense

    AI tools like ChatGPT are great at writing technical content. But when it comes to documentation for a specific product, they often lack the context – they may not know enough about your plugin or SaaS to be truly helpful.

    Most current documentation plugins (like BetterDocs) generate content based on a simple prompt or title. That’s helpful, but not enough.

    As builders, we often explain things based on what the user sees: a settings panel, a dashboard, a button, or a form.

    That’s where screenshots become critical. And that’s exactly what we want to bring into the picture (literally).

    The Vision: Write Docs From Screenshots

    We’re building Write With AI in AssistCamp to work like this:

    1. Upload a screenshot
    2. Enter a short title or prompt
    3. Click “Generate Documentation”
    4. Instantly get a well-structured, clear explanation of the UI — written by AI

    Our AI assistant will “look” at the screenshot, understand the interface, and generate step-by-step documentation that describes what’s happening and how to use it.

    You’ll still be able to edit and tweak the content before publishing, but this gives you a smart, structured starting point, not just a block of generic AI text.

    A Sneak Peek: How It Might Look

    Here’s an early concept of the interface:

    You’ll be able to:

    • Upload one or more screenshots
    • Optionally add a prompt or title
    • Click a button to instantly generate documentation content

    We’re also exploring features like:

    • Templates for common doc types (Setup Guide, Feature Overview, etc.)
    • Smart block suggestions (e.g., tables, warnings, notes)
    • Translation-ready output

    Why We’re Starting with Documentation

    AssistCamp is being built as a modular product hub plugin for WordPress – one that will eventually include feature requests, changelogs, roadmaps, forum, and chatbot.

    But we’re starting with Documentation for a few key reasons:

    • It’s the core of every great product
    • It’s where most SaaS/WordPress tools struggle
    • It allows us to showcase our AI integration early
    • It’s a standalone module that delivers immediate value

    Plus, good documentation sets the foundation for everything else — from support to product feedback.

    Where We Are Now

    We’re still building AssistCamp. The plugin isn’t live yet — but we’re moving fast and testing the AI workflows already.

    If you’re interested in testing the “Write with AI” feature or want early access, you can join the waitlist here.

    Final Thoughts

    Writing documentation doesn’t have to feel like a chore.

    With AssistCamp, we want to make it faster, easier, and smarter — with help from AI that understands what your users see.

    If you’ve ever struggled with writing docs, or have ideas on what your dream AI-powered assistant would do, I’d love to hear from you.