Pricing
A subscription to design, and a price for each build
You pay a monthly subscription to design, document and change your apps. Each build is priced separately from the size of the approved design. We do not guess a price from a sentence.
What you pay for
Three parts, each explained in plain words.
A monthly subscription
The subscription lets you design your apps with us, get the functional document, and come back to change an app as often as you need. It is how we keep every app ready for the next change.
- Design and review your apps as storyboards.
- Receive the functional document for each app.
- Request changes to released apps, again and again.
- Start with a 14-day trial.
Plans and prices
Plans start from USD 49 a month. A 14-day trial lets you try one design first. If a subscription lapses, the apps you already have keep running; design and change requests pause until it resumes.
A price for each build
When you accept a design, the cost of building it is calculated from its size. Use the calculator below for a first idea. You pay it in two parts, and a later change is priced only on what changes.
Your app, delivered your way
We install every release for you. Downloading the app package is for customers who have purchased the source code.
- We install it for you. We install the app in your sandbox and then in production, automatically, with your permission. You do not handle files.
- Source code, with download. After delivery you can buy the source code for an app, under a separate licence. Only then can you download the app package and install it yourself. Business Dynamics Pro keeps the intellectual property.
How the build price is set
The price comes from the size of the approved design. We count the new and changed screens, the new kinds of records, the reports and a few things that make a job harder, such as approvals, posting and links to other systems. Bigger and more complex designs cost more. You see the breakdown in plain words before you accept.
What is included
- Discovery. We read your request, ask follow-up questions and check what your system already does.
- Design rounds. You review the storyboard, comment, and get a revised version until you approve.
- Testing. We test the extension on a running test system before it reaches you.
- Training manual. A manual that covers setup and every daily task, from A to Z.
- Managed install. We install the extension in your sandbox, then in production, with your permission.
- Functional document. A plain-language document that describes how your extension works, step by step.
Two payments for each build
You pay for each build in two equal parts. Each one unlocks the next stage.
- 1
50 %
50 % to start the build
After you approve the design, sign off the functional design and accept the quote.
We start building.
- 2
50 %
50 % before installation
When the extension is built, tested and ready.
We install it in your environment.
Design comes before the quote
Designing your extension with you is part of your subscription, which starts with a 14-day trial. You only commit to the build when you accept a quote.
Larger jobs get a custom quote
Above USD 20,000 we prepare a custom quote after reviewing the design. We never quietly cap a price.
Support plans after delivery
A support plan keeps a delivered extension working, including after updates to Microsoft Dynamics 365 Business Central. 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).
Warranty
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.
Estimate your price
Answer a few questions in plain terms. Guess if you are not sure. We will refine it when we design your extension.
The questions load as you scroll to them.
- How many new screens do you expect?A screen is a page your team opens, such as a list of items or a form for one record.
- How many existing screens need a change?For example, adding a field or a button to a screen your team already uses.
- How many new kinds of information do you need to keep?For example, a list of notes or a list of approval levels. Each kind of list counts as one.
- How many reports or printouts do you need?A report is a document you print, save as a PDF or send.
- Does someone need to approve something?For example, a manager must say yes before an order moves on.
- Does it change what happens when you post?Posting is when a document, such as an invoice or a shipment, becomes final in your books or stock.
- How many other systems does it need to talk to?For example, a website, a bank, a messaging tool or a file exchange. Use 0 if none.
- How many tasks should run by themselves on a schedule?For example, a check that runs every night without anyone clicking anything.
Estimated price (USD)
From USD 3,750 to USD 5,500
Most likely about USD 4,400.
Based on your answers. A member of our team reviews the final figure.
This is an estimate only. The final price comes from the approved design, and it may be higher or lower than the figure shown here.
How this was worked out
- A new place to store information, such as a list of notes or approvals, with its fields and rules.Table, 1 × 30 points30 pts
- Extra fields added to information the system already stores, such as customers or sales orders.Table extension, 2 × 15 points30 pts
- A new screen people open to view or edit information, such as a list or a detail form.Page (list, card or document), 4 × 25 points100 pts
- New fields or buttons added to a screen that already exists.Page extension, 2 × 12 points24 pts
- The behind-the-scenes rules and calculations that make the screens do their work.Codeunit (business logic), 2 × 30 points60 pts
- A small hook that reacts when something happens in a standard process, for example when an order is released.Event subscriber, 4 × 10 points40 pts
- A named group of access rights that decides who may use the new features.Permission set, 1 × 5 points5 pts
289 points in total. Risk multiplier 1.
- Each new screen counts as one page.
- Each new kind of record counts as one table, one list page and one card page.
- Each changed screen counts as one page extension and one table extension, plus two event subscribers.
- One codeunit (business logic) is added for every two screens, rounded up.
- One permission set is included whenever anything is built.
- Posting together with at least one integration is priced with the higher risk multiplier.
- This is an estimate. The final price is set from the design you approve.