Insights

/

22 Nov 2026 · 3 min read

Explainer

“It integrates” doesn’t mean the data moves

“Integrates with” says two apps can talk. It doesn't say what moves, which way, or when. Ask those three things before you pay, not after.

“It integrates” doesn’t mean the data moves

Three boxes made the trip. Ask about the rest.

We wrote 46 pages, each about one app our system connects to. One line from that work set the rule for all of them. Tell a shop owner it “integrates with Shopify,” and they expect the world. Stock levels, shipping, the lot.

What really comes across from a Shopify store is smaller. The customers, their orders and the products. Three moments start work on their own. An order placed, an order sent out, a basket left behind. All of that is useful. But someone who expected stock levels finds the gap after they’ve paid. That’s the worst time to find it, for them and for us.

What does “it integrates” actually tell you?

Only that two apps can pass something between them. It doesn’t say what, which way, or when. Those three things decide whether somebody still types. The word covers a lot. It can mean a live link, or a file somebody copies across once a week.

So before you believe it, ask those three, and two more:

  • What comes across? Customers, orders, invoices, bookings. Ask them to name each one.
  • Which way? One way, or both? If you change it here, does it change there?
  • When? The moment it happens, or once a night, or when someone clicks a button?
  • What starts on its own? A new order, a booking, a paid invoice. Which of them starts the next step?
  • What stays behind? The thing you were hoping for. Ask about it by name.

The last one matters most. Whatever stays behind is still typed by hand. It’s where everything typed twice starts, inside software you paid to stop it.

A small promise you can check beats a big one you find out about later.

What does a good answer look like?

Short, and a little smaller than you hoped. A good answer names the few things that move, says which way, and stops. A long wall of logos says nothing about any one of them. We write our Income Mavericks app pages to that rule.

In Income Mavericks, each connection can be told in a few lines:

  • QuickBooks. Invoices can go across when you send them, and payments follow. A new QuickBooks contact comes back the other way.
  • Calendly. A booking can come across with the person who made it. If they move it in Calendly, it moves here too.
  • Google Calendar. Bookings can go onto your Google calendar. Time already taken there stays closed.
  • Xero. Invoices can go across, and so can what happens next. Sent, part-paid, voided.

None of these is huge. Each one is true, and you can check it on day one. That’s what makes a short answer sound more sure than a long one.

Each app in our integrations library has a page like this. It names what comes across, and stops there.

You don’t need to be technical to ask it. One question, before you pay: what moves, which way, and when?

More on this topic

Automation

18 Nov 2026 · 3 min read · 3 min

Note

Start with the job your team already avoids

Start with the job your team already puts off. Not the one that looks best in a demo. When the system takes that job, the team sees why it's there.

→

Automation

1 Oct 2026 · 5 min read · 5 min

Explainer

Missed call text back buys time, not the job

A missed call text back stops the caller ringing the next name. One saved job a month pays for it many times. It stops working when nobody answers the reply.

→

Automation

18 Sep 2026 · 5 min read · 5 min

Explainer

Most quotes get sent once and never followed up

The revenue is already sitting in quotes you sent. One client reported close to 30% more revenue after the chasing ran on a schedule instead of on memory.

→

Rather talk than read

Bring us the process that keeps going wrong

Tell us what is breaking and we will tell you what it would take to stop it.

Get in touch