# Should you stay on subscriptions and add an assistant, or build a system?

A subscription stack plus an assistant costs a seat per person every month, for someone else's way of working. A system costs a fixed price once and a fee to run, fitted to how your company works. Subscriptions win while your process is still settling; a system wins once it has and the seats keep adding up.

Kicker: Subscriptions 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

A subscription stack charges by the seat, for a way of working the vendor chose.

A system is priced once, then run for a fee, fitted to how your company works.

## What the stack actually costs

A seat every month, per person, for as long as the person and the subscription both last. Add an assistant reading across several inboxes and several subscriptions, and the cost is not the seats. It is the time spent moving information between products that were never built to talk to each other.

## What a system replaces

The moving-between-products part. A system reads what comes in, keeps one record, and does the routing a person was doing by hand between browser tabs. The subscriptions can often stay; what changes is who is doing the joining-up.

## The honest trade

The stack is flexible because someone else maintains it, and that same flexibility is why it never quite fits. A system fits because it is built around your process, and fitting it is the cost: a fixed price up front, then a fee to keep it running and current.

## When the stack is still the right call

Early, and for work that is genuinely the same as everyone else's. Payroll, accounting, ticketing and email are worth buying, not building, and no assistant changes that arithmetic.

## When the alternative is the right call

Stay on subscriptions plus an assistant while you are still working out how the process should go. A system fitted to a process that is still moving fixes the wrong one in place.

Stay on subscriptions when the work is the same as everyone else's: done the same way by every company your size, and a product with many customers has already met the edge cases you have not.

Add a person, not a system, when what is missing is judgement rather than a repeatable step.

## Bears on

- [Growth systems](https://octyn.co/systems/growth)

## Related

- [A dev shop, or an operating partner who stays](https://octyn.co/compare/dev-shop-vs-an-operating-partner)
- [Alternatives to hiring for operations](https://octyn.co/compare/alternatives-to-hiring-for-operations)
- [Growth systems](https://octyn.co/systems/growth)

Canonical: https://octyn.co/compare/saas-stack-and-an-assistant-vs-a-system