How to pay a technical cofounder when cash is tight

Why this gets tense fast

The hard part of how to pay a technical cofounder is simple: the work starts early, and money usually does not. Someone needs to design the product, build the first version, fix bugs, and keep things running before a single customer pays.

That creates an uneven risk on day one. A business founder may bring the idea, early sales, or industry contacts. The technical founder often brings months of hands-on work that the company would otherwise need to buy at market rate.

Tension grows when those two risks do not feel equal. If one person keeps a salary from another job while the other spends nights and weekends building, both can feel underpaid for different reasons. One feels cash pressure. The other feels invisible labor.

Small cash gaps cause bigger emotions than most founders expect. Missing a promised monthly payment by even a few hundred dollars can change the tone fast. What felt like a partnership starts to feel like one person is carrying the company while the other keeps making requests.

Vague promises make this worse. "We will sort out equity later" sounds harmless in the first week. Three months later, after a prototype, customer calls, and a few all-nighters, that same sentence turns into a fight about who earned what.

A common example looks like this: one founder says, "Build the MVP now, and we will make it fair after fundraising." The problem is that fundraising may take six months, or never happen. By then, the technical cofounder has already spent time, skipped paid work, and taken on real risk without a clear deal.

Even when both people mean well, memory changes the story. One remembers every late night and production issue. The other remembers every pitch, intro, and investor meeting. If the agreement lives only in text messages and casual calls, each person starts doing their own math.

That is why founder pay talks get tense so fast. You are not only pricing work. You are pricing risk, timing, trust, and the chance that the company may not work at all. If you do not name the cash amount, ownership rules, and milestones early, the argument shows up later, usually when stress is already high.

Start with the real trade-offs

Most founder fights start when effort feels equal but is not. One person may write code for 35 hours a week, while the other squeezes in 10 hours after a day job and still calls it "full time soon." That gap matters more than optimism.

Write down the actual hours each founder can give every week for the next three to six months. Use real numbers, not best-case promises. If one founder can work nights and weekends only, treat that as part-time. If another can work 40 hours and answer production issues during the day, that is a different level of commitment.

Roles need the same honesty. The technical founder may build the product, but someone still has to handle customer calls, sales, hiring, legal tasks, and the dull admin work that keeps a startup alive. If one person owns code and the other owns product, sales, and operations, that can be fair. If one person does all of that while the other "advises," it usually is not.

Past work and future work should stay separate. A prototype built last month has value, but it should not blur the deal for the next year of work. Treat past contributions as a known input. Then make a fresh plan for what each person will do from this point on.

Money is usually the part people avoid. Do not avoid it. Each founder should say how much cash they need every month to stay afloat. Rent, family costs, debt payments, whatever is real. If one person can survive on almost nothing and the other cannot, pretending they are in the same spot will break trust fast.

A simple example makes this easier. If Maya can code 30 hours a week and needs $2,000 a month to keep going, while Leo can do sales 20 hours a week and needs $500, their deal should reflect both time and cash pressure. Equal titles do not always mean equal terms.

Define "full time" before anyone uses the phrase again. Does it mean 40 hours a week? No side clients? Fast response during work hours? Availability for weekend issues? A vague promise causes more damage than a smaller but clear commitment.

If you are working out how to pay a technical cofounder, start with these plain facts first. The money and equity discussion gets much easier once both sides agree on time, roles, past effort, and basic living needs.

Pick a pay mix you can actually afford

A deal only works if you can still pay it three months from now. Founders often promise a monthly amount that feels fine in week one and painful by month three. Start with the number your company can pay every month without guessing, dipping into personal bills, or betting on money that is not in the bank yet.

If you can afford some cash, pay some cash. Even a small monthly amount changes the tone of the partnership. It shows the technical cofounder is not carrying all the risk alone, and it helps both sides treat the work like a real job from day one.

Use equity to cover the gap, not to dodge the math. If the work would normally cost much more than you can pay, say that out loud and turn the unpaid part into a reasoned ownership share. A lower cash amount that lasts is better than a bigger promise that collapses after eight weeks.

Before you settle on a number, check four things:

• how much the company can pay for at least 6 to 9 months
• how much cash you need to keep for legal, tools, and basic operations
• what budget you want to protect for your first hire
• which business result unlocks a pay increase

That last point matters a lot. Raise cash pay only when something concrete happens, such as first customer revenue, a signed contract, or outside funding. Do not tie higher pay to effort alone. Hard work matters, but revenue pays salaries.

Leave space for the next person you need. Many early teams forget that the technical cofounder is rarely the last hire. You may soon need a contractor, a designer, customer support, or someone to handle sales follow-up. If one cofounder deal eats the whole budget, the company gets stuck.

Review the mix after launch or after the first paying customer. By then, you know more than you did at the start. That is usually the cleanest answer to how to pay a technical cofounder when cash is tight: small steady cash, equity for the shortfall, and more pay only when the business can truly support it.

Stage ownership instead of giving it all up front

Giving away the full stake on day one is usually a mistake. If a technical cofounder leaves after a month, or the fit turns out wrong, you cannot easily unwind that decision. Vesting keeps ownership tied to real work over time.

