Startups and Team Building: Ten Lessons From a First-Generation Founder

It’s very important to start a new venture with the right set of mindset, passion, execution skills and people.

Those four are like the individual wheels of a car. Any one of them goes out of sync and the chances of a fatal learning experience rise sharply. Everything that happens before an entrepreneur successfully creates value in the ecosystem is the product of decisions that were right or wrong — which is essentially, and indirectly, what we end up calling learnings.

As much as I have seen, and as a first-generation entrepreneur myself, startups are not only about the destination. They are equally about the journey and the people in it. A good idea and a good team both matter, and the second one is much harder to get right than the first.

These are ten lessons I have come across so far. Each is stated plainly first, then what it actually means in practice — because a lesson on its own is easy to nod at and hard to act on.

1. Stay connected to the goal, even though the path holds equal importance

The lesson: stay connected to the goal, even though the path holds equal importance.

Both halves of that matter, and founders usually drop one of them.

Drop the goal and you get a company that is very busy. Every week has work in it, every quarter has activity, and after two years nobody can say what was actually built. This is the more common failure, because the path is made of urgent things and the goal never is.

Drop the path and you get the opposite: a founder so attached to a specific destination that they cannot hear what the market is telling them along the way. The destination they defend is usually the one they imagined before they had customers.

The practical version is a habit rather than a strategy. Write the goal down where you will actually see it, and once a month ask one question of the last four weeks: did this move us toward that, or was it just work? Most months the honest answer is partly no, and knowing which part is what stops a year disappearing.

2. Be honest and strict with your team — those are the same thing

The lesson: be honest as well as strict towards work with your team. This does not mean you have to be rude.

People conflate strictness with rudeness because they have mostly seen them together. They are unrelated. Rudeness is about how you speak to someone. Strictness is about what you accept.

The failure mode in a young company is almost never the rude founder — it is the founder who is so anxious to keep a small team happy that nothing is ever called substandard. Work is quietly redone at night instead of being sent back. Deadlines slip without being named. The founder absorbs it, gets resentful, and eventually the resentment arrives all at once in a conversation nobody saw coming.

What being strict without being rude actually looks like: the standard is stated before the work starts, not after it arrives. The feedback is about the work rather than the person. It is given immediately rather than saved up. And it is the same standard for everyone, including the founder — a rule you break yourself is not a standard, it is a preference.

Being honest early is a kindness. Being vague for six months and then frustrated is not.

3. A good idea fails on the wrong people faster than on the wrong market

The lesson: the idea may fail if you choose the wrong set of people, or do not put the effort in the right way.

This is worth being precise about, because the usual startup story blames the market.

An idea is a hypothesis. Testing it needs execution, and execution is people. With the wrong people the test never runs properly, so you do not even learn whether the idea was any good — you spend the money and end up with no information. That is worse than a clean failure, because a clean failure at least tells you something.

The other half — putting effort in the right way — is about direction rather than volume. Effort spent on the part of the business that is not currently the constraint feels productive and changes nothing. In any given month there is usually one thing holding the company back. Working on anything else is a rest, however tiring it is.

4. For the first twenty hires, never hire someone whose reason is the hike

The lesson: for the first 20 hires, do not — I repeat, do not — onboard people who are shifting just because they are getting a good hike.

These are the most harmful people to the system in the long run, and one way or another every stakeholder eventually realises it.

The reasoning is simple. If money brought them happiness, they would never have wanted to jump ship and build something of their own. Someone who moved for a 30% raise will move again for the next one, and in a young company that departure is not a vacancy — it takes the context with it, because nothing has been written down yet.

There is a second, quieter cost. A person who joined for the number treats the job as an exchange: this much money for this much work. That is entirely reasonable and completely wrong for the first twenty people, because at that size nobody’s job has edges. The work that decides whether the company survives is nearly always the work that was not in anyone’s description.

Your core team should be putting in the same effort you do. If they are not, you will feel left out of your own company — and be very selective about who you start the journey with, because early hires set the standard that everybody after them copies.

None of this means underpaying people. Pay fairly. Just do not let the pay be the reason.

5. Moving people out is a decision, not a cruelty

