Business Central & NAV / Small-business implementation
Business Central implementation for a smaller business — without an oversized project.
A smaller business can benefit from working directly with a senior consultant who understands both the operating processes and the technology. We take on selected Microsoft Dynamics 365 Business Central implementations where the scope is manageable and the priorities are clear, with a practical plan for getting core processes live before expanding the solution.
Fit
What a good fit looks like
Fit is about operational complexity, not company size or user count.
A defined initial scope
A clear view of which processes need to work first.
Accessible decision-makers
The people who own finance and operations decisions can be in the room.
Manageable data
Master data and balances that can be reviewed, cleaned, and loaded within the plan.
A realistic set of integrations
The connections the business genuinely depends on, not every system it has ever used.
Willingness to standardize
Using Business Central's standard processes where they fit, and customizing only where the business truly differs.
Processes
Processes to assess, not a fixed package.
Finance & purchasing
General ledger, dimensions, payables, bank reconciliation, and purchasing — assessed for what the business actually does.
Sales & inventory
Order-to-cash, items and costing, and stock control — scoped to the way the business sells and ships.
Every implementation is scoped around what is needed first and what can sensibly wait.
Right-sized
When a broader team is the right answer.
Smaller does not mean simple. A larger or highly specialized program — multi-entity manufacturing, complex regulatory requirements, many integrations — may need a broader team than a focused engagement provides. In that case we can still deliver an agreed component, such as the integration or migration workstream, alongside the wider effort.
What Integrated IT offers is a right-sized approach: senior involvement, a scope matched to the business, and clear responsibilities. Pricing and delivery commitments follow the agreed scope rather than a published package.
How it runs
How a small-business implementation works
Responsibilities for each step are allocated explicitly at the start, not assumed.
Discovery and scope
What the business needs, in what order, and what is deliberately deferred.
Configuration responsibilities
Who configures what — company setup, posting groups, dimensions, templates.
Data migration
Master data, opening balances, and any agreed history, reconciled before go-live.
Agreed integrations
The connections in scope, built and tested against the systems that matter.
Testing and user preparation
Realistic scenarios worked through by the people who will run them.
Cutover planning
A defined cutover with responsibilities, checks, and what happens the first week.
Questions
Common questions.
Is there a fixed package or price?+
No. The scope is defined around what your business needs first, and pricing follows the agreed scope. A published package would either include things you don't need or leave out things you do.
Is the practice large enough to implement our whole business?+
It depends on complexity, not headcount or revenue. Where the scope is manageable and priorities are clear, yes. Where the program is broader, I'll say so and propose the component we should deliver.
We're not sure BC is the right fit. Can we start with that question?+
Yes. Discovery starts by determining what the business actually needs. If Business Central isn't the right answer for that, you should know before an implementation begins.
Already working with a Microsoft partner or MSP? We can take on an agreed integration, EDI, migration, or remediation workstream alongside your existing team.
Start the conversation
Tell me what needs to connect, migrate, or work better.
Describe the systems involved and what you're trying to accomplish. I review every inquiry personally and will tell you directly whether the project is a fit.
Discuss a small-business implementation