We connect the systems your business already runs, so a customer is entered once and every other system picks them up on its own.
Your systems don't talk to each other. So who's doing the typing?
Picture a plumbing business. A customer moves house. The office updates the CRM, but the accounts still have the old address, so the next invoice goes to the wrong place. The job sheet has the old address too, so the plumber drives to the wrong house.
Every retype is paid time, and another chance to get it wrong.
We connect them, so it's typed once and right everywhere.
Today. A customer accepts the quote. Someone retypes it into Xero, then types the job into the scheduler.
If it has an API, we can connect it.
An API is the door a system leaves open for other software. Stripe has one. So do ASIC, most banks and many alarm and access systems. We build both sides: the connection that calls their API, and the endpoint they send to when something happens, like a payment clearing.
- PaymentsStripe Square Tyro PayPal Other payment gateways
- BankingBank feeds RedBark Business banking APIs Open banking data
- Government & registersASIC ABR (ABN checks)
- AccountsXero MYOB QuickBooks Reckon
- Customers & supportHubSpot Salesforce Zoho Pipedrive ServiceNow Jira Service Management Zendesk Freshdesk
- Jobs & bookingsCliniko Halaxy ServiceM8 simPRO Tradify Fergus
- Email, chat & phonesMicrosoft 365 Google Workspace Teams Phone Twilio WhatsApp Business Your phone system
- Telco & nbnnbn Telco ordering systems Telco service systemsNeed the connection itself? RUFEN Infrastructure
- SecurityAlarm monitoring Access control CCTV platformsNeed the network secured too? RUFEN Infrastructure
- DataSQL Server PostgreSQL Firebase Excel Google Sheets
- AIClaude Gemini GPT models
- Anything elseNot listed? Tell us what you run. Book a call
Examples, not partnerships. No API? If a system has another way in, we can usually still connect it.
RUFEN Infrastructure
Your internet, networks and phones, run by the same team that connects your systems.
- Internet & mobile
- Networks & security
- Business communications
- Hosting
RUFEN Infrastructure
Your internet, networks and phones, run by the same team that connects your systems.
- Internet & mobile
- Networks & security
- Business communications
- Hosting
Your AI can use it too.
An MCP server lets an AI assistant look things up in your systems, and act in them only as far as you allow.
Ask which jobs finished last week but haven't been invoiced. The answer comes from the job list and the accounts, not from a spreadsheet someone exported on Friday.
- You choose the access. Start read-only if you like, and add tools as you trust it.
- Passwords stay out of it. The assistant never sees your logins.
- People approve the big moves. A payment, a message or a deletion waits for someone to say yes, or isn't allowed at all.
How we build it, and what you keep.
Four steps, and nothing lives only in our heads.
Map it
We draw what talks to what, and decide which system is the source of truth for each detail.
Build it
We build against your real systems, and test it before it touches a live record.
Watch it
Once it's live we monitor it. If a system goes down or changes, we're the ones who find out.
Hand it over
You get the documentation, so another developer could pick it up tomorrow.
- Keys stay on the server. Passwords and API keys never sit in a browser or an app.
- The code we write for you is yours. No lock-in.
- Where your data is held is set out in Trust & security →
Demo
Each packet is one record moving between systems.
We quote each job after a free 30-minute call.
Questions
Which systems can you connect?
Anything with an API. This page lists examples like Xero, Stripe, ASIC, HubSpot and Microsoft 365, plus bank feeds, nbn systems and security systems. They're examples, not partnerships. If a system has no API but has another way in, we can usually still connect it.
Can you build an endpoint for another system to send to?
Yes. Many services, Stripe among them, send a message the moment something happens, like a payment clearing. We build the endpoint that receives it and passes it to the right system.
How long does an integration take?
1-2 weeks for a small connection, 4-6 weeks for a larger integration. We quote each job after a free 30-minute call.
Who owns the code?
You do. The code we write for you is yours, with the documentation, and another developer can take it over.
Can an AI assistant use the connection?
Yes, through an MCP server, if you want one. You choose what it can read or do. Sending a payment or deleting a record waits for a person to say yes, or isn't allowed at all.
Do you publish prices?
No. We quote each job after a free 30-minute call, and the quote is fixed before work starts.
Tell us what's slowing you down
A line or two is plenty. We read every message ourselves.