StreamsCRM
The CRM you build one stream at a time
Most CRMs give you one shape: contacts, deals and a pipeline that ends at Closed Won. StreamsApp gives every process its own stream, with its own steps, fields and rules, and one record follows the customer through all of them.
A sales pipeline is a stream. So is onboarding a new client, a repair job, or a progress claim against a build. They sit in one workspace, they share one set of contacts, and a step can refuse to let a record move on until it has what it needs.
Why a CRM so often feels like a fight
Everything has to look like a deal
A CRM is built around one object: the deal, moving down one pipeline to Closed Won. The work that happens after the sale, the job itself, the variation, the warranty claim, has to be squeezed into custom objects or kept somewhere else.
So there is always a second tool
The sale is in the CRM, the job is in a spreadsheet or a project board, and the customer history is split between them. Someone copies the details across, and the copy is where mistakes start.
And the status is whatever someone typed
A stage is a dropdown. Anyone can move a deal on, whether or not the proposal went out or the deposit came in. The pipeline report looks tidy and says nothing about whether the work was done.
Every process gets its own stream
In CRM terms, a stream is a pipeline that can be any shape. You choose its steps, the fields a record carries, what each step asks for, and the written instructions your team sees at each one. There is no limit on how many you run, on any plan.
These four come from the templates you can start from, and they share nothing but the workspace:
Sales
10 fields, 5 gated steps- Lead
- Qualified
- Proposal Sent
- Negotiation
- Closed Won
- Invoiced
- Paid
Repair Jobs
12 fields, 7 gated steps- Intake
- Quoted
- Approved
- In Repair
- Ready for Pickup
- Invoiced
- Paid
New Hire Onboarding
8 fields, 5 gated steps- Offer Sent
- Offer Accepted
- Pre-Boarding
- Day One
- 30-Day Review
Support Tickets
6 fields, 3 gated steps- New
- Triaged
- In Progress
- Pending Customer
- Resolved
One record follows the customer through all of them
One stream is marked as your Contacts, and every other stream points at it with a contact field, so a customer is typed in once. When a won deal becomes a job, the record is carried into the next stream with Copy & link, and the Full Record view reads the whole journey as one history: every stream it passed through, every field, every message.
Some things are not one-to-one. A build can have three progress claims or seven. A sub-stream lets you raise any number of them against the parent record, each with its own steps and gates, with the parent still live and a running total on it. A single pipeline cannot model that at all.
Nothing moves on until the step has what it needs
Any field can be required at any step. Until it is filled, the record stays where it is and the person is told what is missing. The proposal is attached before a deal reaches Negotiation. The invoice is raised before a job can close. Nothing is required until you say so, so a sales enquiry can move freely while a compliance step insists on evidence.
Built in, not bolted on
- Contacts, groups and CSV import, with a contact field any stream can point at
- Custom fields: text, number, date, file, dropdown, email, phone, user, notes and more
- Automations that email the customer or a colleague when a record reaches a step
- Email, SMS and WhatsApp from the record, with replies landing back on it
- Quotes with an accept link, invoices with GST, and sync to Xero, MYOB or QuickBooks
- Notes, tasks, step targets with an overdue digest, and a full audit trail
- The Lake: analytics across every stream, and plain-English questions about your records
What it does not have
- A customer portal. Customers reply by email, SMS or WhatsApp, and accept quotes from a link, but they do not log in.
- Marketing sequences, lead scoring or a dialer. This is for running customers through your process, not for outbound campaigns.
- Native phone apps. The whole app works in a phone browser on every plan, with nothing to install.
Priced per organisation, not per seat
Free for two users, with every feature switched on and no credit card. Paid plans start at $29 a month for five users and $79 a month for twenty, in Australian dollars, with no seat minimum. See pricing.
Everything you store is held in Sydney. How data is handled.
Questions
- Is StreamsApp a CRM?
- Yes. It has contacts, custom fields, stages, automations, email and SMS from the record, quotes, invoices and accounting sync. What is different is the shape: instead of one pipeline of deals, every process you run gets its own stream.
- Can I run more than one pipeline?
- As many as you like, on every plan including the free one. Each stream has its own steps, fields, documentation and rules, so a sales pipeline and a repair job do not have to share a shape.
- Does it replace Monday CRM?
- For a small team whose customers go through a set process, often yes, and it has been chosen over Monday CRM on exactly that. Monday is broader: more integrations, dashboards and native apps. StreamsApp is stricter about the process and priced per organisation rather than per seat.
- Can my customers log in?
- Not today. Customers get emails, texts and WhatsApp messages from the record and their replies come back onto it, and quotes have an accept link, but there is no customer login.
- Where is my data held?
- In Australia. Records, files, backups and document scanning all stay in Sydney. The security page lists the few services that sit outside Australia and what they see.
Want to see a sales pipeline built this way first? Look through the Sales template, or see how it runs in seven different trades.
Build your first stream free
Start from the Sales template or your own spreadsheet. Two users, every feature, no credit card, and your data stays in Australia.
Get started free