How to turn “leftover” budget into lasting value


STRATEGY SIGNALS

BY JOSH HULST

How to turn “leftover” budget into lasting value

I’ve been hearing a familiar story lately, and if you’re in a planning role, you probably are too.

After a year of holding back on big investments due to market and technology uncertainty, a lot of teams are finally getting the green light. Budgets that sat untouched are suddenly available, but need to be spent before the year ends.

It’s a good problem to have, but it comes with its own kind of pressure. Leaders are asking not just how fast they can move, but what they can do now that will make the greatest impact.

I wear two hats: Managing Partner of Michigan Software Labs and digital consultant for our clients. With my Managing Partner hat on, I’ll say this bluntly: don’t spend money just because it’s there. If a project isn’t meaningful or strategic, save yourself the trouble and skip it.

But if you do have a narrow window and want to create something that will last, focus your effort on work that will teach you something and/or deliver value quickly.

  • You might run a short product strategy engagement to align stakeholders, research user needs, and define a clear roadmap for future software engineering. This type of work gives leaders confidence in what to build next and why.
  • Or you might launch a first, high-impact feature that simplifies a workflow, automates a manual process, or gives users a measurable improvement without waiting for a full rebuild.

These examples are not another six-week discovery or hundred-page strategy deck, but the kind of work that creates real momentum. Small, intentional starts like these create clarity and traction because they turn “budget to burn” into progress you can point to in January and a foundation you can build on all next year.

So if you have unspent budget and a short runway, ask what will still be creating value six months from now?

That’s the kind of work we love to help teams get off the ground.

I’m setting aside a few 20-minute windows over the next two weeks if you want to compare notes or talk through where a focused start might have the biggest impact.

Talk soon,

Josh

Josh Hulst: Co-founder and partner at Michigan Software Labs | 551 Settlers Dr, Suite 200, Ada, MI 49301

These signals are meant to be shared. If you know someone who’d benefit, invite them to subscribe here.

You can unsubscribe here. To change your email or preferences manage your profile.

Strategy Signals

Strategy Signals is a monthly newsletter for leadership teams who know technology should be driving growth, but aren’t seeing it happen yet. Each issue breaks down the structural reasons progress feels slower than it should and how to change that.

Read more from Strategy Signals

You don't know all the ways your team is using AI. What do you do when your team finds better tools than the ones you approved? The standard response to unauthorized technology use is to shut it down. I’d argue that’s the wrong first move. Sometimes it's willful; someone knows the policy and works around it anyway. More often, it's not. They didn't realize the risk, didn't know a policy existed, or just needed to get something done. Either way, instead of asking "how do we stop this," ask:...

On time, on budget, and still behind. Most executive teams are measuring whether technology gets delivered, not whether it moves the business forward. Organizations often measure technology by activity. How many tickets are closed? How many tools are deployed? How many projects are delivered on time? Yet, none of these metrics answer whether technology is changing what your business is capable of doing. They measure activity, not capacity. Take project delivery, for example. A project...

STRATEGY SIGNALS By Josh Hulst, Michigan Software Labs Does your technology work for you, or against you? If you ask most leadership teams to describe their technology, they'll walk you through a list of tools, such as the CRM they implemented three years ago or an ERP that they inherited from an acquisition. It might be an accurate list, but it's not really the answer I'm looking for. Knowing which tools you have is not the same as knowing what they can support together. For instance, can...