Describe the need. See the design before the build.
Describe what your team needs in plain words. See it as an illustrated storyboard, approve the design, then we build, test and install it, sandbox first.
Start where you are
One process, explained for each role. Pick the one that fits you.
I use Business Central
Say what your team needs in plain words. See it as a storyboard before you pay for the build, then we build, test and install it, sandbox first.
I am a functional consultant
Bring the requirement. We write it down, check standard Business Central first, and give your customer a storyboard to approve before anything is built.
I am a Business Central partner
Add extension delivery to your Business Central practice. You keep the customer relationship.
I am an AL (Business Central language) developer
Start from a written requirement and a design your customer has approved. The customer reviews a storyboard and a functional document, and the technical details stay on our side.
Which of your needs are still waiting?
Needs that wait
A stop on an order, a second approval, a nightly reminder. Which of your team's needs are still waiting for someone to build them?
Code is only one part of an extension
A reliable Business Central extension needs the need understood, the standard product checked, the functionality agreed, the build tested and the users trained. AppoGen takes you through all of it.
Hard to judge from a sentence
A one-line request does not show what you would get or what it would cost. That is why you see the design, and a price breakdown in plain words, before you accept a quote.
How it works
Six steps from a described need to an installed extension. You approve the design, accept the quote and accept the sandbox install before anything goes to production.
Paymentmarks the two moments you pay: 50 % to start the build, 50 % before we install.
Step 1: Describe it
Answer a few plain questions in a short wizard, or talk it through with the requirements assistant. No technical knowledge is needed. We ask about anything unclear. We check how standard Business Central already handles your need. Then we write your needs down for you to read, correct and approve.
Step 2: See it and comment
We show the new way of working as a storyboard: illustrated scenes with an illustrative screen preview. Click any scene to comment. Each round gives a new version, and nothing is built until you approve one.
- Payment 1 of 2 · 50 %
Step 3: Approve and accept the quote
When you approve the design you receive the functional document and a price based on the size of the design. Accept the quote and pay 50 % to start the build.
Step 4: We build, test and review
We build the extension to our written standards and test it against the acceptance criteria in your approved design. A separate AI reviewer that did not write it checks the work. You can follow the current stage in your account.
- Payment 2 of 2 · 50 %
Step 5: Pay the balance, we install it
Pay the remaining 50 %. We install the extension in your sandbox first, where you test it. We install it in production once you accept.
Step 6: Get your training manual
Every extension comes with an HTML5 training manual: setup, permissions, every daily task and troubleshooting, with screen previews.
From your requirement to a working solution
See it before it is built. You have a business problem or requirement. We turn it into a visual storyboard, you review the proposed functionality, and only then do we build, test and deliver the actual extension.
Phase: Understand
Step 1: Your requirementDescribe it in plain words; attach files.
Describe what you need in plain words, or talk it through with the requirements assistant. You can attach screenshots and sample files.
Step 2: Questions and requirements documentWe clarify, you approve a requirements document.
We ask about anything that is unclear, then write your needs down as a requirements document. You read it, correct it and approve it.
Step 3: ResearchWe study how standard Business Central does it.
We research how standard Business Central already handles your need, so your extension fits the way the system works.
Phase: See it
Step 4: Visual storyboardIllustrated scenes you review and comment on.
We show the new way of working as a storyboard of illustrated scenes. You review it and comment on any scene. Each round gives a new version, and nothing is built until you approve one.
Step 5: Your approval and a quoteApprove the design, get a quote, pay the deposit.
When you approve the design you receive the functional document and a price based on the size of the design. You accept the quote and pay 50 % to start the build.
Phase: Build and test
Step 6: We build the extensionBuilt to our written coding standards.
We build the extension for Business Central to our written coding standards, and you can follow progress in your account.
Step 7: Automated testingTested against your acceptance criteria.
We test the extension against the acceptance criteria in your design, and fix what fails before anything reaches you.
Step 8: Quality reviewA separate AI reviewer checks the work.
The work is reviewed by a separate AI reviewer that did not write it, against the design and the standards.
Phase: Deliver
Step 9: Training manual and documentsTraining manual and documents via secure portal.
You get a training manual with screenshots that walks your team through setup and daily use. Your documents are shared through a secure portal with an access code.
Step 10: Installed for youSandbox first, then production, after you accept.
After you pay the remaining 50 % we install the extension in your sandbox. You try it and accept it, and we then install it in production.
Working solution
Tested functionality, installed and ready for your team to use.
What you can ask for
Most requests start as one sentence. These examples show how a customer might put it. They are illustrations, not delivered extensions.
- Stop shipping to customers over their credit limitSalesSee an example
- Ask a second person to approve before a vendor's bank details changeFinanceSee an example
- Warn the team when a bin is loaded past its weight limitWarehouseSee an example
- Send big purchase orders to the right manager before they go outPurchasingSee an example
- Remind us every night about service contracts that are about to endServiceSee an example
- Give every new starter a checklist for their equipment and accessHRSee an example
Why AppoGen
Written standards, reviewed by a separate AI reviewer
Every extension is built to written coding standards. A separate AI reviewer that did not write it checks the work against your approved design and those standards before it reaches you.
See it before you pay for the build
You approve a visual design first. The price is based on that approved design, and you pay 50 % to start the build only after you accept the quote.
We install it for you
We install the extension in your sandbox first, and in production once you accept. You do not handle files. Your administrator does a one-time set-up. After that, we handle the installation as designed, and production waits for your approval.
Tested against your approved design
We test the extension against the acceptance criteria in your approved design and fix what fails before anything reaches you.
A training manual with every extension
Setup, permissions, every daily task and troubleshooting, written for your extension and your team, as a single page you can open offline.
Tell us what your team needs
Describe your need in a short wizard. You pay nothing for the build until you have seen the design and accepted a quote. The subscription, which starts with a 14-day trial, is separate.