+44 (0) 208 058 7005 What's broken? Talk to us

Start typing to search...

1 Getting Started

Before you spend six figures on planning software, spend two weeks finding out if you should.

Wrong technology choice. Failed implementation. Team that can't absorb the change. The Bolt Blueprint tells you which of these risks apply to you before you find out the expensive way.

From £5,000  |  Typically 2-3 weeks  |  Credited against implementation

The questions that actually matter

The Blueprint doesn't start with technology. It starts with your organisation. Because in well over 200 EPM projects, we've learned that the three most common reasons mid-market implementations fail aren't technology problems. They're scoping problems, integration problems, and change management problems. The Blueprint identifies which of these apply to you.

Is this a technology problem, a process problem, or a people problem?

Sometimes the answer is new software. Sometimes it's fixing your chart of accounts. Sometimes it's hiring an FP&A analyst. The Blueprint tells you which.

If it is technology, which platform fits your situation?

Not which one has the best demo. Which one fits your data complexity, your team's technical appetite, and your actual budget. We've implemented them all and can tell you what the vendor won't.

Can your team realistically absorb this change?

Your FP&A team is already stretched. Your IT team has a backlog. Your CFO has three other priorities. The Blueprint assesses whether your organisation is ready, where internal resistance will come from, and what needs to change first.

What does a realistic timeline look like?

Not the vendor's timeline. Yours. Accounting for your data quality, your team's availability, your budget cycle, and the other projects competing for attention. We've seen enough projects to know what's realistic and what's fantasy.

Where will resistance come from, and how do you design around it?

The budget holder who won't give up their spreadsheet. The IT team that doesn't trust cloud platforms. The board member who got burned by the last software project. We identify the blockers and build the plan around them.

What's the real cost? Not the vendor's number. The actual number.

3-5 year total cost of ownership: licensing, implementation, data migration, training, ongoing admin, change management. The number you can actually take to the board, including the bits vendors conveniently leave out.

The most expensive EPM project is the one you have to do twice

Most EPM projects that fail don't fail because of bad technology. They fail because of poor scoping, underestimated integrations, and teams that weren't ready for the change. These are problems that cost six figures to discover during implementation and five figures to discover before it.

Every month your team spends three days on month-end close instead of one is a month your FP&A analysts aren't doing analysis. Every board question that takes a weekend to answer is a decision made without the scenario your CFO needed. The cost of inaction is real, but the cost of the wrong action is worse.

The Blueprint catches these problems when fixing them costs thousands, not hundreds of thousands.

Two to three weeks. Here's what happens.

Week 1

Discovery

We spend time with your finance team, your IT team, and your leadership. Workshops, system walkthroughs, process mapping. We learn how work actually happens, not how it's supposed to happen. You'll need 2-3 days of stakeholder time across the week.

Week 2

Assessment & Analysis

We review your systems, data flows, and integration points. We map current state against future state. We assess your team's readiness for change. We identify the gaps that matter and the ones that don't.

Week 3

Recommendation & Roadmap

We present findings, platform recommendations, investment sizing, and a prioritised action plan. Built together, in your language, ready for your leadership. You walk away with a document you own, not a deck we own.

Tangible deliverables

Architecture document

Current state and future state, clearly mapped. Systems, data flows, integration points, and the gaps between them.

Risk register

Integration complexity, data readiness, change management risks. Scored and prioritised so you know where to focus.

Platform recommendation

Which platform fits (or whether you need one at all), with specific reasons. Not a feature matrix. A recommendation backed by experience.

Investment sizing

3-5 year TCO including the bits vendors don't mention: data migration, change management, ongoing admin, training refreshers.

Prioritised roadmap

What to do first, second, third. With dependencies mapped and realistic timelines. Ready to execute with or without us.

Readiness assessment

Your team's capacity, skills gaps, and change management needs. Where internal resistance will come from and how to handle it.

This is not a vendor assessment

Vendor assessments tell you which software to buy. The Blueprint tells you whether you should buy software at all, whether your organisation can absorb the change, and what needs to happen before, during, and after implementation to make it stick.

Vendor-neutral

We work across Anaplan, Pigment, Planful, IBM Planning Analytics, and several others. We've recommended against every platform we implement, including recently. Our advice is based on your requirements, not our commercial agreements.

Pattern-matched

Based on well over 200 comparable implementations, not a generic framework. We know what goes wrong at companies your size, in your industry, at your stage. We've seen the patterns and we know the fixes.

Credited against implementation

If you proceed with us, the Blueprint fee is credited against the implementation. You're not paying for a sales exercise. You're paying for a diagnostic that has standalone value either way.

Sometimes the answer is "don't buy software"

About 25% of the time, the Blueprint tells clients they don't need new technology yet. Fix your processes first. Clean your data. Hire that FP&A analyst. That recommendation is worth £5,000 when it saves you six figures.

£5,000. Credited if you proceed.

The scope scales based on complexity: number of systems, stakeholders, entities, and locations. We'll discuss your situation and provide a clear proposal before anything starts. No surprises.

If the Blueprint tells you to proceed with implementation and you choose to work with us, the £5,000 is credited against our fees. You haven't paid for a sales exercise. You've paid for a diagnostic that made the implementation faster and more likely to succeed.

If the Blueprint tells you not to proceed, that £5,000 just saved you six figures and several months. About three quarters of Blueprint clients do proceed with us. Not because they're locked in, but because they trust what we've told them and want the same people doing the work.

Blueprint FAQs

What if the Blueprint tells us we don't need new software?
Then we've saved you six figures and several months of disruption. About 25% of the time, that's exactly what happens. The recommendation might be to fix your data first, restructure your chart of accounts, or hire an FP&A analyst before investing in technology. That's a recommendation worth paying for.
How is this different from a free vendor assessment?
A vendor assessment tells you why their product is the right choice. The Blueprint tells you whether any product is the right choice, and if so, which one. We assess your organisational readiness, internal change capacity, data quality, and process maturity alongside the technology question. Vendors don't do that because it might lead to a "not yet" recommendation.
What does our team need to commit?
About 2-3 days of stakeholder time across the two to three weeks. That typically means a few workshops with finance, a technical session with IT, and a leadership alignment meeting. We do the heavy lifting between sessions. The time investment is modest compared to what implementation demands.
Can we use the Blueprint with a different implementation partner?
Yes. The roadmap is yours to execute however you choose. About 75% of Blueprint clients choose to continue with us, but the document stands on its own. It's written for your organisation, not for us.
We already know we need Anaplan / Pigment / Planful. Do we still need a Blueprint?
Probably, yes. Even when the platform is decided, the Blueprint scopes the implementation properly: what to build first, how to handle data migration, what your team needs to learn, and where the risks sit. Implementations that start without this scoping take longer, cost more, and are more likely to need remediation later. The Blueprint is credited against implementation either way, so the financial argument is straightforward.

Book a 20-minute call to see if the Blueprint is right for your situation

No sales pitch. We'll ask about your situation, your timeline, and your budget. If the Blueprint isn't the right next step, we'll tell you that too.