Who Has the Last Word? Decisions, Budgets, and Hiring Family

A business makes decisions without end. Big ones — changing direction, opening a location, or taking on debt. Medium ones — approving the budget or hiring a manager. Small ones — buying this, selling that, or signing here — a dozen before lunch. And behind every decision stands the question that, in my experience, generates the classic partner grievance:

"Who gave you the right to spend that money?"

That sentence, in one version or another, opens a remarkable share of the disputes that reach my table. And notice what kind of complaint it is: not that the decision was wrong, but that the deciding partner didn't have the right to make it alone. Partners can forgive a bad decision made properly far more easily than a good decision made improperly. That's why this chapter exists: to make crystal clear what each partner may do on his own, what requires everyone's consent, and how the last word is reached. The clearer the boundaries, the fewer the fights — that's not a slogan; it's the single most consistent pattern I've observed.

The guide splits decision-making into three altitudes — general direction, the budget, and daily management — plus one special question that deserves its own section (you'll see why). Let me take them one at a time.

The big word: who decides the direction of the business?

First altitude: every major change of direction. New product lines, new locations, taking on major debt, bringing in partners, and selling divisions — these are the decisions that shape what the business is.

The structures range along a spectrum from pure democracy to defined authority. One partner, one vote, majority rules — and note what this means in a two-partner business: complete deadlock protection for both, since neither can force anything on the other. Discussion first, then majority — every change must be discussed with all partners; failing consensus, the majority decides — with a practical safeguard worth its weight in gold: a partner who doesn't show up to the meeting (properly noticed a certain number of days in advance) cannot paralyze the decision by his absence. I've seen the empty-chair veto used as a weapon; this clause disarms it. Nobody can force anybody — even a majority owner cannot impose his view; failing agreement, the dispute-resolution path decides. Try for consensus, then ownership percentage decides — and if the sides hold exactly equal percentages, the conflict clause breaks the tie. A defined leadership group — in multi-partner businesses, a named subset of partners discusses and decides by majority within the group, again with no-show protection. One person has the last word — temporarily: on everything the agreement doesn't settle, a named partner decides until a defined time or condition — as long as he works in the business, for example, or until the business obtains a conventional bank loan — after which power equalizes. This one is beautifully suited to founder-led businesses taking investment: the founder keeps operational command through the fragile years, and the structure matures automatically. And finally, one person always has the last word on everything the agreement doesn't explicitly settle otherwise — the other partner defers. This is perfectly legitimate if it is written and knowingly accepted. The disaster version is when one partner believes this arrangement exists and the other believes in democracy — each running a different constitution in his head.

Which is right for you? The question to ask is an honest one: when you and your partner disagree about something big and neither budges, what should happen, structurally? If your answer is "that won't happen to us," re-read the first article of this series.

The budget: same rules, or its own?

Second altitude, one focused question: does the main budget follow the same approval path as other big decisions?

For most partnerships, yes — one sentence, and it's done. But the question earns its place because the budget is a special kind of decision: approve it once, and you've pre-approved a thousand smaller decisions inside it. Some partnerships, therefore, want the budget handled differently from other big moves — approved by a simple majority of partners, for example, or weighted by ownership shares even where other decisions follow a one-partner-one-vote rule. If the budget is where your partnership's real power should sit, say so; otherwise, the default — the budget follows the big-decision rules — is clean and sensible.

Daily management: speed versus safety

Third altitude: the everyday — buying, selling, hiring, firing, and everything like it. Here the trade-off is explicit, and I put it to partners exactly this way: at one pole, everyone decides everything together, which is maximally safe and unbearably slow; at the other, each partner rules his own domain, which is fast but demands real trust. The art is picking your point on that line — and drawing it in dollars.

The workable structures: majority on everything (or by ownership percentage) — safe, slow, and in practice only fit for businesses with few decisions, like a holding company. Domains with a permission threshold — the pattern I see work most often: each partner has authority over his own area of responsibility (remember the role assignments from the building chapter), but any expense above a set amount — per transaction or cumulative for the year — needs all partners' consent. The dollar line does the work: $25,000 per transaction, say, or perhaps $120,000 cumulative; below it, speed; above it, consultation. Budget-bounded autonomy — each partner decides freely within his domain as long as it fits the approved budget; overruns beyond a small tolerance (say 5%, whether a single case or cumulative) require the partners' approval. The budget becomes the standing permission slip, which is exactly what budgets are for. Two-tier notify/approve — the manager decides daily matters independently; for defined middle-weight actions, he must notify the other partners (within a set number of days — such as hiring above a salary line or expenses above a threshold); for defined heavy actions, he must get explicit permission (bigger hires, loans with collateral, a new location, or taking on a client so large they would exceed a set share of total sales — a concentration-risk trigger most partners never think of until the mega-client leaves and takes a third of the revenue with him). This structure is my recommendation for businesses with one clear operator and one or more hands-off partners: the operator keeps his hands free, the partners keep their eyes open, and the notification duty quietly builds the paper trail that makes the quarterly reckoning boring — which is exactly what you want reckonings to be.

Whatever you choose, the goal is the same: that the sentence "who gave you the right?" becomes unaskable — because the answer is always: page four.

Hiring family: the small question that ends partnerships

And now the question I call small on paper and enormous in life: may a partner bring family members — children, in-laws, relatives — to work in the business?

Why does this one deserve its own section? Because it is the point where the partnership collides with something even stronger than money: family. Consider the day it goes wrong. Your partner's son works in the business and isn't good at his job. Now every managerial conversation is booby-trapped: criticize the son, and you've insulted the partner; fire him — is that even possible without breaking the partnership? Meanwhile, the other partner watches payroll carry a weak employee and feels the business is subsidizing someone else's family. I've watched this exact dynamic corrode partnerships that had survived every financial storm — because nobody could say the obvious thing out loud.

The agreement can say it in advance, when nobody's actual child is on the table. The two honest doors: yes, with defined consent — relatives may be hired, but only with the permission of a defined number of partners (or all of them); or no automatic entry — no relative joins without the written consent of the other partner or partners, case by case. And with the "no" door, I recommend two add-ons without hesitation: The relative signs a non-compete and a conflict-of-interest agreement before starting — because a partner's relative sees everything, and their exit is messier than a stranger's. And this clause, worth more than everything else in the section: if the relative isn't suited to the job, he is treated exactly like any other unsuitable employee — and may be let go. One sentence, agreed upon while it's still hypothetical and written while everyone can still smile at it. It converts the un-haveable conversation into a pre-had one. That is, in miniature, the entire philosophy of this guide.

The quiet dividend

One more thing about clear decision rights, and it's the part people don't anticipate: the rules are at their most valuable when they are never invoked. Partners with clean decision boundaries stop keeping score. The working partner doesn't tally every autonomous decision as a potential future accusation; the money partner doesn't experience every unreviewed purchase as a small trespass. The mental ledger—the exhausting, unspoken bookkeeping of who decided what without asking me—simply closes. What's left is two people doing their jobs. In a good partnership, the constitution's finest work is invisible: it is the fight that never starts, the question that never needs asking, the "who gave you the right?" that dies before it is born—because everyone always knew.