Book a meeting

Services

Choose the service that fits the current state of your documentation, or combine several. Each one is built for Business Central apps.

1Documentation writing

User guides, written from scratch or rebuilt

Written from your end users' perspective. We don't assume what they don't know yet.

We write your app's end-user documentation: functional overviews, step-by-step procedures, setup and configuration guides, and troubleshooting content, structured to match Microsoft Learn standards. We write it from scratch when none exists, or rebuild it when your current documentation doesn't serve your customers well.

We gain a deep understanding of your product while writing. But we do so from the end-user perspective. We learn your product just like your end users learn it, and write about it in a way they can understand.

Rebuilding documentation that isn't working

Existing documentation is usually written by the consultants or developers who know the app best. That's often the problem. It explains what a feature is, but rarely the exact steps to use it, and it assumes knowledge a first-time user doesn't have yet. We rebuild it into procedure-first content in Microsoft Learn structure, tone, and style, and add the beginner path that's usually missing. We change only what needs to change, keep what the existing material already got right, and check the result against the original so no fact is lost or changed by accident. We also fill the gaps: we document features that were never covered and update information that's out of date.

Diagrams and visual explanations

Where a process is easier to show than to explain, we add process flows, data flow diagrams, and business logic overviews. They help customers learn your app, and they help your own team transfer knowledge internally.

Docs-as-code

Articles are written in Markdown in VS Code, and stored and versioned in GitHub or Azure DevOps. The process is very similar to code development. Every change is tracked, easy to revert, and reviewed before it goes live. It's the approach the biggest IT companies, such as Microsoft, Google, and Amazon, follow for their own documentation.

DocFX

Our default publishing tool, and the right choice if you don't already have a preference. It's free, fast to set up, and produces a searchable site with a layout that follows Microsoft's own patterns, so Business Central users feel at home.

ALDoc reference documentation

Developers who build on your app, your own team or a partner extending it, get accurate reference documentation that needs little manual maintenance. It's generated from your AL source code and its code comments, and organized the way Business Central's own object reference is. ALDoc is based on DocFX.

ALDoc tool
2In-app help

Help content inside Business Central

Help where users look first, right in Business Central: tooltips, Ctrl+F1 help, and help content Copilot can use.

Your online help is where customers go to read about your app. In-app help reaches them earlier, inside Business Central, on the page where they have the question. Business Central gives you several tools to help users inside the app, such as tooltips and context-sensitive help. Once your documentation exists, creating this content takes far less work, because most of it is already done while writing the documentation. For each item, we deliver the content and the design. Your developers handle the AL implementation.

Tooltips

The fastest way to answer a user's question: the user gets an explanation at the field where they need it, without leaving the page. We provide tooltip text for every field, within Business Central's character limits, ready for your developers to implement and, where useful, reused and explained in more detail in the documentation.

See on Microsoft Learn

Context-sensitive help

Users get help for the exact page they're working on: they press Ctrl+F1, and the article about that page opens. Without this setup, they typically land on a generic page instead. We map your AL pages to the right online help articles.

See on Microsoft Learn

Copilot enablement

Customers get accurate answers inside Business Central, through Copilot, instead of leaving your app to search for help or filing a ticket. We publish your help site according to Microsoft's guidance for Copilot in Business Central. We then test it with real questions in a sandbox.

See on Microsoft Learn

Teaching tips and in-app tours

New users discover your app's key features as they work, without reading documentation first. We provide short in-app callouts (title and description) and the tour sequence, for both standard teaching tips and spotlight tours that highlight one part of the screen.

See on Microsoft Learn

Get started checklist

New customers get a guided path to a working setup, instead of guessing what to configure first. We build the checklist on Business Central's Guided Experience framework: manual setup steps, assisted setup guides, guided tours, and links to learning content, in the order that fits your app.

See on Microsoft Learn
3Training and quality review

Make your team self-sufficient in documentation

Your consultants and developers write the documentation. We train them, set the standards, and review their work, so the quality holds over time.

If you prefer that your own consultants and developers write the articles, keep in mind that without a person responsible for documentation, its overall quality tends to be poor. Documentation simply becomes no one's responsibility. Yet documentation is often the first indicator customers see of your app's overall quality. Grammar mistakes, inconsistent terms, shortcuts that make sense only to the writer, unverified screenshots, outdated information, and features that aren't documented at all shape how a customer judges a product that's built to a much higher standard. Consultants and developers also tend to explain how a feature works or how they built it, while users usually open the documentation to quickly find out how to complete a task, so they can get back to work.

Our role is to make sure the content meets one consistent standard. We set up the structure, the style guide, and the review process, coach your writers, and review what they write. The long-term goal is a team that writes new content on its own, while we make sure the quality is maintained.

Writer coaching and peer review

Ongoing coaching and peer review for the consultants and developers who write your documentation, so everyone follows the same style guide and writes content customers can follow.

Structure and information architecture

A documentation structure and table of contents for your app, using frameworks like Diátaxis where they fit: landing page, quickstart, key concepts, tutorials, how-to guides, and reference.

Style guide and editing

A style guide built from the Microsoft Writing Style Guide issues we find most often in your existing content, plus editing and auditing of that content against the guide.

Analytics

An analysis of your service desk tickets and your documentation site's usage data, for example from Google Analytics, to find trends and the articles your customers need most.

Keywords and SEO

A keyword list and an internal-linking review, so customers and search engines find your articles.

Layout

Layout improvements that bring your documentation site closer to Microsoft's own patterns, so it feels familiar to Business Central users.

ALDoc reference documentation

Reference documentation that ALDoc generates from your AL source code and the code comments your developers write.

ALDoc tool

Docs-as-code review

Source control setup, DocFX configuration, and best practices for your build and release pipeline.

Check how to improve your Business Central app docs

Book a meeting