Building Your Startup Team (and Yourself as a Founder)

The app will not run your business

Here is something founders do not like to hear: in the AI era, anyone can get software built. If an app were enough, every app would be a business. It is not. The thing that separates a living business from an abandoned one is a team that can sell, deliver and fix problems every single day, including the days you are sick, tired or travelling.

Ask yourself honestly:

• If I disappeared for two weeks, would orders still be taken, delivered and paid?
• Who, by name, is responsible for revenue this month?
• Do I have a plan, and the people, to survive the first six months after launch?

If the answer to all three is "me", this article is for you.

Part 1: Building yourself

You are the first employee and, for a while, the most important one. Most first-time founders are strong in one area (technology, or operations, or a particular industry) and weak in others. That is normal. Pretending otherwise is expensive.

Skills worth building early

Rich or king?

Harvard professor Noam Wasserman's research, summarised in the Harvard Business Review article "The Founder's Dilemma" (2008), describes a trade-off many founders face: decisions that build a more valuable company (bringing in co-founders, hires and investors) often mean giving up some control. In his framing, you are often choosing between being "rich" and being "king". Neither choice is wrong, but you should make it deliberately rather than by accident.

Part 2: Your first hires for an on-demand business

A ride, delivery or services marketplace is an operations business with an app on top. Your first team should reflect that. The exact order depends on your model, but these roles come up again and again.

1. Operations lead

Owns the daily running of the service: dispatch, quality checks, provider schedules, incidents, refunds and the weekly numbers. In many on-demand startups this is the most important early hire after the founders. Look for someone who has run a shift, a branch or a logistics team, not just someone who has read about it.

2. Supply or partner manager

Recruits, onboards, trains and keeps drivers, riders, restaurants or service providers. They handle documents and checks, solve provider complaints and watch provider churn. If your marketplace has no supply, it has nothing to sell.

3. Customer support

Answers chats and calls, fixes order problems, issues refunds within agreed limits and reports patterns to operations. At the start, founders should do support themselves for a while; there is no faster way to learn what is broken. Then hire, and write down what you learned.

4. Marketing and growth

Runs launch campaigns, referrals, partnerships, social media and store listings, and reports cost per customer by channel. In a small startup this person must be comfortable doing both creative work and spreadsheets.

5. Product owner

Someone must decide what the app should do next, write clear requests for developers and test releases. This can be a founder at first. It does not need to be a full engineering team if you use a white-label platform or an external development partner.

A simple first-year sequence

Every business is different, but a common pattern for a small on-demand launch looks like this. Before launch, the founders do sales, supply recruitment and support themselves, with a development partner handling the app. Around launch, the first full-time hire is usually operations, followed by someone dedicated to supply. As order volume grows, support moves from the founders to a dedicated person or small shift team, and marketing becomes a role of its own once you know which channels work. Hire against real workload, not against an organisation chart you drew before launch.

In-house, agency or freelancers?

A useful rule: keep the work that touches customers and providers every day in-house. Outsource work that is specialised, occasional or easy to specify.

Be careful with how you classify people. In the United States, for example, the IRS looks at behavioural control, financial control and the type of relationship to decide whether a worker is an employee or an independent contractor. Other countries have their own tests, and the rules for drivers and riders are under active debate in many places. Get local advice before you build your team on contractors.

Hire people who can run the business without you

The goal of your first year is not to do everything well yourself. It is to build a business that works when you are not in the room.

Write SOPs (standard operating procedures)

An SOP is a short, plain document that explains how a task is done: onboarding a driver, handling a late order, issuing a refund, closing the day's cash. Good SOPs:

• Fit on one or two pages
• Use numbered steps and screenshots
• Say who owns the task and what to do when something unusual happens
• Are updated whenever the process changes

Delegate outcomes, but stay close to the details

Delegation is not disappearing. Paul Graham's 2024 essay "Founder Mode" argues that the standard advice to "hire good people and give them room" can go wrong for founders, and that the best founders stay closely involved in the details while their companies grow. The practical balance for a small startup: give people clear ownership and targets, then review the numbers and a sample of real orders with them every week.

Build simple systems

• A shared dashboard with the same numbers every week
• A shared inbox or ticket tool for support, not personal phones
• A written escalation path for safety incidents
• Access controls, so nobody leaves with the only password

Culture: what you tolerate becomes the culture

You do not need a culture deck. You need a few rules you actually follow:

• Customers and providers are treated with respect, including when they are wrong.
• Bad news travels fast. People are thanked for reporting problems, not punished.
• Numbers are shared. Everyone knows the weekly orders, complaints and cash position at the level they need.
• Promises are kept, especially payouts to providers. Late payouts destroy supply faster than any competitor.

Equity basics (get advice, but know the basics)

Equity disagreements can end a company. Wasserman's research, discussed in Harvard Business School's Working Knowledge, found that 73% of founding teams in his data settled their equity split within the first month, and that around a third split equity equally, often to avoid a hard conversation. Splits made that early cannot reflect how each person will actually contribute.

Basics to discuss with a lawyer:

• Put it in writing. Who owns what, who does what, and what happens if someone leaves.
• Use vesting. Founders and early employees earn their shares over time. A common structure is four years with a one-year cliff, though terms vary.
• Know the tax rules where you incorporate. In the US, founders receiving restricted stock often consider a Section 83(b) election, which the IRS says must be filed no later than 30 days after the property is transferred. Missing the deadline cannot usually be fixed.
• Keep an option pool in mind if you plan to give equity to future key hires.

Burnout is a business risk

The World Health Organization describes burn-out, in ICD-11, as a syndrome resulting from chronic workplace stress that has not been successfully managed. It is characterised by exhaustion, mental distance or cynicism about one's job, and reduced professional efficacy. WHO classifies it as an occupational phenomenon, not a medical condition.

For a founder of an on-demand business that runs late at night and on weekends, this is a real risk. Protect yourself and your team:

• Set on-call rotations instead of everyone always being available.
• Take at least one day a week fully off, and make sure someone else can cover it.
• Watch for cynicism and exhaustion in yourself as seriously as you watch your cash.
• If you are struggling, talk to someone you trust or a professional. It is not weakness; it is maintenance.

Your team-building checklist

• I know my own weak areas and have a plan to cover each one.
• One named person is accountable for revenue every month.
• An operations lead (or a founder, for now) owns daily service quality.
• Someone owns supply: recruiting, onboarding and keeping providers.
• Support runs from a shared tool, not personal phones.
• The top ten recurring tasks have written SOPs.
• I have decided what stays in-house and what goes to partners or freelancers.
• Worker classification has been checked with local advice.
• Founder and early-employee equity is in writing, with vesting.
• I have a personal plan to avoid burnout, and someone who can cover for me.

Where a development partner fits

A good technology partner can take the app off your plate so your team can focus on selling and operating. That is the role Joldisoft plays for founders, from our engineering office in Dhaka. But I will be straight with you: we do not build for everyone. We look for founders who have validated demand, a sales and marketing plan, a budget for operations and runway, and a person accountable for running the business. We want long-term partners whose businesses survive, not one-off projects where the client's money is wasted. Build your team first. Then let us build the software that helps them.