THE PRINCIPLES BEHIND NAV2BC
BUILT FROM EXPERIENCE.DEFINED BY INDEPENDENCE.
Technology built on experience. Relationships built on trust.
Deep technical understanding helps us recognise risks, make informed decisions and deliver solutions that remain maintainable.
Independent thinking means evaluating the options on their merits and recommending what genuinely serves the customer, even when the answer is less convenient.
Trust is built through clear communication, consistent delivery and taking responsibility for outcomes. It should never depend on making a customer dependent.
Customers should control their systems, understand their options and remain free to choose their technology partner. Our work should strengthen that freedom.
Our value is not measured by how dependent customers become. It is measured by the confidence and freedom they gain.
WHERE IT STARTEDCOPENHAGEN. 2004.
Understanding how an application is designed, developed, maintained and improved gives technical decisions a stronger foundation.
Working close to the product encouraged a systems perspective: understanding how business logic, data and application components fit together.
Exposure to structured development methodology showed why testing, release management, support and long-term maintainability belong to the same responsibility.
That experience shaped our technical standards and the way we approach development and independent consultancy. It helped define the direction that NAV2BC follows today.
The journey began in Copenhagen in 2004, with direct exposure to the methodology behind Microsoft Dynamics NAV development.
That experience shaped how we understand software engineering, application architecture, releases and long-term responsibility. It also helped define the independent direction that NAV2BC follows today.
THE EXPERIENCEMORE THAN TWO DECADES INSIDE NAV.
Experience rooted in product development and the application foundations of NAV and Business Central.
Experience across generations of NAV and Business Central, including upgrades and complex projects.
Experience connecting business systems and interfaces in real customer environments.
Working inside business-critical environments taught us to distinguish genuine complexity from complexity that should never have been passed on to the customer.
From product development to business-critical environments, the experience has crossed organisations, countries and generations of NAV and Business Central.
It taught us to respect the technology ›› and to recognise the difference between genuine complexity and complexity that should never have been passed on to the customer.
THE TURNING POINTI HAD SEEN ENOUGH.
Knowledge became concentrated outside the customer’s organisation.
Technical decisions became difficult to challenge, and changing direction became harder.
Costs increased while transparency declined.
Sometimes the cause was poor decisions, weak leadership or misaligned commercial incentives. Whatever the cause, the customer carried the consequences.
Over the years, one thing became increasingly difficult to ignore: customer frustration.
Often the problem was not NAV or Business Central itself, but what happened around it. Knowledge became concentrated outside the customer’s organisation. Technical decisions became difficult to challenge. Costs increased while transparency declined. Changing direction became harder.
Sometimes that came from poor decisions, sometimes from weak leadership, and sometimes from commercial incentives that did not align with the customer’s interests. Whatever the cause, the customer carried the consequences.
A SIMPLE PRINCIPLEDEPENDENCY SHOULD NEVER BE THE BUSINESS MODEL.
A signed contract should be the beginning of responsibility, not an opportunity to gain leverage over a customer.
The deeper a business system becomes embedded in an organisation, the greater the responsibility of those trusted to develop and support it. Customers should gain understanding of their systems.
Good technical work should leave customers with more options and freedom to choose their direction.
Good technical work should leave the customer with more control, not less.
A signed contract should be the beginning of responsibility ›› not an opportunity to gain leverage over a customer.
The deeper a business system becomes embedded in an organisation, the greater the responsibility of those trusted to develop and support it.
Good technical work should leave the customer with more understanding, more options and more control ›› not less.
THE CUSTOMERTHEIR SYSTEM. THEIR BUSINESS. THEIR DECISION.
Listen first. Understand what the customer actually needs before proposing a solution.
Explain the options. Customers deserve to know what is being built and why it matters.
Challenge a requirement when there is a genuine technical reason to challenge it.
Be clear about cost, risk and consequences, including what the customer is paying for.
Listen first. Explain the options. Challenge a requirement when there is a genuine technical reason to challenge it. Be clear about cost, risk and consequences.
Customers do not need to become developers. But they deserve to know what is being built, why it matters and what they are paying for.
INDEPENDENCESOMETIMES YOU HAVE TO BE WILLING TO SAY NO.
Asking difficult questions can make people uncomfortable, especially when established decisions or interests are challenged.
Doing the right thing is not always the commercially convenient thing. Technical consequences must come first.
NAV2BC was created around the freedom to apply independent technical judgement and speak plainly when something does not make sense.
Independent judgement protects the customer’s interests when commercial convenience points elsewhere.
Doing the right thing is not always the commercially convenient thing. Asking difficult questions can make someone uncomfortable ›› particularly when established decisions or interests are being challenged.
NAV2BC was created around the freedom to apply independent technical judgement and speak plainly when something does not make sense.
WHAT WE BELIEVETRUST SHOULD COME FROM THE FREEDOM TO LEAVE AND THE REASONS TO STAY.
Customers should have the freedom to leave. Technical or commercial dependency is not the foundation of a strong relationship.
We would rather be chosen because our work is good and our reasoning is clear. Those are reasons to stay.
A relationship built on confidence and earned trust is stronger than one maintained by dependency.
We would rather be chosen because our work is good, our reasoning is clear and our customers trust us.
A relationship built on confidence is stronger than one maintained by technical or commercial dependency.
WHAT COMES NEXTEXPERIENCE BUILT THE FOUNDATION. THE FUTURE IS THE PURPOSE.
NAV2BC begins with decades of experience, but it is not intended to live in the past.
The ambition includes developing the next generation of NAV and Business Central professionals.
Practical customer knowledge must remain central to the work and relationships we build.
The future needs sound technical judgement, architecture and an internationally minded approach.
Pass experience forward without losing the principles that made NAV2BC necessary.
NAV2BC begins with decades of experience, but it is not intended to live in the past.
The ambition is to build something technically respected, internationally minded and capable of developing the next generation of NAV and Business Central professionals ›› without losing the principles that made NAV2BC necessary.
Built from experience. Driven by independence. Focused on the customer.
LIFE’S TOO SHORT FOR CORPORATE NONSENSE.
And the NAV Universe is too big to explore alone.
COME SAY HELLO