Keystone · Independent consultancy

The piece that holds it all together.

Finance, organisations and information systems only hold together when aligned. Keystone works at the interface between Executive Management, business teams and IT, to transform without breaking what works.

01
Approach

Why Keystone

A keystone is invisible. It carries nothing on its own. But without it, the arch collapses.

That is Keystone's role: the central piece that holds finance, business and systems together.

A simple conviction: a tool only creates value if it fits the organisation and the processes that carry it. Finance, ERP, transformation, project governance. Keystone works across these areas depending on the scope of the engagement, often on several at once.
02
Expertise

Five fields, one thread

01

Finance & management control

Structuring financial steering, improving forecast reliability, decision reporting and steering indicators.

02

ERP & business systems

Deployment, stabilisation and evolution of industrial and real-estate ERPs. Functional configuration, testing, data migration.

03

Organisation & processes

Harmonising Finance and Project processes, structuring functions, digitising operational workflows.

04

Operational transformation

Change management, transforming functions amid reorganisation and international growth.

05

PMO & project governance

Setting up project governance, portfolio steering, resource allocation, risk management.

The thread

The interface
Business · IT · Management

What ties everything above together. Translating business needs into an IT roadmap, and the IT roadmap into value for management.

03
Engagements

Where Keystone steps in

Six types of engagement, from a short diagnostic to interim management. For each, the right profile is brought in depending on scope, stakes and duration.

Engagement · 01

International multi-site ERP deployment

Does this sound familiar?
  • You are launching a multi-site ERP project and lack an independent lead between management, business and integrator
  • The functional scope is drifting, scoping workshops go in circles
  • Data migration is stalling, the legacy system is fragmented
  • Go-live is approaching and acceptance testing isn't credible
  • Group IT and local sites don't speak the same language
Engagement · 02

Finance IS audit and transformation roadmap

Does this sound familiar?
  • You sense your Finance IS no longer fits but don't know where to start
  • Tools have piled up project after project with no master plan
  • Management wants a business case to decide on a Finance IS investment
  • You want to compare several roadmaps before deciding
  • You need an independent diagnostic to defend a transformation budget
Engagement · 03

Critical ERP stabilisation after a crisis

Does this sound familiar?
  • Your ERP go-live went wrong and critical operations are at risk
  • Users are losing trust and workarounds are multiplying
  • The project has burned its budget and the sponsor has moved on
  • You must choose between stabilising the existing system or replacing some modules
  • The relationship between business and IT has soured, no one talks anymore
Engagement · 04

Finance function transformation

Does this sound familiar?
  • Your Finance department works in silos and information no longer flows up
  • Budget cycles are manual and deadlines are slipping
  • You want to create an internal control or project controlling function
  • Reporting is produced but no one uses it to decide
  • A new ERP requires redesigning the Finance processes
Engagement · 05

Interim management · Finance & Business Tools

Does this sound familiar?
  • Your CFO is leaving with no successor and the role must be held
  • A transformation project needs a full-time cross-functional lead for several months
  • No one on the executive committee owns business-tools governance
  • You need a steady presence on the executive committee to champion Finance and IT
  • A Finance leader must be found without losing momentum
Engagement · 06

Project governance and PMO for large groups

Does this sound familiar?
  • Your IT portfolio has grown dense and no one has the full picture
  • Project trade-offs happen with no framework, driven by sponsor influence
  • The IT budget isn't tied to a portfolio strategy
  • You want to set up a PMO without drowning in bureaucracy
  • Project risks surface only once they've become problems
Keystone method

The process before the tool

An ERP project that starts with the tool starts in the wrong place. You start from the process, test it against reality, and the need comes out of that. Eight domains mapped, from sales to close, as objective trees.

See the method →
SalesBills of materialsPurchasingDownstream purchasingTime trackingBillingAccounting & bankingFinancial control
04
Applications

Tools, not slides

Applications built by Keystone, available as a local prototype to explore how they work. Each tool adapts to the needs, processes and ways of working of the company. Onboarding and rollout are delivered as a Keystone engagement.

Other applications

Bespoke

Not every business process is covered by an ERP. Some are too specific, others fall between existing tools. Keystone builds dedicated applications for these process gaps, starting from the need rather than from a technical building block.

The engagement covers the whole path: defining the right tool, building it, and delivering a prototype tailored to your context.

01Scoping
02Design
03Build
04Prototype
Who runs Keystone

Jean-Christophe Vermeersch

Finance and transformation leadership, from the industrial floor to large groups. Today, independent consulting through Keystone.

View the background →
Contact

Let's talk about your arch.

contact@key-stone.fr
Write via the form →
Phone
+33 6 80 34 66 50
Locations
Bordeaux / Paris · International mobility
Working languages
French · English · Italian