Flowrate

We build the systems your business runs on.

Built around the way your team already works, so information goes in once and the retyping, the chasing and the month-end scramble stop.

Book a free callSee what we build
  • Admin systems
  • Field apps
  • Reporting
  • Websites

Built by people who had to do the job by hand first. Names and numbers in the example are made up.

1WhatsApp group

Someone on site sends a photo

2Spreadsheet

Someone types it in

C4 
AC
1JobTotal
204162,310.00
304171,980.00
40418 

3Accounts

Typed in again, by hand

New invoiceINV-0193

Customer

Greenway Café

Line itemAmount
Job 0418 

4Invoice

Sent to the customer

INV-0193

To Greenway Café

Job 0418 
Total

Same number, four places, typed by hand every time. It only takes one slip.

Six places to look. Or one.

Right now the truth about a job is scattered across WhatsApp, Google Sheets, Gmail, Xero, paper and somebody's memory. We pull it into one system, and the invoices, reports and updates come out the other side.

WhatsApp
Sheets
Gmail
Xero
Paper
Memory
Your systemEntered once. Used everywhere.

Jobs board

Draft invoices

Reports

Client updates

Same jobs. Two ways to run them.

Drag the line. On the left, the spreadsheet most teams run on: copies, gaps, and notes only one person understands. On the right, the same jobs in an app built around how you already work.

Got a spreadsheet like that?

Paste the column names from its top row. You'll see the simple app it would become: what goes in on the phone, what the office sees, and what adds itself up.

Only the column names are sent. Nothing is stored.

Whatever the job runs on, we can build it.

Every business has a process held together by WhatsApp, a spreadsheet and somebody's memory. We find it, and build the system that runs it.

One place where every job, order or booking lives, from the first call to the paid invoice.

Your system / JobsLive

Jobs

New job
All 24Needs a look 1Ready to invoice 3
JobCustomerStatus
0419Hill & CoOffice lighting, three floorsQuote sent
0418Greenway CaféFridge not cooling — door sealWaiting on signature
0416Mara’s BakeryAnnual serviceReady to invoice
0415Harbour FoodsCold room alarmInvoiced
0414Oakline JoineryDust extraction, site visitNeeds a look

5 of 24 jobs · updated just now

Connects to the tools you already use, like Xero, Google Drive, Excel and email. Screens shown are examples.

The example above isn't a concept.

We built the same kind of system inside a working fleet, and it runs every day. Drivers photograph their paperwork at the end of a run, and the office never retypes it.

  • Works with no signal
  • Reads every document
  • Checks weights before it bills
  • Files everything automatically
  • A person approves every invoice
  • Holds anything that doesn’t add up
Live
Activity / todayExample data
  1. 17:42Load 2417 captured3 photos · no signal, saved on the driver’s phone
  2. 18:06Signal back, sent automaticallyNothing re-entered
  3. 18:06Documents readDelivery note, weighbridge ticket, load slip
  4. 18:06Weights checked28,460 kg on every page
  5. 18:07Filed and trip sheet updatedStored with the load
  6. 18:07Draft invoice createdWaiting for a person to approve
  7. 18:31Load 2418 heldTicket and delivery note disagree · needs a look

How a build works.

No long requirements documents, and no software you have to bend your business around. It starts with how you work now.

  1. 1

    We learn how the job really runs

    A call first, then time with the people who do the work. We map every step, including the workarounds nobody wrote down.

    A clear map of the job as it runs today.

  2. 2

    You see it before we build it

    We show you how the system will work, screen by screen, and change it until it fits the way your team already works.

    A design you’ve signed off, so nothing is a surprise.

  3. 3

    We build it and launch it with you

    We test it on real jobs before anyone relies on it, then set it up with your team so it’s used from day one.

    A working system, running on your real jobs.

Andrew Murray, founder of Flowrate
The Flowrate mascot, a cartoon of Andrew

You'll deal with the person who builds it.

I'm Andrew Murray, founder of Flowrate. The cartoon in our logo is me.

Before I built software, I did the work it replaces: the paperwork, the retyping, the chasing at month-end. That's why every Flowrate system starts with how your job actually runs, not with a feature list.

When you book a call, it's with me. You'll be talking to the person who designs your system and builds it.

Andrew Murray's signature

Andrew Murray

Founder, Flowrate

Book a free call

What does the retyping cost you?

Set the sliders to match a normal week. The answer is your own numbers added up, nothing of ours.

3

From WhatsApp to a spreadsheet, from the spreadsheet to the accounts.

30 min

Retyping, copying across, chasing who did what.

25

In your own currency. Leave it at 0 to see hours only.

Hours a year spent typing things in twice

345

That's about 9 full working weeks, or roughly 8,625 a year.

3 people × 30 min × 230 working days ÷ 60 = 345 h · ÷ 40 h a week = 9 weeks · × 25 an hour = 8,625

On a free call we'll look at which of those hours a system can take off your hands.

Book a free call

Questions people ask first.

Not covered here? Ask the assistant in the corner, or email andrew@flowrate.agency.

Admin systems that track every job from first call to paid invoice, apps your team uses on their phones out on the job, reports that show what really happened, and websites. Most projects are a mix: the point is that information gets entered once and flows everywhere it needs to go.

Tell us the job you'd love to stop doing by hand.

A few lines is enough. Andrew reads every message himself and replies with how he'd approach it, whether or not that ends with us working together.

Rather talk? Book a free 30-minute callOr email andrew@flowrate.agency

No mailing list, no follow-up sequence. Just a reply.