The lesson: don’t feel bad if you have to act logically about bringing people in and out of the ecosystem.

It is a sad reality, but there are many people who do everything in their power to worry about work rather than to do the work. Those people can rot the system, and for a while they can stall the thing you are trying to build.

The distinction is worth learning to spot, because it is not obvious from the outside. Someone worrying about work is visibly busy: long updates, detailed objections, meetings about the meeting, a clear account of why something could not be finished. Someone doing the work is often quieter and finishes things. In a small team the first pattern spreads, because it looks like diligence and it is far more comfortable than delivery.

Two things make this decision less painful when it comes. Make it early — the cost of waiting falls entirely on the people who are delivering, and they notice long before you act. And separate the person from the fit: most people who are wrong for a five-person company are perfectly good at a hundred-person one. Saying that honestly, and saying it kindly, is not a contradiction.

6. Experiment at the edges, not at the centre

The lesson: don’t be afraid to experiment with something new, or expand your services or product portfolio — it should not go completely off track from the idea.

Genuinely innovating, or building and selling something over the top of what you already do, can be very helpful in the long run. The constraint in the second half of that sentence is the whole lesson.

An experiment adjacent to what you already do reuses your customers, your credibility and your delivery capability, so it is cheap to run and quick to read. An experiment far from what you do reuses nothing, which means it is a second startup being funded by the first — and the first is not usually strong enough to fund anything.

The useful test before starting anything new: which of our existing assets does this borrow? If the honest answer is none, it is not an expansion, it is a distraction with a business plan.

7. Don’t build on makeshift tech, and put a date on everything

The lesson: don’t waste time with makeshift tech or any other gigs. Always define what you want and when you want it.

Makeshift solutions are not cheap; they are borrowed. The interest is paid later by whoever has to work around them, and the payment is usually due at exactly the wrong moment — when you finally have volume and the thing that was “fine for now” stops being fine.

The second half — define what and when — is the part that gets skipped. A requirement without a date is a wish, and a wish cannot slip, so nobody notices it has. The moment something goes off timeline, look for a solution immediately, because more delay only puts the goal further away. A week acknowledged early is a week; a week noticed late is usually a month.

Where the work is repetitive rather than judgemental, automating it is usually cheaper than hiring for it — and it does not resign.

8. Hire young talent, but build the induction kit before they arrive

The lesson: hire preferably young talent, and before bringing them into the ecosystem keep your induction and training toolkit ready.

I am sure almost nobody thinks about this, but it makes life really very easy when training and dealing with a fresh mind.

Here is why the order matters so much. Without a kit, every new person is trained by interruption — they ask, someone stops what they were doing, an answer gets given once and is never written down. The company pays that cost again for every single hire, and the answers drift, because ten people explaining something from memory produce ten slightly different versions of it.

The kit does not need to be elaborate. What we do and for whom, how a piece of work goes from request to delivered, where things live, who decides what, and the five questions every new joiner has asked so far. It takes a couple of days to write, and the second hire pays for it.

Fresh graduates may look like a headache today, but over the long run they become the first, second and third level pillars of the company. You do not want to buy a pillar and just place it there as if you were assembling a modular building — pillars that hold weight are grown in place, which is exactly what the training kit is for.

9. Keep exploring what the market is doing

The lesson: keep exploring what’s happening in the market. There is always room for new learnings, and you should never skip this.

The danger for a founder is not ignorance, it is being one cycle behind while feeling fully informed. Internal work is absorbing, and a company can spend two years becoming excellent at something the market has quietly stopped paying for.

This does not require a research function. It requires a small, regular habit: talk to people who are not your customers, look at what your competitors have changed rather than what they say, and pay attention to the tools your own team keeps asking for — that last one is usually the earliest signal you get, and it is free.

The skills that actually matter in the age of AI is a view of where that market is currently moving.

10. Protect the founder, because the company cannot outlast you

The lesson: focus on yourself, family, health, mental health and wealth. Any order is fine — these specifics just need to be ingredients.

This reads like an afterthought in most startup writing, and it is the one lesson with a hard mechanical justification: in a company this small, you are a single point of failure. The founder’s capacity is genuinely a business asset, and it is the only one with no redundancy behind it.

