MENU

Chapter 16

Working With Outside Help

At some point, you may need help. The problems you have identified may require expertise you do not have, time you cannot spare, or capabilities that would take too long to develop internally.

Outside help can accelerate progress significantly. It can also waste money, create new dependencies, and leave you worse off than before. The difference lies in how the engagement is structured and how well you understand what you are buying.

When to Do It Yourself

Not every problem requires outside help. Documenting a process, choosing a standard tool, or organizing information that is already well-understood are tasks that can often be handled internally. But when the problem involves designing systems, building something custom, or changing how the business fundamentally operates, the cost of learning through trial and error often exceeds the cost of working with someone who has done it before.

When to Get Help

Outside help makes sense when the problem requires specialized expertise that would take too long to develop. If solving the problem requires skills your team does not have and will not need again, hiring that expertise is more efficient than building it.

Speed is another reason. A well-scoped project with clear deliverables is a good candidate for outside help. The outsider can focus entirely on the project while your team continues normal operations.

Perspective is a third. Someone who is not embedded in your daily operations may see patterns you have become blind to. They can ask questions that seem obvious but have never been asked, and challenge assumptions that have gone unexamined.

There is also a structural reason. Some businesses reach a point where standard tools no longer fit how they operate, but enterprise-grade solutions are designed for organizations much larger and more complex. The business needs something custom, but the providers who build custom systems often price and scope their work for companies with dedicated IT departments and six-figure budgets. If your business is in this middle ground, finding a provider who understands small business constraints and can build solutions at an appropriate scale is not a luxury. It is the difference between staying stuck and moving forward.

How to Evaluate Vendors and Agencies

If you decide to seek outside help, the challenge becomes finding help that will actually help. The market for business services is full of providers who are better at selling than delivering. A few principles can improve your odds.

The first thing to look for is specificity. A good provider will ask detailed questions about your situation before proposing a solution. They will want to understand the problem, not just sell their standard offering. Vague promises and generic proposals are warning signs. If a provider claims their solution will work for any business without understanding yours, they are selling a product, not solving your problem.

Transparency about process and pricing matters equally. A trustworthy provider will explain how they work, what they will deliver, and what it will cost. They will not hide behind proprietary methodologies or resist questions about their approach. If you cannot understand what you are buying, you cannot evaluate whether it is worth the price.

Evidence of similar work is valuable. Past experience with businesses like yours reduces risk. Ask for references and actually contact them. Ask what went well, what went poorly, and whether they would hire the provider again. The answers are more informative than any sales presentation.

Finally, consider alignment of incentives. Some business models create conflicts of interest. A provider who sells software has an incentive to recommend software whether or not it is needed. A provider who locks you into long contracts has an incentive to make switching difficult. Understand how the provider makes money and consider how that might affect their recommendations.

Red Flags

Certain patterns in proposals and engagements should raise concern.

Vague scope is the most common. If the proposal does not clearly define what will be delivered, when, and at what cost, disagreements are inevitable. Vague scope gives the provider room to manipulate: claiming something is out of scope when you reasonably expected it to be included, or charging extra for work you assumed was part of the agreement.

Long contracts with difficult exit terms are another. A provider confident in their value does not need to lock you in. Long contracts protect the provider from the consequences of poor performance. If you cannot leave, they have less incentive to keep you satisfied.

Proprietary processes that you cannot understand or replicate should raise concern. If the provider’s approach is a black box, you become dependent on them to maintain or modify what they build. This may be intentional. A provider who creates dependency ensures future revenue at your expense.

The same applies to resistance to transparency. If a provider will not explain how they work, will not share documentation, or will not give you access to your own data, they are prioritizing their control over your interests. You should own what you pay for and understand how it works.

Finally, pressure to decide quickly. Legitimate opportunities do not expire overnight. Pressure to commit before you have had time to evaluate is a sales tactic, not a sign of value.

Do Not Become the Integration Layer

An earlier chapter described how business owners often become the human integration layer, manually connecting tools and systems that do not talk to each other. The same pattern can emerge with outside help.

When you hire multiple providers who do not coordinate with each other, you become the connection point. Information must flow through you. Decisions require your translation between different specialists. Problems that fall between areas of responsibility land on your desk. The providers do their work, but the work of making their outputs fit together becomes yours.

This is exhausting and easy to overlook. It is also avoidable. When engaging outside help, consider who is responsible for integration. If the answer is you, reconsider the structure of the engagement. A single provider with broader scope may be more expensive per hour but less expensive overall when the cost of your coordination time is included.

Alternatively, make integration an explicit part of the scope. If you are hiring multiple specialists, define how they will coordinate, who is responsible for handoffs, and how conflicts will be resolved. Do not assume it will work itself out.

What Good Help Looks Like

Despite the warnings in this chapter, good outside help exists. Providers who genuinely want to solve your problem, who are transparent about their methods and pricing, and who deliver what they promise and do not create unnecessary dependency are out there.

Good help feels like partnership. The provider understands your situation and tailors their approach to it. They communicate clearly and frequently. They teach you what they are doing so you can maintain it after they leave. They want you to succeed, not just to continue paying them.

Good help leaves you better off. When the engagement ends, you have not just a deliverable but also understanding. You know how the system works. You can modify it or extend it. You are not more dependent than when you started; you are less.

Some businesses benefit from an ongoing relationship rather than a series of discrete projects. A partner who understands your operations, your data, and your constraints does not need to relearn the context each time a new need arises. They can recommend changes because they have watched the business evolve, and they can implement those changes efficiently because they built what already exists. This is different from dependency. Dependency means you cannot leave. Partnership means you choose to stay because the relationship continues to create value.

Finding good help requires patience and discernment. The red flags in this chapter can help you avoid the worst outcomes. The principles can help you recognize providers worth trusting. And the clarity you have developed about your own business—what problems matter, what constraints apply, and what you actually need—makes you a better buyer of whatever help you choose to seek.

From Guidance to Vision

You now have a framework for diagnosing problems, principles for prioritizing improvements, and guidance on working with outside help when needed.

The final chapter steps back from tactics to offer something different: a picture of what success looks like. Not a checklist of what to do, but a vision of what a well-designed small business feels like to operate.

About the Author

Alison Stoughton

Alison Stoughton

Founder & Lead Software Engineer, Stratelios

Alison is a software engineer and small business advocate who has spent over a decade building operational systems for growing companies across Kansas and Missouri. She founded Stratelios to give small businesses access to enterprise-quality technology through a direct, long-term partnership model.

Learn more about Alison →

Ready to Transform Your Business?

There are a number of ways to get in touch with us. Feel free to connect in whatever way you find most convenient.

Get in Touch

Contact Form

Call or Text

Slack

Slack

Slack Connect DM: alison@stratelios.com Open Slack

Google Chat

Google Chat DM: alison@stratelios.com Open Google Chat