Why Harp & Crown

A practitioner who has owned these systems, not sold them.

Most people advising you on a finance platform are selling you one. We have owned these systems from inside a finance function.

Run the close. Delivered the upgrades. Rebuilt the integrations. Lived with the decisions afterwards. That is a different vantage point from a delivery contract, and it is the one this practice is built around.

This page sets out how the practice works, what it can honestly claim, and what happens after go-live, when most vendors have already moved on to the next sale.

The practice model

Named and practitioner-led, on purpose.

The work is delivered by a practitioner, not routed through a bench of juniors while a partner signs off from a distance.

One accountable name

Every engagement is led personally, start to finish. There is no handover between a salesperson, a scoping consultant and a delivery team who never spoke to each other.

A network, not a bench

Where an engagement needs more hands than one person has, the practice draws on a network of specialists. There is no standing bench, and the site does not imply one.

Capacity is limited on purpose

A single client is not allowed to consume the practice. We will not accept a delivery date we cannot staff, and for a very large programme the honest answer may be a larger firm.

The true number, on request

If you ask how many consultants we have, you get the true number. No plural framing implying a headcount that does not exist.

Finance operations depth

The record behind the recommendation.

Every figure below is delivery, not marketing: work performed inside real finance functions, not case studies written for a pitch deck.

OneStream, over six years

Delivery across FTSE100, private equity portfolio and multinational group environments, including a major version upgrade completed without disrupting a close cycle.

Cloud-to-cloud migration

Database transfer, security reconfiguration and re-pointing of ERP integrations, carried out as a single controlled cutover.

Consolidation and budgeting design

Cube design across fifty and more legal entities, and a SOX-compliant change management module, built and in production.

The integration and engineering layer

SAP, Kerridge, Microsoft Dynamics 365, NetSuite and Redshift, with SQL and VB.Net engineering behind the mappings, not just configuration.

30%Close time reduction, FTSE100 client
50+Legal entities in a single cube design
3,500+Cost centres in one implementation
7,000+Accounts mapped and reconciled

ERP to EPM understanding

The chain runs from the ledger upwards, and we work the whole of it.

Most advisers arrive at the performance management layer and stop. The practice is built to work every stage the chain actually has.

01 · Accounting & ERP

The numbers begin in systems finance may not fully control. See Accounting & ERP Systems.

02 · Integration & Reconciliation

The data arrives but cannot be trusted or tied back until someone builds and proves the mapping. See Finance Systems Integration.

03 · Finance Application Engineering

The application needs logic beyond configuration. See Finance Application Engineering.

04 · OneStream & Anaplan

Finance needs a governed performance management model. See Performance Management.

05 · Support & Optimisation

It works, but ownership and change are becoming fragile. See Application Support & Optimisation.

A source system issue presents as a OneStream issue. A mapping error presents as a reporting error. Working out which layer you are actually in requires someone who has worked in all five.

Ownership after go-live

Go-live is not the finish line.

A platform that works on cutover day and degrades over the following year has not actually been delivered.

Administrator coaching, not dependency

The goal is a finance team that can run and change the platform itself. Coaching is built into delivery rather than sold back later as a support contract.

A defined handover

What the finance team owns after go-live, and what needs specialist support, is agreed before go-live, not discovered during the first live incident.

Bounded, planned support

Where ongoing support is needed, capacity is planned and honestly bounded rather than open-ended. See Application Support & Optimisation.

Release testing that holds

Platform releases and configuration changes are tested against real reconciliation risk, not waved through on a change log.

Still worrying about

Questions we get asked directly.

How big is your firm?

Small, and deliberately so. Harp & Crown is a practitioner-led practice: the work is delivered by a practitioner, drawing on a network of specialists where an engagement needs more capacity than one person has. There is no standing bench and we do not imply one.

That has a real consequence you should weigh. We limit how much of our capacity any single client can take, we will not accept a delivery date we cannot staff, and for a very large programme the right answer may be a larger firm. We will say so.

Are you a OneStream partner?

Not at present. Partner status requires firm-level references that a young practice has to earn first, and we would rather tell you that than let a badge on a website do the talking. What stands behind the work is the delivery record set out above, which is personal and verifiable.

Do you resell Sage, OneStream or Anaplan licences?

No. We are not a reseller of any of the platforms named on this site and take no margin on licences. Our role is implementation, integration, engineering and support, whichever platform you already run or are choosing between.

What happens if a client outgrows the practice's capacity?

We say so before it becomes a problem. Capacity is planned in advance, and where a programme is larger than the practice can honestly staff, the right answer is told to you directly rather than accepted and mismanaged.

Start with the diagnosis, not the platform.

From £5,000, and the output is yours whether or not you go further.

Finance Systems Diagnostic