Intake
Systems integration
CRM to accounting, warehouse to online store, supplier portal to whatever you plan the week in. Most already have a way in. Few businesses use it.
Paterson Projects
Plumbers for data
Your best people are plumbing.
01 / The symptoms
Most businesses don't have a software problem. They have a plumbing problem.
The software is usually fine. It's the gaps between it that leak, and none of it shows on a balance sheet. See how many of these you recognise.
-
The same number, typed three times
Keyed into the CRM, then the accounting system, then a spreadsheet for the weekly report. Three chances to get it wrong.
-
The spreadsheet nobody is allowed to touch
It runs something important, nobody else understands the formulas, and they're on leave next week.
-
The job that only happens on Tuesdays
Not because Tuesday matters, but because that's when somebody has time. Everything downstream waits.
-
Month-end takes four days
The first is spent deciding which of the four figures is real. By then the month is gone.
-
Work that arrives as a PDF
And leaves as a PDF, read by a person purely to move six fields into a form.
-
Two systems, one truth, no agreement
Stock, addresses, pipeline value: it depends which screen you're on. Everyone has quietly picked a favourite.
Before
After
02 / The work
- Intake
- Join
- Treat
- Outflow
We fit the pipes between the things you already own.
Almost nobody needs new software. They need the software they already pay for to stop behaving like four separate businesses.
End to end, from the first survey to the thing running at three in the morning while nobody watches.
Join
Process automation
Approvals that route themselves, records that create themselves, the Tuesday job that runs the moment its trigger arrives.
Treat
AI workflows
For steps needing judgement, not just movement: reading an invoice, classifying an enquiry, pulling six fields from a document. Used where it beats a rule, nowhere else.
Outflow
Reporting you can trust
One number, one source, available when you ask rather than four days later.
We join what you already have
- Xero
- MYOB
- HubSpot
- Salesforce
- Shopify
- WooCommerce
- NetSuite
- Microsoft 365
- Google Workspace
- Slack
- SQL Server
- Postgres
- Snowflake
- Power BI
- REST and GraphQL APIs
- CSV over SFTP
- Whatever that 2009 system exports
03 / The method
Every join made by hand is a join that will fail. Quietly, eventually, and at the worst available moment.
-
We tell you what not to build
The cheapest automation is the step you delete. We look for those first, even when it shrinks the invoice.
-
The person in the meeting writes the code
No account managers, no handover to a junior. You talk to the person building it, every time.
-
Working software every week
Not status reports, not slide decks. You should watch the thing running before you've finished paying for it.
-
You own all of it
Your accounts, your code, your infrastructure, your data. Walk away whenever you like and it all keeps working.
-
One leak at a time
We fix the worst one, prove it holds, then move to the next. Big-bang transformations are how this work got its bad name.
04 / Who you're dealing with
Paterson Projects is Reece Paterson.
A senior software engineer who has spent his career building the kind of systems this page describes: the integrations, pipelines and automations a business quietly runs on.
No account manager, no sales team, no layer between you and the work. The person who scopes the job writes the code, and answers the phone when it breaks late on a Friday.
- Based
- Bay of Plenty
Aotearoa New Zealand - Discipline
- Senior software engineering
Integration and automation - Works
- Remotely across New Zealand
and with offshore teams - Direct line
-
reece@patersonprojects.com
022 544 1928
05 / How we start
It starts with a drawing.
Before anything gets built you get a picture of your own business: where information comes in, where it stops, and who moves it by hand.
Find the leaks
A short piece of paid work, fixed price, agreed up front. You get a diagram of your current system and a ranked list of the leaks, with what each one costs.
Yours to keep, whether or not you carry on with us.
Prove it holds
The smallest job with the biggest bleed, in use in weeks rather than quarters. You judge us on something real, not a proposal.
Then the rest
Once one join is proven, the rest get cheaper. We keep going while there's a leak worth fixing, and say so plainly when there isn't.
06 / What's next
Let's have a look.
Start with a conversation. Describe the job that keeps getting done by hand and we'll tell you straight whether it's worth automating. If it isn't, we'll say so before anybody spends anything.
Based in Aotearoa New Zealand. Working with anyone whose systems have stopped speaking to each other.
Most of it is smaller than you think.
reece@patersonprojects.com