Skip to content

Three Questions Every CEO Should Be Asking About Their Tech Stack

These will reveal whether your technology is an asset or a liability

Most CEOs can immediately tell you their revenue targets, top three markets and their headcount. Ask them what their tech stack actually costs to run or whether it can support the company in five years and you'll get a long (expensive) pause.

Technology is not an IT problem. It never was. It is a business strategy problem and the CEO is the one accountable for it. Not the CIO or the CFO. You. The moment you handed that decision off entirely to someone else, you stopped steering a key part of your business.

You don't need to know how a server works but you do need to ask the right questions. Three of them, specifically. They're not complicated. And if you can't answer them clearly right now, that tells you something important.

There is a version of technology that actively enables growth. It connects your operations, gives your team real-time data, surfaces problems before they become crises and scales without requiring a project team every time you add a new country, product line or acquisition.

Then there's the other version. The one that works, sort of. The one your team has built workarounds for and where closing the books takes two weeks and a spreadsheet army. The one where you can't easily answer a question like "what are our margins on product line B across the three regions we launched last year?" without someone spending two days pulling reports.

If your tech stack is the second version, it's not helping you grow. Instead, it's holding you in place while your competitors move.

Microsoft Dynamics 365 is built for growth. Not in the marketing brochure sense but in the operational sense. One platform across finance, supply chain, customer relationship management and analytics means your data is not scattered across five systems that were never designed to talk to each other. Your team stops being the integration layer. Your decisions get faster because the information is actually there when you need it.

Ask yourself honestly which version you have. Growth engine or life support.

Nobody wants to ask this question, so nobody does. And then the system fails.

You're not being asked to catastrophize. You're being asked to think about dependency. Modern businesses run on their systems. Every order, every invoice, every compliance report, every customer interaction. If the system that holds all of that together went dark for 72 hours, what would happen?

For companies running on aging on-premise ERP systems, this question is not theoretical. It's a matter of when, not if. Hardware fails. Unsupported software becomes a security risk. The one person who understood how the old customizations worked retires or gets hit by a bus, and suddenly you're looking at a system nobody can fix.

Cloud-based platforms like Microsoft Dynamics 365 eliminate most of that risk. Microsoft runs the infrastructure, security patches happen automatically. There's no single server in a back room somewhere. The system is designed to be available, because Microsoft's business depends on it being available.

But here's what this question is really about. It's about understanding how vulnerable you are right now. If the answer is "a three-day failure would cost us more than we're comfortable with," that is a risk management conversation you should be having at the board level. Not the IT level.

This is the most uncomfortable question of the three, because it's not about your system. It's about your advisors.

A lot of technology decisions get made based on what the vendor wants to sell, what the internal IT team is comfortable maintaining or what the last CEO put in place ten years ago and nobody has questioned since. None of those are good reasons to keep or replace a system. But they're the real reasons behind a surprising number of technology strategies.

If you're running Dynamics 365 or considering it, the partner you choose matters enormously. Most partners will tell you they're the best. Most partners will also quote you a number, start an implementation and then start billing you for every change order when reality turns out to be more complicated than the sales deck implied.

Hoalani Group was built differently. Jesper Kehlet, our founder, was part of the original development team for Axapta, the product that became Microsoft Dynamics. He's not someone who learned this product from a certification course. He helped build it. That means when Hoalani tells you something about what D365 can and can't do, that advice is grounded in decades of real, hard-won knowledge, not a partner playbook.

We operate across seven countries. We have project teams that span time zones, which means your implementation doesn't stop when one office closes. We've seen the failure modes and cleaned up the messes other partners left behind. We know what good looks like, and we know how to get there without pretending it's easier than it is.

Honest advice is the rarest thing in enterprise technology consulting. It's also the most valuable.

Nobody expects you to have all the answers on your tech stack. That's not your job. Your job is to ask the right questions, demand clear answers and hold the right people accountable.

If you can't answer the three questions above with confidence, that's your signal. Not to panic. Not to start a full replacement project on Monday. But to start the conversation.

Technology that can't support your strategy is not neutral. It is a drag. And in a competitive environment, drag costs you market position, margin, talent and time.

We're not here to scare you into a deal. We're here to give you an honest picture of where you stand and a clear path to where you want to go. That's what a real advisory partner does.

Start with a conversation. Not a sales call, not a demo with a script. A conversation with someone who has seen this movie before and will tell you what they actually think.

Reach out to Jesper Kehlet directly for a CEO to CEO conversation. We operate across the US, Spain, Portugal, Ghana and Canada and work with companies wherever they are.

Three questions. Honest answers. That's where it starts.