About Middlecut
About Middlecut: keep what matters, cut the rest.
The name comes from distilling. When a spirit is run through a still, the first part off the still and the last part are set aside. What’s kept is the middle cut: the part worth having.
- Heads: Busywork, set aside
- Middle cut: What matters, kept
- Tails: Busywork, set aside
We do the same with business software. Business Central already does a great deal well, so we don’t replace it. We look at a task, set aside the steps, fields and pop-ups that don’t belong to it, and keep the part your team actually needs.
That usually ends up as one screen per task, running inside Business Central, on a desktop or a phone.
How we work
Four habits you’ll notice on a project.
Precise
We name the steps we’re removing.
Every proposal lists the task as it’s done today, click by click, and the version we’ll build. You can check our work against it.
Calm
Small changes, shipped in order.
One screen at a time, tested in a sandbox copy of your Business Central first. Nothing goes live without your say.
Practical
Built for where the work happens.
The receiving dock, the sales counter, the service van. We test on the phones and scanners your team uses, not only on a big monitor.
Thoughtful
We plan for whoever comes after us.
You own the code, and the documentation is written for the next developer, whether that’s us, your partner or someone you hire.
Who we are
Two founders who build, and then support, what they sell.
Middlecut is two people who build and support extensions for Microsoft Dynamics 365 Business Central. The people who scope your screen are the people who write it, and the same people answer when it needs attention after an update.
There’s no hand-off between a sales team and a development team, because there isn’t one of each. You talk to the builders from the first call.
What we build
Control add-ins (custom screens that run inside Business Central) and the AL extensions behind them.
Who we build for
Companies running Business Central, and Business Central partners who need a specialist on a project.
What we look after
The extensions we build, through each twice-yearly Business Central update, on a support plan.
Listen · Refine · Deliver
What each stage leaves in your hands.
Our process has three names. On a project they turn into three things you can hold us to.
After listening: the task on paper
A written record of how the task runs today, written from watching the people who do it. It includes the spreadsheet on the side and the sticky note on the monitor.
After refining: one screen, agreed
A sketch of the task as a single screen, with the steps it drops listed next to the ones it keeps. Nothing Business Central can do is taken away; it only moves out of the way.
After delivery: code you own
The screen running in your Business Central, its source code and the documentation the next developer needs, whoever that turns out to be.
What we won’t do
A few promises, kept by saying no.
Lock you in
The source code and documentation are yours from handover. If you want another developer to take over, they start from the same code and documentation we use.
Rebuild what Business Central already does well
If a standard page works for a task, we’ll tell you to keep it. We only build where the standard screen is costing your team time.
Promise offline
Screens inside Business Central need a connection to save their work. We can design for a weak signal, but a truly offline app is a different kind of project, and we’ll say so up front.
Dress up demo screens as results
The screens on this site are real builds shown with demo data. We won’t quote savings we haven’t measured with you.
Free Business Central UX review
Send us the screen your team hates most.
In 30 minutes we count the steps your team takes today and sketch the same task as one screen, on desktop and phone. You keep the written summary. No slides, no obligation.