# Should you keep doing it by hand, or build a system for it?

Doing it by hand costs nothing to start and grows with every hour it takes. A system costs a fixed price to build and a fee to run, buying back those hours once instead of spending them every week. Below a certain volume, doing it by hand still costs less; above it, the hours are the real bill.

Kicker: By hand or built
Checked: 2026-09-27

## Alternatives

- **By hand**: What it costs you, your founder’s hours; Fitted to how you work, yes; Who keeps it current, the founder, until they can’t
- **Subscriptions plus an assistant**: What it costs you, a seat per person, every month; Fitted to how you work, you work the way they allow; Who keeps it current, the vendors, on their roadmap
- **A dev shop or freelancer**: What it costs you, capital once; Fitted to how you work, at launch; Who keeps it current, nobody; it falls behind
- **A hire or an offshore team**: What it costs you, a salary, every month; Fitted to how you work, once they have learned it; Who keeps it current, the hire, while they stay
- **A system, built and run**: What it costs you, a fixed price, then a monthly run; Fitted to how you work, made for one company; Who keeps it current, us

## The contrast

By hand, every hour worked is an hour spent again next week.

A system holds the part that repeats, and a person still decides what needs judgement.

## What by hand actually costs

Nothing up front, which is exactly why it is the default. The cost shows up later, spread across every week it keeps happening: the person doing it, the person who could have been doing something else, and the version of the process that lives only in their head.

## Where the hours go missing

A founder who is also the one routing every request, chasing every follow-up and keeping the one record in their own head is a single point of failure with no name for it. The company runs on what they remember, and it stops the moment they are on a call, on leave, or gone.

## What a system takes off the list

The part that repeats: reading what comes in, sorting it, chasing what is waiting, keeping one record, and showing what is stuck. It does not replace the decisions. It removes the hours spent getting to the point where a decision is even possible.

## The honest trade

A system is a fixed price to build and a fee to run, against hours that would otherwise keep growing with the company. That trade only pays off once the hours are real and repeating. Before that point, by hand is not a failure of ambition. It is the correct answer.

## When the alternative is the right call

Keep doing it by hand while the volume is low and the process is still changing week to week. Building around a moving target fixes the wrong version of it.

Keep doing it by hand when almost every case needs a judgement call a system cannot make. A system prepares the case; a person still has to decide it.

Move to a system once the hours are steady, the steps have settled, and the same few decisions repeat often enough to be worth writing down.

## Dated record

- The craft retailer's outreach system still costs one person, one window a day: nothing goes out until they have read the queue (recorded 2026-08-25)

## Terms used here

- [Total cost of ownership](https://octyn.co/glossary/total-cost-of-ownership)

## Bears on

- [Operations systems](https://octyn.co/systems/operations)

## Related

- [Alternatives to hiring for operations](https://octyn.co/compare/alternatives-to-hiring-for-operations)
- [Hiring for the role, or building a system for the work](https://octyn.co/compare/hiring-vs-building-a-system)
- [Operations systems](https://octyn.co/systems/operations)

Canonical: https://octyn.co/compare/doing-it-by-hand-vs-a-system