A software subscription gives you a product. A consultant helps translate the way your business operates into a working system. Many businesses need both, but they should not pay for custom work when a standard feature already solves the problem.
/ 01
Choose software when the process is standard
Packaged software is usually the better answer for established jobs such as accounting, scheduling, basic email marketing, or support ticketing. If 80–90% of the requirement matches a mature product and the business can adopt its workflow, configuration is usually cheaper, faster, and easier to maintain than custom code.
Test the product with five real cases before buying an annual plan. Verify export, permissions, audit history, integration limits, usage pricing, and what happens when you leave.
/ 02
Choose consulting when the process crosses systems
A consultant becomes useful when the real process crosses inboxes, spreadsheets, documents, databases, and informal decisions. The hard part is not merely connecting applications; it is deciding which information is authoritative, translating policy into testable rules, limiting access, and handling exceptions.
The deliverable should include more than a working demo: a process map, boundary statement, permission list, test evidence, owner, operating instructions, asset inventory, and recovery path.
/ 03
Choose an internal hire when demand is continuous
If several departments have a permanent queue of automation work, an internal owner may be the right long-term choice. That person still needs business stakeholders, security support, and clear governance.
/ 04
Use a short consultation to decide
A focused consultation should identify one process, the systems involved, the likely risk, and whether the next step is configuration, custom implementation, or no project at all. A credible advisor should be willing to recommend an existing product or no automation when those are the better choices.
/ 05
Use this decision matrix
Score each statement from zero to two. Favor software when the process is standard, the team can change its habits, and the product already meets security and integration needs. Favor consulting when the process is differentiating, crosses several systems, includes non-obvious exceptions, or requires tailored controls. Favor an internal hire when demand is continuous across multiple teams and the organization can support product ownership.
A blended path is common: buy the system of record, then use focused consulting to configure it, connect it safely, migrate data, document decisions, and build only the missing pieces.
- Can a mature product solve at least 80% without custom code?
- Will the team adopt the product's process?
- Does the workflow create strategic differentiation?
- Are exceptions or permissions business-specific?
- Is there a permanent backlog for one full-time owner?
- Who maintains the result after launch?
/ Practical takeaway
Buy software for standard work, use consulting for business-specific integration and controls, and hire internally when the backlog and ownership needs are truly continuous.