StreamsApp runs alongside other tools: it imports CSV and has an inbound API. It is built for jobs that end in a quote and an invoice, with the invoice part of the record.

Can I document each stage the way a checklist does?

Yes. Every stage carries its own rich documentation, shown on the stage while the work is being done. You can have the AI draft a starter version from the stage name and its fields, then edit it.

Do you have conditional steps?

No. Every job in a stream follows the same stages today. Conditional branching is not built, and we will not pretend otherwise. Variable work is handled by raising sub-records against a job rather than by branching the stages.

StreamsApp compared with Process Street

The closest thing to what we do

Process Street starts from the same idea we do, so this comparison is narrower than the others.

Side by side

Product features change. Check anything here against Process Street before you decide.

Does the process enforce itself?

Process Street: Yes. This is the shared premise.
StreamsApp: Yes, stage by stage where you switch it on. Required fields, and gates on whether an action genuinely happened.

Can the job be quoted and invoiced from inside it?

Process Street: No. That is a different system, linked.
StreamsApp: Built in, with GST, online acceptance, and sync to Xero, MYOB or QuickBooks.

Can a job raise a variable number of sub-items against itself?

Process Street: Not as a first-class idea.
StreamsApp: Yes. Claims, variations and defects raised against a parent, which stays open.

Where is the data held?

Process Street: Check their current terms for your region.
StreamsApp: Australia. Records, files and backups in Sydney, and document scanning too.

What does it cost to start?

Process Street: Check their current pricing.
StreamsApp: Free plan, no credit card, every plugin switched on.

The difference is the end of the job

A checklist ends when the checklist ends. A job ends when somebody has been billed and has paid.

That is the practical difference. Because quotes and invoices are part of the record here, the last stages of a process can depend on them: this job cannot close until an invoice has been raised, or until it has been paid in full. Only real work counts, so a draft or a voided invoice does not satisfy it.

If the processes you want to enforce end in an invoice, that matters.

Where your data sits

Everything stored here is in Australia. Records, fields, notes, the audit log, uploaded files, quote and invoice PDFs and database backups are all in Sydney, and document scanning runs on our own service in Sydney rather than an overseas AI provider.

Some things do leave when you trigger them, and we say exactly which on our security page: sending email, sending SMS, the AI features and payments. If you never use those, nothing you store leaves the country.

We are not ISO 27001 certified and not SOC 2 audited, and we will not imply otherwise. If that is a hard requirement, it is worth knowing now rather than after a procurement review.

How much of this you switch on is up to you

Nothing here is required until you say so. A new stream starts with no requirements at all, and a stage that asks for nothing lets a job straight through.

Most businesses end up running both kinds side by side. A compliance job can insist on the slab certificate, so it cannot reach the frame stage without one. A sales enquiry in the same account can have nothing required at all, because chasing a lead is not a process and a rule there is only friction.

That is the real difference. Not that the software is strict, but that you get to decide where it is, one stage at a time, and change your mind later without starting again.

Questions

Can I use both?: StreamsApp runs alongside other tools: it imports CSV and has an inbound API. It is built for jobs that end in a quote and an invoice, with the invoice part of the record.
Can I document each stage the way a checklist does?: Yes. Every stage carries its own rich documentation, shown on the stage while the work is being done. You can have the AI draft a starter version from the stage name and its fields, then edit it.
Do you have conditional steps?: No. Every job in a stream follows the same stages today. Conditional branching is not built, and we will not pretend otherwise. Variable work is handled by raising sub-records against a job rather than by branching the stages.

See it for your kind of work

Other comparisons

Try it against your own process

The free plan is enough to put a real job through end to end and find out for yourself. No credit card, and nothing to uninstall if it is not for you.

Get started free