About
An independent BC developer.
I’m a contract software developer specialising in Microsoft Dynamics 365 Business Central. I started with Navision Financials 2.0 back in 1999 — just in time for the Y2K scare — and I’ve been in and around the platform ever since.
I work with two kinds of client. End-users: companies running Business Central in-house who want help with their implementation without hiring a full-time developer for it. And partners: Microsoft vendors and BC consultancies who need short-term resource when projects stack up.
I keep things small and straightforward. Short-ish engagements, clear scope, written notes as we go, and work that someone else can pick up after I’ve gone.
A narrow stack, on purpose.
Business Central is plenty to keep one developer busy. I don’t pretend to be a full-stack generalist.
- Core AL · modern Business CentralExtensions, events, permission sets, translations — the day-to-day development work.
- Reports Report objects · Word layoutsThe invoice, the statement, the picking slip that has to look just so.
- Tooling Azure DevOps · GitHubSource control, pull requests, the basics done properly.
- Integration Web services · REST · ODataThe usual ways BC talks to the things around it.
- Adjacent SQL Server · PowerShellEnough to be useful day-to-day.
A handful of principles.
Straight answers
If a thing is a bad idea, I’ll say so — politely, privately, with a better option where I have one.
Write it down
Decisions captured, handovers written, commit messages explained. You should be able to replace me tomorrow.
One person · one invoice
No junior hidden in the margins. You get me, for the hours we agreed, at the rate we agreed.
Finish the thing
Closing tickets, tidying the sandbox, writing the README. The unglamorous 10%.
The shortest route is email.
A sentence or two about what you’re working on and roughly when you’d like to start is plenty. I reply within a business day.