A simple startup vesting schedule works better than a handshake promise. Many teams use monthly vesting over several years, with a 12 month cliff at the start. That cliff matters. If someone stops working in month 8, they do not walk away with a large piece of the company for a short stint.

Extra equity can sit behind clear cofounder equity milestones. Keep those milestones concrete and easy to check:

• a working product shipped to the agreed scope
• the first production release used by real customers
• a defined technical handoff, if the role changes later
• a written review of ownership if responsibilities expand a lot

Avoid vague milestone language. "Help with product" and "support growth" sound nice, but they create fights later. Write outcomes that two tired founders can still agree on at 11 p.m. without arguing.

You also need rules for messy cases. If the technical cofounder drops from full-time to five hours a week, say what changes. If the scope doubles because the business changes direction, pause and update the deal before more work starts. Do not let silent resentment replace a real conversation.

Keep the cap table simple. One page should explain how much equity vests over time, what the cliff is, which milestones unlock extra shares, and what happens if either founder leaves. If you cannot explain the deal in plain English, the deal is too complicated.

This is a big part of how to pay a technical cofounder fairly when cash is tight. Small cash helps with day-to-day pressure. Staged ownership protects both sides while the company is still proving itself.

Set the deal in five steps

Money stress turns vague promises into arguments fast. A simple five step deal gives both founders something concrete to check when pressure goes up.

1. Start with the first product goal. Define the first version that matters, not the dream version. Maybe that means a usable beta, working payments, and one real customer. If you cannot name the first finish line, you cannot price the work fairly.

2. Set the monthly cash floor. Pick the smallest amount the company can pay every month for at least six months without panic. Even a modest payment changes the tone. It shows respect for the technical founder's time, and it forces the company to stay honest about runway.

3. Choose an equity range and write the reason. Do not jump to one number in a loose chat. Pick a narrow range based on expected hours, risk, stage, and whether this person is joining as a true cofounder or acting more like an early builder. Write down why the range makes sense, because memory gets very convenient later.

4. Break ownership into milestones. Two or three milestones are enough for an early deal. Give each one a date and a clear deliverable, such as a beta by June 30, first paying customer support by August 31, or a stable release with agreed performance targets. Tie each equity chunk to work that both sides can verify.

5. Put review dates on the calendar before any work starts. A monthly check-in and a formal review at each milestone usually works well. Use those meetings to adjust scope, timing, or cash if reality changes.

This is the practical version of how to pay a technical cofounder when cash is tight. Small cash, staged equity, written reasons, and fixed review dates feel a little rigid on day one. They feel much better than a messy argument in month three.

A simple founder pay example

Sam runs the business side. He handles sales calls, talks to early customers, and spends time on fundraising. Priya takes the product side and agrees to build the first version over six months.

The company is short on cash, so Priya does not get a normal market salary. Instead, the startup pays her $1,500 a month during that first stretch. That amount will not match what she could earn at a larger company, but it does two useful things: it helps cover basic living costs, and it shows that her work is not being treated as free labor.

On the ownership side, Priya earns 12% equity on a four-year vesting schedule with a one-year cliff. If she leaves after a few months, she does not keep part of the company just because she started the codebase. If she stays and keeps building, her stake vests over time like any other founder deal that takes risk seriously.

The deal also adds one clear milestone. After Priya ships a working beta, she gets another 2% grant. That extra piece ties ownership to a real result, not just time on the calendar. A shipped beta is easy to see and hard to argue about later.

This setup works because each founder carries a different burden. Sam does the customer work and tries to bring money in. Priya builds the product for below-market cash and takes a large part of her pay in upside. That is a fairer version of how to pay a technical cofounder when the company cannot afford full salaries yet.

They also set one point to revisit cash pay: either the startup reaches ten paying customers or it closes outside funding. Once one of those happens, they sit down and adjust Priya's monthly pay based on what the business can support.

A deal like this is not fancy. That is why it works. The cash number is clear, the vesting is clear, the milestone is clear, and the review point is clear. When pressure hits, clarity matters more than optimism.

Write down the rules before work starts

Verbal deals feel fine when both founders are excited. They fall apart when payroll slips, the build takes longer than expected, or one person thinks a milestone is done and the other does not. Put the full deal in one shared document before anyone writes code or quits a job.

When people ask how to pay a technical cofounder, the money mix gets most of the attention. The rules around that mix matter just as much. If you skip them, small surprises turn into personal fights.

A good draft should answer five boring but costly questions:

• When does cash get paid, on what date, and what happens if the company cannot cover the full amount that month?
• What does each milestone mean in real terms, with work anyone can check instead of vague labels like "MVP done"?
• Who owns the code, design files, domains, accounts, and customer data from day one?
• How do you change scope, deadlines, or pay if the product shifts?
• What happens if one founder leaves after 3 weeks, 6 months, or right after launch?

Write milestones so a third person could read them and say yes or no. "Build onboarding" is too loose. "Users can sign up, confirm email, create a workspace, and invite one teammate" is clear enough to test.

