Built by one person, in Australia

Why it exists

“I’ve worked across legal, politics, engineering and tech; every CRM I used forced my team to work around its structure. After years of bending our processes to fit someone else’s template, I built Streams to work the other way around.”

The specific thing that kept happening was smaller than the quote makes it sound. Everyone knew the process. The process was written down somewhere. And work still moved on without the certificate, without the approval, without the invoice, because nothing in any of the tools could tell the difference between work being finished and somebody saying it was.

So that is the one thing this does that the alternatives do not. A job does not leave a stage until the stage has what it needs. Not a reminder. Not a report on Friday. The record stays where it is, and the person is told which fields are missing.

What it is not trying to be

A small product is only useful if it is honest about its edges. These are ours, and they are choices rather than a roadmap.

• Not a CRM

  There is a contact book, because jobs belong to people. But nobody has bought this to chase a sales pipeline, and building for that would make it worse at the thing it is good at.

• Not an ERP

  No inventory, no bills of materials, no stock levels, and none planned. If you need those, keep the system that has them and run the job alongside it.

• Not a project planner

  No task dependencies, no critical path, no resource levelling. This is for repeatable work where every job follows the same stages.

• Not certified

  Not ISO 27001 and not SOC 2. The infrastructure providers hold those, which is a different thing, and we will not blur the two.

Where your data lives

Everything an organisation stores is held in Australia. Records, fields, notes, the audit log, uploaded files, quote and invoice PDFs and the database backups are all in Sydney, and document scanning runs on our own service in Sydney rather than being sent to an overseas provider.

Some things do leave when you trigger them: sending email, sending SMS, the AI features and payments. We list exactly which, and who handles them, rather than summarising it away.

How it is built

Everything that ships is written up on the changelog, including the unglamorous parts. There is a free plan with every feature switched on rather than a trial that expires, because the only way to know whether a process tool fits your process is to put a real job through it.

Prices can change, but never with less than 30 days notice by email and never for a month already paid for, and you can leave before an increase starts with no exit fee. Cutting what a plan includes counts as a price change under the same rule.