"Fractional technical advisor" is a phrase that means nothing until someone describes the actual work. So here it is plainly.
The problem it solves
A small business reaches a point where the constraint is not effort or sales. It is that the way work moves through the business no longer holds.
Leads arrive and get lost. Information lives in four places. The owner is the only person who can do several important things. Software has accumulated without a plan. Somebody built a spreadsheet that now runs the company.
The business needs someone who can look at that, understand both the technology and the business economics, decide what is worth fixing, and then actually build it.
Hiring a full-time person for that is expensive and, at this size, usually not a full-time job. So you get a fraction of one.
What the work actually is
Finding the leak. Not a general audit. Specifically: where is this business losing money or time right now, and how much? Missed calls that never get returned. Quotes nobody followed up. A process that takes four hours a week and could take ten minutes.
Deciding what is worth doing. Most identified problems should not be fixed. The value is in ranking honestly by return, and being willing to say "that one is not worth the money" — which is the part a vendor selling you something will not do.
Building the fix. Actually building it, not writing a recommendation for someone else to build. The system exists, works, and is handed over.
Handing it over properly. Documented, owned by you, running without me. If it needs me to keep working, I built the wrong thing.
Being available for the next decision. Should we buy this software. Is this vendor legitimate. Do we need custom development for this. Why does this keep breaking. That is where the ongoing part of the role lives.
What it is not
Not a developer for hire. A developer builds what you specify. If your specification is wrong, you get a well-built wrong thing.
Not a strategy consultant. No deck at the end, nothing to implement afterward.
Not an agency retainer where you buy hours and hope.
Not a lock-in. What gets built belongs to you and runs without me. Plenty of businesses do one project and are set.
When a business genuinely needs one
- The owner is the bottleneck for several important things.
- Software has piled up and nobody is sure what is actually used.
- Something is clearly leaking — leads, follow-up, time — and nobody has quantified it.
- A vendor is proposing something expensive and there is nobody internally who can evaluate it.
- The business is about to grow and the current way of working will not survive it.
- Someone built the system and left.
When it does not
- The problem is sales volume, not operations. More traffic is a marketing problem.
- The business is very small and genuinely simple. Some businesses do not need this and should be told so.
- There is no willingness to change how things are done. A system nobody adopts is money burned.
- What is actually needed is a specific piece of software that already exists.
How to evaluate anyone offering this
Ask these:
- What would you look at first, and why? A good answer is specific and about your business. A bad one is a generic methodology.
- What have you built, and what number did it move? Not what you advised. What exists and what changed.
- What would you tell me not to do? Someone who has never talked a client out of a project is selling, not advising.
- What happens when we are done? Ownership, documentation, and whether anything depends on them.
- Have you run a business yourself? Not essential, and it changes how someone thinks about cash flow and risk.
The honest version of the economics
This works when the thing built saves or earns more than it cost, reasonably quickly, and keeps doing so without ongoing spend.
If that maths does not hold for a particular project, the right answer is to say so before starting. A free call where someone tells you the numbers do not work is worth more than a proposal that ignores them.