Money terms need the same level of detail. Set the payment date, any deferred amount, and the exact trigger for a fallback plan if cash runs short. For example, you might pause cash pay when runway drops below two months, then convert the unpaid part into a founder loan or extra equity only if both founders approve it in writing.

Ownership needs plain words too. The company should own product code, designs, and customer data. Founders should know who controls repos, hosting, admin accounts, and backups. If someone leaves, the company still needs clean access on the same day.

Add one small rule for change requests: no major scope or deadline change counts unless both founders write it down and agree to the trade-off. That one habit prevents a lot of silent resentment.

If a founder leaves, spell out vesting, handoff duties, and account access. You do not need a long document. You need a clear one.

Mistakes that break trust

Trust usually breaks before the product does. It breaks when one founder feels locked into a bad deal, or when the other feels the rules keep changing.

The fastest way to create that problem is giving away a large chunk of equity on day one. If someone gets full ownership before they prove they can stay, build, and deliver, the other founder takes all the risk. A startup vesting schedule exists for a reason. It gives both people time to earn the deal instead of guessing up front.

Another common mistake is promising "more later" without a written trigger. That sounds flexible, but it usually turns into an argument. "Later" means one thing to the person writing code at midnight and another thing to the person pitching investors. If extra equity depends on shipping an MVP, hitting revenue, or taking over engineering full time, write that down in plain words.

Founders also damage trust when they treat the original idea as equal to months of build work. Ideas matter, but execution is where the cost shows up. One person may bring the concept, early customer talks, or industry knowledge. The other may spend four months building, fixing bugs, and handling every technical choice. Those are not the same kind of contribution, and pretending they are will sting later.

Unpaid work already done should not disappear from the conversation. If a technical cofounder spent nights and weekends building the first version before any formal deal existed, count that effort somehow. You do not need a perfect formula. You do need to admit the work happened and agree on how it affects the cash and equity split.

The worst time to renegotiate is when someone is already exhausted. Burnout makes every discussion feel personal. Small resets work better when they happen early.

A few warning signs are hard to miss:

• one founder keeps asking when equity will be updated
• the scope grows, but pay stays frozen
• unpaid work piles up with no record
• both sides remember the original deal differently

If you are figuring out how to pay a technical cofounder, clarity matters more than optimism. A modest cash amount, staged equity, and written milestones may feel less romantic, but they give both founders a fair shot at staying on the same side.

Quick checks before you agree

A deal can look fair on paper and still fall apart in month two. The usual problems are plain ones: the cash runs out, milestones mean different things to each founder, or equity keeps vesting after someone stops doing the work.

Test the cash part against your real bank balance, not your best-case forecast. If you promise even a modest monthly payment, make sure the company can cover it for at least three months without depending on a lucky sale, a fast fundraise, or a delayed bill.

Milestones need plain language. "Launch beta" sounds clear until one founder means "the product works on a test server" and the other means "customers can sign up and use it without help." If you both define the same milestone in different ways now, you will argue about it later.

A short checklist catches most weak deals:

• Can the startup pay the cash part for the next three months, even if revenue is late?
• Can both founders describe each milestone in the same words and point to the same proof?
• If one founder stops showing up, does equity vesting pause, or does it keep running anyway?
• Did you write down the salary or cash payment, equity amount, vesting terms, and review dates?
• If the launch slips by a month, would both sides still call the deal fair?

That last question matters more than people expect. Missed dates are normal in startups. If the agreement only feels fair when everything goes to plan, it is not a strong agreement.

If you are working out how to pay a technical cofounder, stress-test the deal before emotions and sunk time make changes harder. The right setup should survive a late launch, a rough month, and an honest disagreement without turning into a personal fight.

What to do next

A founder deal can look fair in a doc and still break once real bills show up. Before you sign anything, ask someone outside the founding team to challenge the plan. You want a second view from someone who is not tired, excited, or emotionally attached to the idea.

Put the deal through a few plain checks.

• Compare the cash part with your runway. If sales slip or fundraising takes longer, can you still pay it for at least a few months?
• Compare it with your hiring options. If the same budget buys a strong contractor or first engineer, the cofounder deal should give you more than extra coding hours.
• Compare the milestones with real work. Both sides should be able to point to a shipped result and say, "yes, that counts".
• Compare the vesting schedule with risk. If someone leaves early, the company should not lose a large chunk of ownership for unfinished work.

A small example makes this easier. Say you offer a low monthly payment plus equity that vests over four years, with more ownership unlocked after an MVP and first paying customers. That can work. But if your runway is only five months, even a small cash promise may be too much. And if "first paying customers" depends more on sales than product work, that milestone may feel unfair from day one.

This is where an experienced outsider earns their fee. A good fractional CTO or startup advisor can spot weak numbers, fuzzy milestones, and equity terms that look balanced only until stress hits. That kind of review is often cheaper than fixing a cofounder split after trust starts to crack.

If you still feel stuck on how to pay a technical cofounder, get that review before anyone signs. Oleg Sotnikov does this kind of work with founders and can help shape a fair plan without adding extra complexity. One careful pass now can save months of tension later.