middlecut
Free UX reviewFree review

For Business Central partners

Your customer, your brand. We build the hard screen.

Overflow and specialist development for Business Central partners. We build control add-ins and AL extensions under your name, deliver them into your repository and never contact your customer unless you ask us to.

Talk partner terms How an engagement works

77%

of Business Central partners say a lack of skilled professionals is holding them back.

Source: Microsoft Partner blog, “Reskill”

55,000+

Business Central online customers in April 2026, up from 45,000 a year earlier.

Source: Microsoft, Directions NA 2026, via yzhums milestone tracker

2029

is when updates for Dynamics GP end, so migrations, and the custom screens they need, will keep arriving.

Source: Forvis Mazars, Encore

The gap partners describe

More Business Central work than people to build it.

Control add-ins are the hardest part of that backlog to staff. They need AL, the language Business Central extensions are written in, for the Business Central side and JavaScript, HTML and CSS for the screen itself. Many partner developers came up through C/AL and AL, so the front-end half often has nobody to take it.

That’s the half we specialize in. We can take the whole build, or just the screen while your team keeps the AL.

The offer

Built to make you look good, then stay out of the way.

White-label or co-branded

Under your brand by default. If it helps the sale, we can be introduced as your add-in team. Either way you stay customer-facing and own the relationship.

NDA and non-solicit, by default

We sign your NDA before the brief, and a non-solicit for your customers and your staff. We don’t sell to your accounts directly.

Your repo, your pipelines, your prefix

Code goes into your repository and through your build pipelines, using your object ranges, naming prefix and code-analysis rules.

Fixed quotes, fast

Send a complete brief and you get a fixed quote within 48 hours, so you can price the work to your customer while the conversation is still warm. Partner rates on request.

How an engagement works

From brief to your pipeline in five steps.

You decide how close we get to the customer. You can keep us one step back and forward our demos yourself.

  1. Paperwork first

    NDA and non-solicit signed before you share anything about the customer.

  2. You send the brief

    The workflow, the users, the Business Central version and any existing extensions. Screenshots help.

  3. Fixed quote within 48 hours

    Scope, price and timeline in writing, so you can mark it up and send it on.

  4. Build with regular demos

    Short demos you can show your customer as your own. Questions come to you, not to them.

  5. Handover into your repo

    Clean code, tests and documentation, ready for your team to deploy and support. We can stay on for upgrades if you want us to.

What you get

Work your team can own the day it lands.

  • A control add-in and the AL that drives it, or just the add-in if your team writes the AL
  • Extensions only: no changes to Microsoft’s base code, so the work survives release waves
  • Code that passes your code-analysis rules, with your prefix and object ranges
  • Test codeunits for the business logic, and screens checked on desktop and on a phone
  • Documentation your consultants can hand to the customer under your name
  • Intellectual property assigned to you or your customer, as your contract requires

Partner terms

Send us the screen nobody on your bench wants to build.

Tell us about your team and the kind of work you’d send. We’ll come back with partner terms.

Talk partner terms See what we’ve built