Two practical notes. Family and health are the two things that give way silently — nothing announces that they are being spent, and by the time there is a symptom the debt is large. And personal wealth is not greed here; a founder with no personal buffer makes decisions from fear, and fear is an expensive way to run a company.

A daily routine that actually sticks is the mechanism most founders skip here, because it is the least urgent thing on any given day and the most compounding one over five years.

And one that sits underneath all ten: networking

Networking plays a good role, and it is worth being deliberate about. Part of that is dropping the bad ghost that makes you say the wrong things when they are not required — a positive attitude is always appreciated, and in a small market it is remembered.

The reason this belongs with team building rather than sales: the people you meet now are the people you will hire, be hired by, be introduced by and be vouched for by later. Reputation in a small industry travels far ahead of you and is very hard to correct once it has set. There is more on this in networking: the one lesson I wish I’d learned earlier.

How these connect

Read separately these are ten observations. Read together they say one thing: in the first two years, the team is the company. The idea can be adjusted, the product can be rebuilt, the market can be re-entered — but all of that is done by whoever is in the room, and who is in the room is the one decision that is genuinely hard to reverse.

That is why the hiring lessons carry the most weight, why the induction kit matters more than it looks, and why moving the wrong person out early is a kindness to everyone still delivering. It is also why the founder’s own health belongs on a list about team building: the person deciding all of the above is part of the team, and the only part with no cover.

The same mechanism runs through brand — a company’s brand is just the accumulated evidence of how its people behave, which is why brand building starts on day one rather than when you have a marketing budget.

FAQs

What matters most when starting a new venture?

Mindset, passion, execution skills and people — and they work like the four wheels of a car. Any one of them going out of sync raises the chance of a fatal learning experience. A good business idea and a good team both matter, and almost everything that happens on the way to creating value is the product of decisions that later read as learnings.

Who should a startup avoid hiring early on?

People who are shifting roles purely because they are getting a good hike. For the first twenty hires especially, those joiners tend to be the most harmful to the system in the long run, and one way or another every stakeholder realises it. If money brought them happiness, they would never have wanted to jump ship and build something of their own.

Should a startup hire freshers or experienced people?

Young talent is worth hiring, provided the induction and training toolkit is ready before anyone is brought into the ecosystem. Almost nobody thinks about that in advance, and it is what makes training a fresh mind easy rather than painful. Fresh graduates can look like a headache today and become the first, second or third level pillars of the company later.

When should a founder move someone out of the team?

When it becomes clear they are doing everything in their power to worry about work rather than to do the work. Acting logically about bringing people in and out of the ecosystem is a sad reality rather than a cruelty — those people can rot the system, and for a while they can stall what you are trying to build.

How do you avoid losing time in the early stage?

Do not waste it on makeshift tech or other gigs. Define what you want and when you want it, and the moment something goes off timeline, look for a solution immediately, because more delay only puts the goal further away. Where the work is repetitive rather than judgemental, automating it is usually cheaper than hiring for it.

Is being strict with a small team a bad idea?

No — being strict and being rude are different things. Strictness is about what you accept; rudeness is about how you speak to people. The common failure in a young company is the opposite of strictness: nothing is ever called substandard, the founder quietly absorbs it, and the frustration eventually arrives all at once.

Key takeaways

• Mindset, passion, execution and people are four wheels. One out of sync is enough.

• For the first twenty hires, never hire someone whose reason for joining is the raise. Pay fairly; just don’t let the pay be the reason.

• Write the induction and training kit before the first young hire arrives — the second one pays for it.

• Move the wrong person out early. The cost of waiting is paid entirely by the people still delivering.

• Experiment at the edges of what you already do, so the experiment borrows customers, credibility and capability.

• Give every requirement a date, because a requirement without one cannot slip and so nobody notices that it has.

• The founder’s health and buffer are business assets with no redundancy behind them.

Always remember: your passion brought you where you are today. Don’t let an external factor come in and change what you set out to build. Go for it, and don’t stop until it is done as you wanted it — or as the customers wanted it.

Related reading: brand building: five lessons from working inside SMEs, networking: the one lesson I wish I’d learned earlier, and a daily routine that actually sticks.