Skip to main content

See it before it is built

Before we build anything, we show you the new way of working as a short storyboard. Here is one for a sample extension.

Sample extension

Credit hold at order release, with approval

When someone releases a sales order that would take a customer over their credit limit, the order waits for a finance manager to approve it.

All names, customers and amounts on this page are made up for illustration.

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
  1. 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.

  2. 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.

  3. 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
  1. Step 4: Visual storyboardRealistic screens you review and comment on.

    We show the new way of working as a storyboard of realistic screens. You review it, comment on any scene and ask for changes until it is right.

  2. 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
  1. Step 6: We build the extensionAI agents code to our written standards.

    AI agents write the extension for Business Central to our written coding standards, and you can follow progress in your account.

  2. Step 7: Automated testingCompiled and tested against your acceptance criteria.

    We compile the extension and run automated tests, planned from the acceptance criteria in your design, and fix what fails before anything reaches you.

  3. Step 8: Quality reviewAn independent reviewer checks code against design.

    A second, independent reviewer checks the code against the design and the standards. People review as well where the risk is higher.

Phase: Deliver
  1. 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.

  2. 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.

The storyboard

Scene 1 of 6

Anna

Sales order processor

Anna finishes a sales order and presses Release, as she does every day.

Benefit: Nothing changes in how Anna works. She does not have to remember to check anything.

Your business system

Sales Order SO-1042

  • Release
  • Post
  • Print

General

Customer
Sample Customer Ltd
Order total
USD 8,400
Status
Open

Scene 2 of 6

Anna

Sales order processor

The extension checks the customer's credit position and sees this order is over the limit.

Benefit: The check happens at the right moment, before anything ships, and Anna sees exactly why the order is waiting.

Your business system

Sales Order SO-1042

  • Release
  • Cancel approval request

This order would take Sample Customer Ltd USD 3,200 over its credit limit. It has been sent to Mark for approval.

General

Credit limit
USD 20,000
Open balance
USD 14,800
With this order
USD 23,200New
Status
Pending approvalNew

Scene 3 of 6

Mark

Finance manager

Mark gets the request with everything he needs to decide in one place.

Benefit: Mark does not have to open three reports or call anyone to understand the situation.

Your business system

Approval request: credit limit exceeded

  • Approve
  • Reject
  • Ask for more information

General

Requested by
Anna
Customer
Sample Customer Ltd
Over the limit by
USD 3,200New
Overdue invoices
None

Scene 4 of 6

Mark

Finance manager

Mark approves and adds a short reason.

Benefit: Every decision is recorded with who made it, when and why.

Your business system

Approve request

  • Confirm
  • Back

Approved. Anna has been told.

General

Decision
ApproveNew
Reason
Customer paid their last invoice early

Scene 5 of 6

Anna

Sales order processor

The order is released on its own and Anna can carry on.

Benefit: No email back and forth. The order moves as soon as the decision is made.

Your business system

Sales Order SO-1042

  • Create warehouse shipment
  • Post

Order released. Approved by Mark.

General

Status
ReleasedNew
Approved by
Mark
Reason
Customer paid their last invoice early

Scene 6 of 6

Priya

Credit controller

Priya opens one list of every order on hold, and who is waiting on whom.

Benefit: Finance sees problems early, instead of finding them after the goods have left.

Your business system

Orders on credit hold

  • Open order
  • Remind approver
  • Export to a spreadsheet

General

Waiting for approval
SO-1042, SO-1047New
Oldest request
Today
Approved this week
SO-1031, SO-1038

Before and after

Today

  1. Anna releases the order. Nothing checks the credit position.

  2. The goods ship.

  3. Later, Finance spots the overdue balance in a report.

  4. Finance phones the customer and emails Sales.

  5. Everyone tries to work out who agreed to what.

With the extension

  1. Anna releases the order as usual.

  2. The extension checks the credit position and holds the order if it is over the limit.

  3. Mark gets one request with the facts on it.

  4. Mark approves or rejects, with a reason.

  5. The order moves on, and the decision is on record.

Fewer hand-offs, no manual checking and no surprises after shipping. Risky orders are caught before they leave, and each decision has a name and a reason attached.

After the first release, the story goes on

An app is not finished when it is delivered. You can come back to the released version and change it, as many times as you need.

  1. Subscribe

    A monthly subscription lets you design, document and change your apps.

  2. Design it with us

    Review the storyboard, comment and approve. You receive the functional document.

  3. We build and test it

    The build is priced from the approved design and tested before it reaches you.

  4. We install it

    We install it for you automatically, first in your sandbox and then in production.

  5. Request a change

    Open the released app, describe what should change and review the new storyboard. We price only the difference.

Click any scene to comment

When we show you your own design, every scene and every field on a screen can take a comment. You can also pick from suggested changes, such as "also tell Finance". Each round of comments gives you a new version to look at. Nothing is built until you approve one.

A functional document, in plain language

You never need technical detail. You review your design as a storyboard and you receive a functional document that describes how your extension works, step by step. The technical details stay on our side.

Tell us what your team needs

It takes a few minutes. You pay nothing for the build until you have seen the design and accepted a quote.