How to Build a Startup Team Before You Can Afford One

Five ways to build a team without a salary, why equity is the most expensive option, who to bring in first, and how to test someone before you commit.

  • What building a startup team means before you have money
  • Why equity is the most expensive way to pay a team
  • Five ways to build a team without a salary
  • Who to bring into your team first
  • How to test someone before you give them equity
  • How much equity should an advisor get?
  • How to attract people when you cannot pay them
  • Where to find people before you can pay
  • Five mistakes that cost founders their cap table
  • Building a team without spending cash or equity

The share of new companies started by a single founder has doubled over the past decade, which means more people than ever are doing product, sales, design, and support in the same week while telling themselves the team comes after the money. What usually happens instead is that the money arrives late, the work compounds faster than one person can absorb, and the first real hire gets made in a panic rather than a plan.

What building a startup team means before you have money

A team is not a payroll. It is a group of people who are reliably accountable for something in your business, and payroll is only one of several ways to create that accountability.

Before revenue or funding, most founders assemble something closer to a constellation than a company. One or two people deeply committed, a few specialists who appear for defined pieces of work, and a handful who advise occasionally.

The distinction that matters: you are not trying to hire people. You are trying to buy accountability for specific outcomes, and there are at least five ways to do that.

Why equity is the most expensive way to pay a team

When founders cannot pay, they reach for equity, because it feels free at the moment of the offer. It is not free, it is simply deferred, and the data on how quickly it disappears is sobering.

Carta's Founder Ownership Report 2026, published in March, tracks that trajectory precisely across its platform data. By the time a company raises a seed round, the median founding team retains about 56 percent of its fully diluted equity, and by Series A that has fallen to 36 percent.

The number that should stop you is further along. By Series C, the median employee option pool sits at 16.8 percent while the median founding team holds 16.1 percent, meaning the people you hired collectively own more of the company than the people who started it.

That is the normal, healthy outcome of a company that worked. The report, available in full as Carta's founder ownership data , also found that about 36 percent of startups founded on Carta in 2025 were led by a solo founder, up from 31 percent the year before.

Read those two findings together and the lesson is practical rather than gloomy. More founders are starting alone, and the currency they reach for when they cannot pay is the most finite thing they own, so it should be the last instrument they use, not the first.

Five ways to build a team without a salary

Each of these creates accountability, and each costs something different. The skill is matching the instrument to the need rather than defaulting to whichever one is most familiar.

The pattern worth internalising is that permanence should track certainty. The less sure you are that a need is permanent, the further down that table you should be looking.

Who to bring into your team first

Sequence matters more than titles at this stage, and the order below holds for most early businesses regardless of sector.

  • Cover the thing that stops you selling. Whatever prevents you from putting the product in front of a buyer is the first gap to fill, whether that is design, engineering, or a working demo.
  • Cover the thing you are worst at that customers see. Internal weaknesses can wait. Anything a customer experiences cannot.
  • Cover the thing that would break if you disappeared for a week. Single points of failure are cheap to fix early and expensive to fix later.
  • Only then, cover the thing you dislike. Founders routinely invert this and hire away their least favourite task while the real bottleneck stays untouched.

Tip: write the outcome before the role. "Someone who can take us from ten demos a month to forty" is a brief. "A growth person" is a wish.

How to test someone before you give them equity

Never give equity to someone you have not worked with. The single most reliable protection against a bad early partnership is a small paid or exchanged project first, run properly.

What a good trial looks like:

  • Scoped to two weeks or less, with a defined deliverable
  • Real work that matters, not a hypothetical exercise
  • Clear expectations written down before it starts
  • Compensated in some form, whether money, exchange, or expertise back
  • Followed by an honest conversation about what it revealed

What you are actually testing: how they communicate when something goes wrong, whether they ask good questions or just accept the brief, how they handle feedback, and whether the work arrived when they said it would. Skill is the easiest thing to assess and the least likely to be the problem.

How much equity should an advisor get?

Advisor equity is where early founders most often overpay, usually because the ask arrives wrapped in flattery and there is no obvious benchmark to push back against.

Commonly cited ranges for advisors at the earliest stages sit well under one percent, frequently a fraction of that, and almost always vest over one to two years with a clear scope of what the advisor will actually do. Anything that looks like co-founder equity for a monthly call is a mistake you will still be paying for at Series B.

Three rules keep this clean. Put a vesting schedule on it, define the commitment in hours rather than in enthusiasm, and include a way to end it that does not require a difficult conversation.

Note that equity, vesting, and contractor classification carry real legal and tax consequences that vary by country. Nothing here is legal advice, and an early conversation with a lawyer costs far less than unwinding a cap table later.

