What business owners ask before buying operations help

Business owners describe their operations problems vividly and accurately. What stops them from buying help is something else: they cannot picture what they would get, what it would cost in total or whether their team would use it. Most have already tried a fix that failed. Price is rarely the deciding objection.

These findings describe patterns, not rates

This volume draws on the questions hundreds of owners and executives of businesses have asked us, and on the diagnostics we run inside their companies. We looked for what came up again and again: the problems owners describe, the fixes they have already tried, the questions they ask and the objections they raise.

Three limits apply to what follows:

• Every company here chose to talk to an operations partner. That is not a random cross-section of companies.
• We describe how often something comes up in plain terms, such as “most” or “a smaller group”. We do not claim precise rates.
• Names and identifying details are removed from every quote.

The exhibits draw on a published survey of software buyers, cited below. None of them counts our own conversations.

Most owners have already tried a fix and been burned

Before they look for outside help, most owners have tried at least one of four common fixes and been disappointed. Many have tried more than one.

• Buying software. The most common fix. Owners buy project, CRM or field-service tools to fix their operations. One owner told us: “I’ve already spent thousands of dollars on ClickUp… nobody’s using them.”
• Hiring a developer or freelancer, or building it themselves. Nearly as common. Some owners have tried to build their own systems with AI coding tools. One said: “We got burnt by one who said he could deliver but didn’t.”
• Paying a consultant for a report. Less common. One owner described consultants who “promise the world and deliver an atlas”.
• Hiring an operations manager or COO. Some owners have hired, or seriously considered hiring, someone to run operations. One said: “I can pay one person a salary to try to do that and they will likely fail.”

Published survey data points the same way. In Capterra’s survey of US software buyers, 58% regretted at least one purchase made in the previous 12 to 18 months, and 23% had made more than one.¹ Buyers at smaller companies reported less regret than those at larger ones, but still about half.

0%20%40%60%80%

51%

67%

66%

5 to 249 staff250 to 999 staff1,000 or more staff

About half of small-company software buyers regret a recent purchase

Company size	Buyers with regret
5 to 249 staff	51
250 to 999 staff	67
1,000 or more staff	66

Source: Capterra 2024 Tech Trends Survey, 700 US buyers, July 2023¹

Our reading of the common thread is sequence. Each fix started with a solution before anyone had mapped how the work actually moved.

Doing nothing is the default, and owners pay for it in their own hours

The fifth option, absorbing the work themselves, is where nearly every owner starts. Owners describe its cost in evenings, weekends and lost sleep, and in the senior people who spend their weeks holding the operation together.

The words owners use are consistent: “the business depends on me”, “falls through the cracks”, “nothing closes the loop”, “triple entry”, “duct-taped tools”. When they describe what they want, the words are just as plain: a clear picture of where every job is, one system the team actually uses, and “someone who sticks around and drives it”. Owners almost never use vendor terms such as “fragmented tech stack” or “operational bandwidth”.

Owners ask about what happens after the first payment

Owners rarely ask how the work will be done. They ask what they will get, what it will cost and what will happen to the tools they already have.

• The most common question is what happens after the initial review, and what the whole engagement costs.
• Most owners blur the review, the prototype and the build together, and need them separated.
• Most also struggle to picture the product. They try words such as “platform” and “program” before settling on one.
• Many ask whether a new system would replace their current tools or sit alongside them, and come back to the question more than once.
• Often, owners want a written total-investment figure they can share, and ask for references or comparable clients.
• A recurring request is to see a real system from a business like theirs.
• A smaller group asks security and technical questions about hosting, data agreements and how the AI components are built.

The strongest reactions come when an owner sees a prototype of their own business. One owner’s response was short: “This is the right direction.” The weakest conversations are the ones where nothing is shown.

Price is rarely the deciding objection

Price or budget seldom decides whether an owner goes ahead. Many tell us outright that money is not the issue. One said: “Time is more valuable than the money.” Another said: “We have money… I want to understand what we’re getting.”

The survey data supports the same reading. Among US buyers who regretted a software purchase, more blamed a poor handoff from the sales team to the implementation team than blamed a higher-than-expected cost.¹

1. Sales-to-implementation handoff48%
2. Expectations poorly managed39%
3. Cost higher than expected35%
4. Hard to onboard and train users34%

Buyers who regret software blame the handoff to implementation more often than the price

Cause	Share citing it
Sales-to-implementation handoff	48
Expectations poorly managed	39
Cost higher than expected	35
Hard to onboard and train users	34

Source: Capterra 2024 Tech Trends Survey¹

Note: Shares add to more than 100% because buyers could cite several causes.

The objections that recur are about trust and decision-making:

• Most have been burned by a previous tool, freelancer or consultant.
• Many need a partner, a board or another executive to agree before going ahead.
• Often, owners are comparing several providers at once.
• Some raise distance and trust. One put it this way: “other side of the world and I’ve never met you”.

More than once, an owner has heard an optional monthly fee as a standard cost and decided against going ahead on that alone. An unclear total does more damage than a high one.

Four written answers separate a provider worth hiring from a promise

Each finding converts into a question you can put to any provider before you sign. A provider worth hiring can answer all four in writing.

The worry	The question to ask before you sign
What will I actually get?	What will I hold after the first phase, and do I keep it if I stop?
What will it cost in total?	What is the total cost path, with optional items labeled as optional?
Will it work for a company like mine?	Can I see a real system from a business like mine?
Will my team use it?	How is my team involved before launch, and who stays until they use it?

Source: Verticulate, from the questions owners and executives ask us

The questions apply to each of the four fixes owners have already tried: software, a developer, a consultant and an operations hire. A vendor should say who sets the tool up and who trains the team. A consultant should say what you hold when the report is delivered. A new hire should know which process they own in their first months.

How we engage sets out our own answers: every stage, what you hold at each one and which parts are optional. Volume 2, State of Operations 2027, moves from what owners ask to how their operations actually run. It is in progress and has no results yet.