Questions and answers

An extension adds a feature to your Microsoft Dynamics 365 Business Central without changing the standard product. It can add a field, a rule, an approval step, a report or a link to another system.

Because it sits beside the standard product, it can be added, updated and removed on its own.

Yes. AppoGen uses AI to help with research, design, building and testing.

The price is not decided by AI. It is worked out by fixed rules from your approved design. Your description is treated as information about your business, never as instructions to our systems.

A separate AI reviewer that did not write the extension checks it against your approved design and our standards.

You review the design yourself, as a storyboard and a functional document, before anything is built.

Yes. We research how standard Business Central already handles your need, so your extension fits the way the system works. The research names what is already supported and what genuinely needs extending.

We do not change the standard product.

Typical needs include: stopping shipments to customers over a credit limit; a second approval before a vendor's bank details change; a warning when a warehouse bin is over its weight limit; routing big purchase orders to the right manager; a nightly reminder about service contracts about to end; and a checklist for every new starter.

These are examples of how a need might be put, not finished products. See the examples page for more.

No. You describe what you need in plain words in a short wizard. We fill in the technical details, and you review the result as a storyboard with screens, not as code.

You receive a functional document that describes your extension in plain language.

Only what you need, in plain words. A short wizard asks for your need. It gives examples, lets you attach screenshots and files, and asks which roles will use it and how many people. No technical knowledge is needed.

If you prefer to talk it through, the requirements assistant proposes a solution in plain steps first and asks only what it must.

No. A storyboard is a set of illustrated scenes with an illustrative screen preview, who does what, and the benefit. It shows how the new way of working will feel, so you can judge it before anything is built.

Microsoft Dynamics 365 Business Central is a product of Microsoft. AppoGen is an independent service and is not affiliated with, endorsed by or sponsored by Microsoft.

You read them, correct them and approve them. We ask about anything unclear first. Nothing is designed from them until you approve.

You can comment on any scene or field of the design, and each round gives a new version. Nothing is built until you approve one.

It depends on the size of the extension and on how many review rounds you need. A small change takes less time than a large one, and quick answers from you shorten every stage.

You see the current stage in your account at all times.

Business Dynamics Pro keeps the intellectual property. You receive a licence to use the extension in the environments you name.

You receive the functional document that describes your extension in plain language. If you want the source code, you can buy it for an app after it is delivered, under a separate licence.

We install it for you: first in your sandbox, a safe copy of your system, where you test it, then in production once you accept.

You do not handle any files. Your administrator does a one-time set-up first.

Business Central updates twice a year. We cannot promise that an update will not affect an extension.

If something no longer works, you can request a fix. Without a support plan, a fix is a priced change. Support plans cost a share of the build price each month: Essential (1.25 % of the build price a month, at least USD 49), Standard (1.75 % of the build price a month, at least USD 99) and Priority (2.5 % of the build price a month, at least USD 249).

We do not need your production data. We design and test using the CRONUS sample company that comes with Business Central, never your live records.

All instructions and screenshots in your manual use the CRONUS sample company, never your records.

We store what you send us: your request, any files you attach and the designs we create. Please do not paste passwords or personal data into a request. Which companies process this information and how long we keep it are listed on our privacy page.

We build extensions that add to or change how your system works. We do not change the standard product itself, and we do not build things that bypass its security or licensing.

Some requests are very large or need a closer look. For those we prepare a custom quote, or tell you honestly that another route is better.

Yes. Our partner program is for Business Central practices that keep the customer relationship. It has four tiers: Referral, Reseller, Premier and Elite. Program terms apply. See the partner page at /partners.

Discounts apply to builds and changes, not to subscriptions, support plans or source code.

Every extension comes with a training manual. It covers what the extension does, how to check the install, how to set it up, who needs which permissions, every daily task as a numbered walk-through with screen previews, and every page and action.

It also covers notifications and approvals, reports, troubleshooting, common questions, a glossary and the version history.

It is a single page you can open without an internet connection, and you can also read it in your account.

You can show your client a requirements document to read and approve, and a storyboard of the new way of working. A functional document describes the extension in plain language, step by step. The functional design includes flow maps.

After delivery there is a training manual, an HTML5 page that covers setup, permissions and every daily task, with screen previews.

You pay for each build in two equal parts. You pay 50 % when you accept the quote, and the build starts. You pay the other 50 % when the extension is built and tested, before we install it.

Designing the extension with you comes first and is part of your subscription. The subscription starts with a 14-day trial, so you can see a design and its functional document before you commit.

No. You pay nothing for the build until you have seen the design and accepted a quote.

This is about the build price. The monthly subscription is separate: plans start from USD 49 a month, with a 14-day trial.

Your price depends on how complex your extension is and how many parts we need to design: screens, records, reports, approvals and links to other systems. Simple extensions usually cost USD 2,000 to 5,000, standard ones USD 5,000 to 12,000 and advanced ones USD 12,000 to 20,000. Above USD 20,000, we prepare a custom quote after reviewing the design.

You see the breakdown before you accept.

Yes. A price estimate calculator lets you answer a short list of questions and see an estimate.

It is an estimate, not a quote. The final price comes from your approved design and may be higher or lower. You see the breakdown in plain words before you accept anything.

We recommend a dedicated sandbox with the CRONUS sample company. We install there first so you can test safely, and move to production only after you accept it. We do not need your live data to design or test.

For installation we ask an administrator of your Microsoft environment to give us permission to install extensions on your behalf. This is called delegated admin consent. You stay in control and you decide which environments we may use.

Yes. A change after approval is treated as a change request. We design it with you and price only the difference.

We build from the design you approve. For 30 days after installation we fix anything that does not match it. Our total responsibility never exceeds what you paid for that extension.

Tell us if something is wrong. You test in your sandbox before production, which is the best moment to find problems. After the warranty, you can always request changes, priced on the size of the change.

We build to written coding standards. The extension is tested against the acceptance criteria in your approved design, and what fails is fixed before anything reaches you.

A separate AI reviewer that did not write it checks the work against your approved design and the standards.

A monthly subscription gives you access to design your apps with us, to receive the functional document for each app, and to come back to your released apps and ask for changes, which cost less than starting again. Plans start from USD 49 a month, with a 14-day trial.

The cost of building an app is separate. It is calculated from the size of the approved design and paid in two parts for each build.

If your subscription lapses, the apps you already have keep running. Design and change requests pause until it resumes.

Yes. Open the app in your account, request a change and describe it in plain words. We start from the released version, show you a storyboard of the change and price only the difference.

The new version is installed as an upgrade, in your sandbox first.

We install it for you. This is the standard way, and it is automatic: first in your sandbox and then in production, with the permission you give us.

Downloading the app package is available only to customers who have purchased the source code for that app. You accept the licence terms before you download.