How to attract people when you cannot pay them

This is the part most guides skip, and it is the part that actually determines whether any of the above works. People give their time to early companies for reasons that have nothing to do with the invoice.

  • Clarity. A founder who knows exactly what they need is dramatically easier to help than one who needs everything.
  • Momentum. People join things that are visibly moving. Ship something small and public before you ask.
  • Learning. Access to a problem, a market, or a technology someone wants experience in is genuine compensation.
  • Reputation. Work that will be visible, referenceable, and something they can point at afterwards.
  • Reciprocity. The most durable of all, because it is the only one where they get something concrete back.

The strongest professional relationships in most careers were never transactional in the first place, which is the argument made at length in the piece on unpaid professional relationships , and it applies directly to how early teams actually form.

Where to find people before you can pay

Cold outreach to strangers is the least effective route and the one most founders try first. The people who join early companies almost always come from a shorter list.

  • People who have already seen your work. Former colleagues, clients, and collaborators need no convincing about whether you deliver.
  • Communities built around the problem. Not startup communities, but the places where people with the specific skill already gather to talk about the craft.
  • People who wrote about it. Anyone publishing thoughtfully on your problem has already declared their interest publicly.
  • Second-degree introductions. One warm introduction outperforms fifty cold messages, and the ask should name the exact piece of work.
  • Exchange networks. Places where specialists are already open to bounded work in return for something other than a salary.

Tip: the message that works names one specific task, one timeframe, and what they get back. The message that fails asks whether someone wants to "grab a call about an exciting opportunity."

Five mistakes that cost founders their cap table

  • Giving co-founder equity to a first employee. The title is flattering and the equity is permanent. If the person is filling a role rather than sharing the risk, they are an early hire, and that is not an insult.
  • No vesting, or vesting with no cliff. Someone who leaves in month three should not keep years of ownership. A standard schedule with a one year cliff exists precisely because early partnerships fail often.
  • Paying in equity for work that cash could buy. Equity is for people whose upside depends on the company's outcome. A logo, a landing page, or a two week build is not that.
  • Hiring your friends by default. Sometimes it works. The question to answer honestly first is whether you could give this person hard feedback, and whether you could end it if you had to.
  • Waiting for funding to start building the team. The relationships that make hiring fast later are built now, through small pieces of real work with people you might one day want full time.

Building a team without spending cash or equity

Every instrument above costs you one of two finite things, and equity is the one you can never get back. That is the specific problem BEXHUB was built around.

Members bring their expertise to each other through collaborations settled in BEX, so the designer, developer, or marketer you need for a defined piece of work can be brought in without touching your runway and without issuing a single share. The cap table stays exactly as it was, which matters most in precisely the period when you are least certain what the company will become.

It also functions as a low-risk audition at scale. Working with several specialists on bounded projects tells you far more about who you would want permanently than any interview process, and the mechanics of that are covered in how skill exchange works . Members can also work in money on any listing with zero commission, so the choice of how to settle stays yours on every project.

Frequently Asked Questions

How much equity should a co-founder get?
There is no correct number, and the honest answer depends on timing, contribution, risk taken, and what each person is giving up. Carta's data shows equal splits becoming more common but still a minority of teams, and whatever you decide should be documented with vesting from day one.
How much equity does an advisor get?
Far less than most first-time founders expect, typically a fraction of a percent at the earliest stages, vesting over one to two years against a defined commitment. If someone asks for a percentage that sounds like a founder's stake, that is a signal rather than a negotiation.
Can I hire someone with equity only?
You can, but be careful. Equity-only arrangements attract people who cannot afford to be wrong about you, they create expectations that are hard to reset, and in many countries they carry employment and tax implications that founders discover too late.
What is the difference between a co-founder and a first employee?
Risk and timing. A co-founder shares the existential risk of the company failing and is usually there before there is anything to join. A first employee joins something that already exists, however small, and is compensated rather than exposed.
How do I find people willing to work with me before I can pay?
Start with people who already know your work, be specific about the exact piece you need rather than asking for general help, and offer something concrete in return, whether that is your own expertise, access, learning, or visible credit.
How do I find a technical co-founder?
Start from people who have already seen you work rather than from strangers, and run a small real project together before either of you uses the word co-founder. The most reliable technical co-founders were collaborators first, and the arrangement was named afterwards.
Should I use contractors or make a hire?
Use contractors while the need is uncertain, bounded, or specialised, and hire when the work is continuous and the role is clear enough to write down. Most early companies convert too slowly on the first and too quickly on the second.