FP&A

Right Tool, Wrong Time: Build vs Buy Software Decisions in Finance

Right Tool, Wrong Time: Build vs Buy Software Decisions in Finance
Key Takeaways
  • Timing stalls more decisions than doubt does: Finance leaders who see clear value in a new tool still pause for budget season, busy calendars and competing projects.
  • Build vs buy software is also a maintenance decision: A workaround that buys another year still has to be maintained, and the people holding it together don't stop while the decision waits.
  • The pain tends to come back on schedule: The next planning cycle, a key person leaving or the current setup finally breaking usually reopens the conversation.
  • Waiting has a cost in team hours: Another year on a workaround or on manual reporting takes hours from the team you already have, and that's the number to weigh against the disruption of moving.

One of my favorite prospects this fall stopped me halfway through a demo to ask whether he should just kick the can down the road. He liked what he was seeing. He wanted to know if he could wait.

I get a version of that question more than any other, and I’ve stopped treating it as an objection. It’s usually the most honest thing anyone says on the call. In finance, most of the build vs buy software decisions I see get stuck on timing: a budget to finish, a busy calendar, or a workaround that’s still holding.

This piece is based on three conversations I had in recent months, with any identifying details removed.

How do finance leaders decide on build vs buy software?

The finance leader who asked about kicking the can saw plenty he wanted. He liked being able to change how the business was structured in the model without rebuilding everything. He liked owning his own data mappings, so a change wouldn’t mean calling in outside help. Headcount forecasting, drill-down and the cash flow forecast all landed, and he called the cash forecast slick.

He also had a workaround. His data team had built something that got him most of what he needed, and he reckoned it could carry him another year or two. He’d been encouraging his own people to evaluate FP&A software vendors before building anything, and he wanted to practice what he preached. So he was weighing build vs buy software, honestly and out loud. Gartner’s research on AI in finance notes that many projects end up as a mix of the two: a platform bought as the foundation, with custom pieces built on top. His data team’s work could stay part of that picture, since Datarails can pull in data from a warehouse they already run.

I respect that question, and I don’t try to talk people out of asking it. What I ask in return is a short set of questions. Who keeps the workaround running, and what happens when that person is busy or leaves? What does a change take when the business adds an entity, a department or a new reporting line? Can finance make that change itself, or does every change go back to the data team? And what is the team putting off while it keeps the workaround alive? A tool your team built is still a tool your team has to keep running.

What makes a company pause a decision it has already made?

Another prospect saw the whole picture a year ago. My colleague Raluca ran a deep dive with them, and they liked what they saw: Excel reports that refresh from connected data, dashboards, drill-downs, and no code to write. Their team was spending its time fighting with the information, and pulling anything remotely was slow.

Then they went quiet. It had been a tough year for the business, and with AI moving as fast as it was, they didn’t want to commit to anything until they’d seen where it went. They stayed on their old reporting tool for another year.

This fall they came back. The biggest pain points hadn’t gone anywhere, the business was in a better spot, and the old tool’s version problems had reached the point where they described it as a do-not-resuscitate situation. The next fiscal plan needed something better, and they knew it.

They’d seen the same product a year earlier. The year in between is what changed their mind.

How do budget season and busy calendars slow down a decision?

The third conversation stalled in the most ordinary way possible.

The value was clear to everyone on the call. They wanted to stop doing manual Excel work, speed up budgeting and turn raw data into board-quality reporting without hours of formatting. They also liked having the process written down in a system, so it wouldn’t depend on a few people who’d eventually move on.

Then summer happened. Their CFO was away for much of it, and a list of other technology projects was competing for the same attention. By the time everyone was back, it was budget season, and they asked to pick things up again in December once the budget was done.

I pointed out, gently, that the budget they were finishing by hand was one of the things they wanted the software for. They laughed. They still waited, and that’s fine. December is a real date.

When is the right time to change how finance reports?

Put those three side by side and a pattern shows up. Nobody doubted the value. What held each of them back was timing: a hard year and the wait to see where AI went, a busy summer and a budget to finish, a workaround that was still just about holding.

So when someone tells me it isn’t the right time, I ask what changes between now and then. The answer is usually one of three things: the next planning cycle, a key person leaving, or the current setup finally breaking. Once we know which, we can work backward and pick a start date that gets them set up before the busy season starts. That only works if you know the lead time, so ask any vendor, us included, how long it takes to get live on your own systems and data before you pick the date.

Can a small team really handle all the reporting?

The question underneath most of these conversations is whether the change is worth the disruption for a team that’s already stretched.

One verified G2 reviewer put it simply: a small team now handles all of their reporting, and they called it a great return on investment. That’s one company’s experience. For a team deciding whether to wait another year, the useful comparison is the hours another year of manual reporting takes from the people you have, set against the effort of moving. The work still has to get done either way.

Where should you start if you’re not sure the timing is right?

Write down what has to be true before you’d make the change, and put a date next to it. If the answer is “after budget season” or “before the next audit,” you already have your timeline. That list is also the first step in a software evaluation process, because it tells you what any tool, or any build, has to deliver and by when.

If you’re weighing now against next year, I’m happy to help you work it out at your own pace. On a Datarails demo, tell us what’s on your calendar for the next twelve months, and we’ll show you what getting started would look like around it. If the answer is “not yet,” you’ll at least know exactly when.

Related Articles

Become a Partner

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails

Drive Business Performance With Datarails