You ask your fractional CTO which observability tool to buy, which agency to bring in for the mobile app, or which cloud reseller to move your billing to. They give you a clear answer. What you may not know is whether anyone pays them when you follow it.
The short answer: a fractional CTO can be paid by the vendors they recommend, through partner programs, reseller margins, agency referral fees, or recruiter placement splits. None of these is illegal, and some advisors use them openly. The problem is undisclosed money. You are paying for independent judgment, and a recommendation with a hidden commission attached is not independent. Ask the question directly, put a disclosure clause in the contract, and treat a vague answer as an answer.
Where vendor money comes from
Most founders imagine a kickback as an envelope. In practice it is a normal business program that the vendor runs for anyone who sends them customers. The common sources:
- Software partner and affiliate programs. Many developer tools, hosting platforms, and SaaS products pay partners a share of the customer's spend, either once or for a period after signup. The partner is often an agency or consultant, which is exactly the role a fractional CTO plays.
- Cloud resale and billing. Some advisors and agencies resell cloud accounts, putting your usage under their billing so they earn a margin or keep discounts the provider gives them. The money is invisible on your side because your invoice looks normal.
- Agency referral fees. Development agencies frequently pay for introductions to clients, either a flat fee or a percentage of the first contract. An advisor who sends you to "a team I trust" may also be sending an invoice to that team.
- Recruiter splits. When an advisor introduces a recruiter who then fills your senior engineer role, the advisor may receive part of the placement fee.
- Equity or ownership. The quietest case. The advisor holds shares in, or is a partner of, the agency or tool they keep recommending.
Each of these can exist alongside honest advice. The issue is that you cannot tell which recommendation was made on the merits unless you know where the money flows.
Why it matters more for a fractional CTO than for most advisors
A fractional CTO's main job in the first year is spending decisions: which vendor, which hire, which platform, whether to buy at all. Those are the decisions where a referral payment points the same way every time, toward spending, toward a specific vendor, and toward switching rather than staying.
It also compounds. A tool chosen today becomes the thing you pay for every month for years, and switching costs grow as you build on it. A cloud account under someone else's billing is harder to move later, a pattern covered in a cloud account inside a reseller's organization. A biased first choice is not a one-time cost.
This is the same structural concern as charging a percent of engineering spend: when the advisor earns more as you spend more, the one judgment you need most, when not to spend, gets harder to trust.
What a clean arrangement looks like
There are three acceptable positions, and all of them are written down.
No vendor money at all
The advisor takes no partner fees, no reseller margin, and no referral payments, and says so in the contract. This is the simplest and the one I use. It costs the advisor some income, and it removes the question entirely.
Disclosed and passed through
The advisor is enrolled in a partner program, perhaps because it gives access to support or early features, but any commission is disclosed before you buy and credited back against your retainer. You get the benefit, and the incentive to pick that vendor disappears.
Disclosed and declined from the decision
The advisor has an interest, for example equity in an agency, and says so up front, then steps out of that specific decision. You run a vendor bake-off without them steering it, or bring in a second opinion.
What is not acceptable is the fourth position: a payment you find out about later.
The clause to put in the contract
Whatever your advisor's answer, put it in writing. A workable clause covers four things:
- The advisor must disclose, in writing and before you commit, any fee, commission, margin, equity, or other benefit they or their firm receive or expect to receive from a vendor, agency, recruiter, or platform they recommend.
- The disclosure covers related firms, so an advisor cannot route the payment through a partner company.
- Any undisclosed payment is refundable to you, and finding one is grounds to end the engagement without the notice period.
- You can ask, at any time, for a written list of current vendor relationships.
This sits naturally next to the conflict exclusions in what to cap and what not to cap in a fractional CTO's liability: undisclosed conflicts are not ordinary mistakes, and they should not be protected by a fee cap.
How to check without accusing anyone
Most advisors are honest, and the question should feel routine, not like an audit. Ways to ask that work:
- In the first call: "Do you have any paid relationships with vendors, agencies, or recruiters you might recommend to us?" A good advisor answers immediately and specifically.
- When a recommendation comes in: "What were the alternatives, and why this one?" A real answer names two or three options and the tradeoff. A thin answer is a signal, whatever the reason.
- When signing up for something: check whether the signup link carries a referral or partner code. Many do, and the URL tells you.
- For cloud: confirm that your cloud account is in your own organization, billed to your own card, with your own root access.
If the advisor gets defensive about any of this, that tells you more than any clause would.
What this looks like in practice
This is a composite of a pattern I have seen more than once. A seed-stage founder brings me in after a previous advisor had left. Over about a year the company has moved its hosting, its error tracking, and its mobile build to vendors the advisor recommended, and has engaged an agency for the app. None of the choices is bad on its own. But a review of the accounts shows two of the tools were signed up through partner links, and the agency confirms it pays introduction fees. The advisor never mentioned either. Nothing illegal happened, and the tools mostly work. The founder's real loss is not the money; it is that they can no longer trust the earlier reasoning, so the expensive decisions have to be redone from scratch. That review usually costs more than the commissions ever paid.
How I handle it
I take no vendor, agency, recruiter, or reseller payments, and I am happy to put that in the contract. If that ever changed for a specific relationship, it would be disclosed in writing before you made a decision. My terms are on the pricing page. If you want a second opinion on vendor choices someone else made for you, the technical teardown is built for that, or you can book a call.
FAQ
Is it legal for a fractional CTO to take referral fees from vendors?
Generally yes. Partner programs, reseller margins, and referral fees are ordinary business arrangements. The concern is not legality but disclosure: you are paying for independent advice, and an undisclosed payment from the recommended vendor undermines that.
How do I find out if my fractional CTO gets paid by a vendor?
Ask directly and in writing, check signup links for partner or referral codes, and confirm that cloud and SaaS accounts are in your own name and billed to you. A contract clause requiring written disclosure is the reliable fix.
What if my advisor is in a partner program for good reasons?
That can be fine. The clean version is disclosure before you buy plus a credit of any commission back against your fees, so the program's benefits reach you without biasing the recommendation.
Should I redo decisions made by a previous advisor with undisclosed vendor ties?
Not all of them. Review the ones with ongoing cost and high switching cost first, such as hosting, core infrastructure, and long agency contracts. Many earlier choices will turn out fine; the point is to know they were made on the merits.