Most requests to advise a founder never arrive as requests. They arrive as a question at the end of dinner, a text with a screenshot attached, a five-minute conversation in a parking lot that turns into forty. Nobody says the words "will you advise me." You just find yourself three months into an unpaid, undefined, permanently available role, with opinions you are now expected to keep having.
That drift is the real risk in advising founders you also know socially. It is not the dramatic falling-out over a bad call. It is the slow accumulation of half-informed input that neither of you ever agreed to, until the friendship is carrying weight it was never built for. Florida makes this more likely, not less. The circles here are small and overlapping, and the person asking you about their cap table on Saturday is somebody you will see again on Tuesday whether the advice worked or not.
Name the role out loud, even if it feels stiff
There are only three roles available, and the trouble starts when both people assume a different one. You are a friend with a view, which carries no duty and no follow-up. You are an advisor, which means bounded work on a defined question, with a beginning and an end. Or you are a fiduciary — a board member or an investor — which means your obligation runs to the company, not to the person who invited you.
Saying which one you are in is awkward for about ten seconds and saves you a year of ambiguity. I have found that the plainest version works best: "I'm happy to think about this with you as a friend, but I'm not going to be the person who signs off on it." Founders rarely take offence at that. What they take offence at is discovering, after they relied on you, that you thought you were making conversation.
The distinction also protects them. A friend's opinion delivered with an advisor's confidence is a genuinely dangerous product. If I have not seen the numbers, I say I have not seen the numbers, and I discount everything that follows in front of them rather than in my own head.
What I say yes to, and what I decline
I say yes to bounded questions. A pricing decision, a hiring structure, a specific negotiation, a read on whether a term sheet is normal. Those have edges. I can be useful inside a few conversations and then leave, and the friendship absorbs no permanent obligation.
I decline open-ended custodianship — "help me run this" — because it is the request that most reliably ends badly between friends. It has no completion condition, so the only way out is for one of you to withdraw, which always reads as a judgment on the other. I also decline when the honest answer is that they need an operator and I would only be lending a network. Introductions are not strategy, and a founder who mistakes access for advice will spend a year on the wrong problem.
And I decline when I might want to invest. You cannot coach someone through a decision and price the outcome of that decision at the same time. If I think there is a chance I will be on the other side of a table, I say so early, before I have absorbed anything that would be unfair to hold. This is the same instinct that governs how I approach board seats generally — I ask to observe a meeting before I accept one, because watching a group handle a real disagreement tells you more than any conversation about the role. I wrote about the rest of that screen in the questions I ask before saying yes to a board seat.
Give the relationship a venue
The most useful boundary I have found is not about content. It is about where the advising happens. Social settings are terrible places to give business advice. You are half-informed, both of you are relaxed, and the answer you produce in that state gets remembered with more authority than it earned.
So I move it. Thirty scheduled minutes, on a call or across a table, with the specific question stated in advance. It sounds bureaucratic between friends, and it is the single change that improves the quality of everything that follows. The founder arrives having thought about what they actually want to know. I arrive having looked at something. And the dinner stays a dinner.
There is a second benefit. A scheduled slot has a natural end, which means the relationship has a rhythm rather than a permanent open channel. Ambient availability feels generous. In practice it trains a founder to outsource small decisions they should be making alone, and it quietly makes you responsible for outcomes you have no ability to influence.
Keep the two information streams apart
This is the boundary people miss. When you know a founder socially, you learn things socially — that they are stretched, that a co-founder relationship is strained, that they are more worried than they let on in the meeting. If you also sit in a governance role, you now hold information that arrived through the wrong door.
My rule is that anything I learn as a friend does not get used in a formal setting, and anything I learn in a formal setting does not get repeated in a social one. If something I heard over a weekend genuinely matters to the company, I do not smuggle it into a discussion. I tell the founder it matters and that they should be the one to raise it. That keeps the channel honest in both directions. The alternative — becoming the person who knows things he cannot explain how he knows — corrodes trust faster than any disagreement.
Small boards make this harder because there is no committee structure to route things through and often no minute-taker who is not also a friend. Some of that has structural fixes, which I have set out in a piece on governance when the board is four people and a lawyer, but most of it is personal discipline exercised in the moment.
How to disagree without spending the friendship
Disagreement is the whole value of the relationship. If you cannot deliver it, you are company, not counsel. The technique that works for me has four parts and takes about two minutes.
First, separate the decision from the person explicitly. Not "you're being naive" but "this plan assumes something I don't think holds." Second, state your confidence level. There is a real difference between "I would not do this" and "I lean the other way, but I could be wrong," and founders deserve to know which one they are getting. Third, say it once, completely, including the part that is uncomfortable. Repeating yourself is how advice turns into pressure. Fourth — and this is the one that preserves the friendship — say out loud that it is their call and that you will support it either way, and then actually do that.
The follow-through matters more than the delivery. If they go the other way and it works, you say so cheerfully. If it fails, you do not mention that you called it. A friend who collects vindication is not a friend anybody consults twice. I would rather be the person a founder calls after the bad quarter than the person who was right about it.
Writing it down helps too. A short note after the conversation — here is what I understood, here is what I'd do, here is what I'm unsure about — removes the memory dispute that otherwise poisons things a year later. It takes five minutes and it is the cheapest insurance in the relationship.
Build in an ending before you need one
Every advising relationship between friends should have a stated end: a date, a milestone, or a specific decision after which it is over unless you both renew it. Most people skip this because it feels like planning for failure. It is the opposite. An end date makes it possible to stop without anyone reading the stop as a verdict.
Living in the same market as the people you advise raises the stakes on all of this, which is a theme I keep returning to — in how board service works when you live in the same market, and in the alumni community I founded and chair here in Florida, where the person across the table this month is somebody's neighbour next month. You do not get clean exits in a small market. You get continued proximity. That is an argument for more structure between friends, not less.
What the friendship is actually for
The reason to keep distance is not self-protection. It is that a founder with plenty of cheerleaders and no candid outside view is badly served, and you cannot be candid with someone whose good opinion you are trying to keep. The boundary is what makes the honesty affordable.
So name the role, pick the venue, disagree once and clearly, and agree on when it ends. Do that and you get to keep both things — the useful counsel and the friendship underneath it. Skip it and you usually lose the second one defending the first.