Margin · Programmes · Investment returns

The numbers add up. The business doesn’t.

We establish where the numbers management relies on diverge from operational reality, and what that means financially.

Which number would you least like to defend?

Reconciliation · One number

Illustrative example
Reported margin, key-account segment
18.0%
Customers in CRM / ERP / contracts
412 / 389 / 371
Indexation agreed, not invoiced
27 contracts
Specialist hours with no customer
31%
Margin, traced
14.1% – 21.3%
Lower bound: the segment carries its share of the specialist hours booked to no customer. Upper bound: the agreed indexation is billed. Which customers belong to the segment moves both. Three open choices, about seven points apart.

Why it matters

Revenue can grow while margin shrinks.

Unbilled work, misallocated costs and investments that fail to reduce work can all contribute. AtlasVertex establishes where the gap comes from before you decide what to cut, change or fund.

Where we start

We start where a decision is about to be made on a number nobody has checked.

We never presume the cause. Each engagement starts from a discrepancy you can already see, and establishes where it comes from.

Margin and revenue leakage

Revenue grows, margin does not. Before you cut, establish where the gap comes from.

When
A margin plan, a budget review, a forecast shortfall
We look at
Contract terms never billed, such as indexation and extra work. Specialist and project costs not linked to the customers who cause them.
You get
Where margin leaks, how much, and which customers and contracts to look at first

Programme and business-case risk

The money is committed. Does the business case still hold before the next tranche?

When
A programme behind plan, a funding tranche, an investment approval
We look at
The capacity, dependencies and assumptions the benefits rely on, including the external specialists on the critical path
You get
Which assumptions no longer hold, what delay costs, and the decisions to take now

AI and technology returns

Which investments reduce the work they were meant to, and which only add cost?

When
A review of the AI or technology portfolio, next year’s budget
We look at
Claimed benefits traced to actual hours, resources and cost, before and after
You get
What to scale, what to stop, and the evidence for each

Point of view

The tech moved. The company didn’t.

Companies add software, data, automation and AI while the underlying processes and responsibilities remain unchanged. Existing tools overlap, data remains unreliable, and expected benefits fail to materialise.

Sometimes new technology is the answer. Sometimes the answer is to fix what already exists. We establish what needs to change before deciding what to buy or build.

Method

Four views of the same number, side by side.

Most numbers are precise and still uncertain. We put the four versions next to each other and show where they part ways.

You do not get a new number. You get a range, the evidence behind every finding, and a short list of decisions with an owner for each. Your finance team stays the owner of the number.

Believed

What management assumes

The number as reported, and the story told about it.

Recorded

What the systems say

Where CRM, ERP, billing, HR and procurement disagree.

Actual

How the work really runs

Who does the work, for which customer or programme, at what cost.

Agreed

What has been decided

Which definitions are settled, and which have simply grown over time.

Engagement

Diagnose first. Change what matters. Prove the result.

Where the evidence justifies it, we work with your team to implement the necessary commercial, process or technology change. We then return to the original measure to establish whether it delivered the intended outcome.

  1. 01 · Where every engagement starts

    Scan

    One number, decision or programme. Fixed scope, fixed fee. You get the gap, its evidenced drivers, the economic consequences, the decisions required with an owner for each, and the limits of the evidence.

  2. 02 · Only if justified

    Build or remediate

    The specific change that addresses the finding: a commercial or process change, a data fix, an architecture, an integration, automation or an AI-enabled solution. Scoped and priced separately, with acceptance criteria tied to the business problem.

  3. 03 · After the change

    Verify

    We return to the original measure and establish whether it moved, separating realised value from expected benefit. If you keep us on, we repeat this each quarter.

How we contract the work

  • Defined scope. Each engagement has clear deliverables; implementation is scoped separately.
  • Business-linked acceptance. Every build addresses an identified problem with agreed acceptance criteria.
  • Verified outcomes. Technical completion is not counted as economic benefit. We return to the original measure, stating what changed and what remains uncertain.

