What operations means in an early tech startup.

In a large company, operations is a department. In a tech startup of five people, it is a set of jobs that someone has to do: paying suppliers, onboarding new team members, managing tools and access, keeping records, running meetings and making sure promises to customers are kept. If nobody owns these jobs, they fall to the founder, usually late at night.

Operations matters for three reasons. It saves time, because repeated tasks get done the same way without rethinking them. It reduces risk, because important things (renewals, filings, backups, access removal) do not depend on memory. And it builds value, because a business that runs without its founder is easier to fund, scale or sell. Investors and acquirers will test this in due diligence.

What operations covers at this stage

Finance, people and legal each have their own playbooks: see finance, people and legal. Operations connects them, making sure the processes between functions run smoothly.

Step by step: getting started

1. Name an owner. One person is accountable for operations, even if it is a quarter of their time. In most early teams this is a co-founder.
2. List what keeps breaking. Spend a week noting every time something is forgotten, done twice, delayed or depends on one person. This list is your operations backlog.
3. Write a company calendar of fixed dates. Confirmation statement, annual accounts, VAT returns if registered, payroll dates, insurance renewals, software renewals and domain renewals. Put reminders well ahead of each one. The upon incorporation checklist covers the statutory basics.
4. Create a single source of truth. One shared drive or wiki with a clear folder structure: company records, contracts, policies, processes, finance, people. Everything important lives there, not in personal inboxes.
5. Fix the top three. Pick the three items from your backlog that cost the most time or risk and fix them properly before moving on.

How much operations is enough

A useful test is to ask what would happen if the person who usually does a task were unavailable for a month. If the answer is “it would not get done” or “we would get it wrong”, that task needs at least a checklist and a second person who has done it. If the answer is “someone would work it out from the shared drive”, you probably have enough structure for now. As a rule of thumb, add process only where something has gone wrong twice or where the cost of getting it wrong once is high, such as payroll, customer data or statutory filings. Everything else can stay informal until the team grows.

A worked example

Halden Labs, a fictional Nottingham tech startup with six people, made software for veterinary practices. Its co-founders kept company documents in personal email, and a key hosting contract auto-renewed on worse terms because nobody noticed the notice period.

One co-founder took ownership of operations for one day a week. She created a shared drive, a calendar of fixed dates and a contract register. Within a month, the team knew where everything was, and the next renewal was renegotiated three months early.

Common mistakes

• Treating operations as admin. It is a lever on speed and risk, not just paperwork.
• Over-engineering early. A ten-person company does not need an enterprise process manual.
• Nobody accountable. Shared ownership usually means no ownership.
• Fixing symptoms. Chasing the same late invoice every month instead of fixing the process that creates it.

What to measure

• Number of open items on the operations backlog, and how many were closed this month.
• Missed deadlines or renewals (aim for none).
• Hours per week the founding team spends on operational tasks.
• Share of core processes documented.