User guides, written from scratch or rebuilt
Written from your end users' perspective. We learn your product the way your users learn it, so we don't assume what they don't know yet.
See documentation writingWe write documentation for Business Central apps. It shows your unique know-how in full depth.
Pick the one of our three documentation services that matches the current state of your documentation.
Written from your end users' perspective. We learn your product the way your users learn it, so we don't assume what they don't know yet.
See documentation writingHelp where users look first, right in Business Central: tooltips, Ctrl+F1 help, and help content Copilot can use.
See in-app helpYour consultants and developers write the documentation. We train them, set the standards, and review their work, so the quality holds over time.
See training and quality reviewDocumentation is one of the first signals customers use to judge product quality when they compare Business Central applications on AppSource. Business Central partners evaluating your app for their own customers read the documentation before they recommend it. A well-structured knowledge base gives them the depth to evaluate your app with confidence, and it improves your search rankings through relevant keywords and backlinks. Customer confidence grows the moment they see reliable self-service support in place.
69%of B2B software buyers ended up choosing a different vendor than they originally expected, based on AI chatbot guidance, and 33% purchased from a brand they'd never heard of.
G2 2026 AI Search Insight Report
A complete knowledge base lets customers find what they need when they need it, which reduces frustration and errors. Over time, it helps them discover more of what your app can do.
Customers typically keep using only what they learned during initial training. Without documentation, many valuable features stay hidden. Good documentation helps customers use the full functionality of your app and get the return they expected when they bought it.
80%of features in the average software product are rarely or never used.
Pendo, 2019 Feature Adoption Report
Self-service documentation reduces the load on your service desk by letting customers solve problems themselves. At many Business Central partners, the people answering those tickets are the same developers who built the feature. Every repeat question your documentation answers gives developer time back to your product, not just a lower support bill.
Customers prefer finding an answer immediately over waiting in a queue. Every question your documentation answers is one your team doesn't have to, so they can focus on complex requests.
A growing share of those answers comes from AI instead of a person, and AI can only resolve what your documentation actually covers.
50%of service cases are expected to be resolved by AI by 2027, up from 30% in 2025.
Salesforce, State of Service
More customers now use AI to research software before they ever contact you. They might:
Copilot in Business Central can answer questions about the apps installed in a customer's environment. Microsoft's guidance for app publishers says Copilot bases these answers on your online help. If there's no structured content for it to find, Copilot has little to work with. A complete, well-structured knowledge base gives it accurate material, so it describes your app correctly instead of guessing.
“Rather than relying on Large Language Models to answer questions, where the AI model might not know the details of your app, Copilot uses your online content as grounding data to provide better answers.”
Microsoft Learn, Prepare your app Help for Copilot

Documentation keeps critical product knowledge inside your organization, even when the product managers and developers who built your app move on.
A well-structured knowledge base limits information loss and speeds up onboarding for new employees. Without it, expertise remains with a few individuals and is hard to recover once they leave.
42%of institutional knowledge is unique to the individual.
Panopto
We write your documentation to the Microsoft Writing Style Guide, the rules for tone, terminology, formatting, and structure that Microsoft Learn follows. Business Central users feel at home in it from the first page.
See an example
We organize your documentation the way Business Central's own documentation on Microsoft Learn is organized. Business Central users already know that structure, so they know how to navigate it.
See how we structure documentation
We match the design and layout of Microsoft Learn, so customers know they're in the right place. Your documentation feels like a natural extension of the product, not a separate site they have to learn first.