Your data stays in your environment, under your security model.

About

Independent by design. Accountable to the evidence.

We don’t replace your advisers. We test the assumptions their recommendations depend on.

AtlasVertex exists to answer a question that often stays open, even after the strategy is agreed, the experts consulted and the investment approved: does the evidence from the business support the assumptions behind the decision?

The result is a clearer basis for deciding what to keep, change, stop or fund, before the next decision commits more money, time or capacity.

Commercial and operational

Fifteen years inside enterprise software companies

How technology is sold, bought and implemented, and what happens to the business case once the contract is signed.

Data and architecture

More than two decades in data and analytics

Microsoft Data Platform MVP, Microsoft Certified Trainer and Microsoft Fabric specialist, across real-time intelligence, analytics engineering and data architecture. It shows how information is structured across systems, where definitions diverge, and what the evidence can and cannot establish.

Executive and investment

CIO and private-equity operating experience

Connects each change to executive priorities, operating models and investment decisions, so that a technically sound build also solves the problem that justified it.

Contact

Which number would you least like to defend?

Start with one consequential number. We will discuss what it represents, what evidence exists, and whether there is a case for a focused diagnostic.

Five quick questions, under two minutes.

Privacy

Privacy notice

Last updated: 16 October 2026

This notice explains what personal data is processed when you visit this website or contact us, why, and what your rights are. We keep it short because we collect very little.

Who is responsible

The controller is AtlasVertex. For any privacy question or request, email info@atlasvertex.io.

No cookies, no tracking

This website sets no cookies and uses no analytics, tracking pixels, advertising tools or embedded third-party content. The fonts are stored on our own server, so your browser does not contact Google or any other provider to load them. Because nothing is stored on your device, there is no cookie banner.

Server logs (hosting)

The site is hosted by Hostinger. Like every web server, it records technical log data when you visit: your IP address, the date and time, and the page requested. This is used only to operate the site and keep it secure. The legal basis is our legitimate interest in a working, secure website (Art. 6(1)(f) GDPR). Logs are kept only for the limited period set by our hosting provider, and then deleted automatically.

When you use our contact form

The “Discuss a number” buttons open a short form hosted by Tally, a Belgian company that stores form data in the EU and acts as our processor. We receive what you enter (your answers, name, role and work email) to reply to you and, if it leads to one, for the follow-up business relationship. The legal basis is the same as for email, below. Tally’s own privacy notice applies to its form page.

When you open the form from this website, the link also passes three details that are stored with your submission only: any campaign tag in the address you arrived on (such as utm_source), the website that referred you, and which button you used. We use this only to understand how people find us. It is not combined with other data and no cookies are set on this website for it.

When you email us

If you email us, we process your name, email address and the content of your message to reply and, if it leads to one, for the follow-up business relationship. The legal basis is taking steps at your request before a possible contract (Art. 6(1)(b) GDPR) and our legitimate interest in answering business enquiries (Art. 6(1)(f) GDPR).

Our email runs on Google Workspace. Google acts as our processor. Where data is transferred outside the EU, this is covered by the EU standard contractual clauses and the EU–US Data Privacy Framework. We keep email correspondence for as long as needed to handle your enquiry and any business relationship that follows, and no longer than the law requires.

What we never do

We do not sell your data and do not share it with anyone for marketing. We do not profile visitors.

Your rights

You have the right to access the personal data we hold about you, and to ask us to rectify or erase it, to restrict its processing, to object to processing based on legitimate interest, and to receive your data in a portable format. Email info@atlasvertex.io and we will respond within one month.

You also have the right to lodge a complaint with your national data protection authority. In the Netherlands this is the Autoriteit Persoonsgegevens.

Changes

If the way we handle data changes, for example if we add cookieless analytics, we will update this notice and the date above.

Back to top