The market for external help for SaaS founders has expanded significantly. "SaaS coach", "fractional CTO", and "SaaS consultant" appear on a lot of professional profiles — often on the same profile. The overlapping terminology makes it genuinely difficult for a founder to identify what they actually need.
This matters because the three roles operate at very different levels and address very different problems. Engaging the wrong one for your situation means spending money on help that does not address the actual constraint in your business.
The SaaS coach
A SaaS coach focuses on the founder and the business. Not exclusively on the technical side, not exclusively on the commercial side, but on the intersection of the person building the business and the decisions that business needs to make.
Coaching engagements address questions like: Are you building the right product for the right market? Is your pricing model correct? Are you spending time on the highest-leverage activities? What assumptions are you holding about your customers that have not been tested? Why have you been avoiding the conversation you know you need to have?
The defining characteristic of coaching is that it changes how you think, not just what you do. A good SaaS coach will identify the patterns in your decision-making that are causing you to make the same mistakes repeatedly — whether that is over-scoping the product, under-pricing the service, avoiding sales conversations, or building features rather than talking to customers.
Coaching works best when you have already established a direction and the constraint is the quality of your thinking and decisions, not the absence of a specific piece of technical capability or a specific deliverable. It is also particularly valuable in the earliest stages — before you have built much — because the decisions made at that stage are the hardest to reverse.
The fractional CTO
A fractional CTO focuses on technical leadership. They own the technical direction of the company on a part-time basis — the architecture, the engineering team, the development process, and the representation of the technical function to investors and partners.
A fractional CTO is an operational role, not an advisory one. They do not just advise on technical decisions — they make them, and they are accountable for them. This is the distinction that separates a fractional CTO from a technical advisor, who is consulted but does not own outcomes.
The fractional CTO is the right engagement when you have a technical function that needs leadership — a development team that lacks direction, an architecture that is not being managed intentionally, a technical roadmap that is not aligned with commercial goals. They give you the equivalent of a full-time technical leadership role at a cost structure that makes sense for an early-stage company.
The limitation of a fractional CTO is that they are primarily focused on the technical domain. If your problem is not primarily technical — if the constraint in your business is go-to-market strategy, customer discovery, pricing, or founder decision-making — a fractional CTO addresses a different problem.
The SaaS consultant
A SaaS consultant delivers specific outputs within a defined scope. They are engaged to produce something — an architecture review, a technical specification, an MVP build, a security audit, an infrastructure migration plan. The engagement has a defined start, a defined deliverable, and a defined end.
The consultant model is the right choice when you have a specific, bounded problem that requires external expertise to solve. The constraint is clear, the deliverable is clear, and the measure of success is clear.
SaaS consulting engagements are typically more transactional than coaching or fractional CTO arrangements. The consultant brings specific expertise, applies it to a defined problem, delivers the output, and the engagement concludes. There is less ongoing relationship, less strategic context-building, and less involvement in the overall direction of the business.
The limitation is the mirror image of the strength: a consultant solves the problem they are engaged to solve, but they are not positioned to identify the problems adjacent to it, and they are not incentivised to question the framing of the engagement itself.
How to choose
The question to ask is: what is the actual constraint in my business right now?
If the constraint is the quality of your thinking and decisions — you are not sure you are working on the right things, you keep running into the same obstacles, your strategy is unclear or untested — you need a coach.
If the constraint is technical leadership — your engineering function lacks direction, your architecture is not being managed, your technical team needs someone accountable for outcomes — you need a fractional CTO.
If the constraint is a specific deliverable — you need an architecture designed, a system audited, an MVP built, a technical specification written — you need a consultant.
These are not mutually exclusive. A single engagement can incorporate elements of all three. Joel's work with SaaS founders regularly involves coaching on strategy and positioning alongside architecture design and hands-on development consulting. But knowing which need is primary helps you evaluate whether the person you are considering can actually address it.
The red flags
A fractional CTO who will not own decisions — who will only advise — is not a fractional CTO. They are a technical advisor with an inflated title. Be explicit about what ownership means in the engagement and what decisions they are accountable for.
A SaaS coach who does not have direct experience building SaaS products is offering a generic coaching framework applied to a domain they do not deeply understand. SaaS has specific dynamics — recurring revenue, churn, multi-tenancy, pricing psychology, the relationship between architecture and growth — that cannot be understood without direct experience.
A SaaS consultant who expands scope without explicit agreement is optimising for billing, not for your business. Scope expansion happens in consulting — requirements are often unclear at the start — but it should always be explicit, agreed, and justified.
In all three cases, the clearest signal is whether the person asks hard questions before agreeing to engage. Someone who takes any engagement without challenging the framing is telling you something about how they work.