Service · Reporting & integrations
One set of numbers, delivered, not rebuilt every Friday.
When your bookings, invoices and customer details live in tools that don't talk to each other, someone ends up copying between them and stitching a report together by hand. This service connects the tools, with clear rules about which one is right, and delivers the report on a schedule.
The copy-paste layer nobody planned.
Small businesses pick tools one at a time: one for scheduling, one for invoicing, a spreadsheet for everything else. Each is fine on its own. The trouble is the gap between them: a customer's new phone number updated in one place but not the other, a job marked done that never got invoiced, a weekly summary that takes an evening to assemble and is out of date by Monday.
The fix is rarely a bigger platform. It's usually a few well-defined connections and one report that assembles itself, built so that when something doesn't line up, you're told rather than given a confident wrong number.
For every number, one system is right.
Before anything is connected, each important piece of information gets a named home: the one system whose version wins when two disagree. For example:
- Customer contact details may belong to your booking tool.
- What was billed and paid belongs to your accounting or invoicing tool.
- Notes and job status might live in a shared spreadsheet.
Writing this down sounds bureaucratic. It's what prevents two systems from quietly overwriting each other, and it makes every report traceable back to where its numbers came from.
03 · Sync direction
Which way does information flow?
Most problems with connected systems come from not deciding this. Every connection is one of three shapes, chosen deliberately.
Mismatches are surfaced, not smoothed over.
- Matching rules: how a record in one system is recognised in another (an email address, a job number, an invoice reference) is agreed up front, not guessed at runtime.
- Duplicates: likely duplicates, such as the same customer entered twice, are listed for a person to resolve rather than merged automatically.
- Missing sources: if a system can't be reached when a report runs, the report says so plainly instead of presenting last week's numbers as this week's.
- A change log: anything written into a system is recorded, so "where did this value come from?" has an answer.
- Narrow access: read-only connections wherever reading is enough; write access only where the workflow genuinely needs it.
05 · Labeled example
A weekly owner summary, outlined.
An illustrative structure for a fictional service business with a booking tool, an invoicing tool and a shared spreadsheet. It isn't a client deliverable, and it contains no real figures.
The layout is the useful part: the same sections every week, each tied to a named source, and an exceptions section that's never skipped.
- Jobs completed this weekFrom the booking tool: count and list, grouped by service.
- Invoiced vs. completedCompleted jobs matched to invoices; any job without an invoice is listed by name.
- Payments received and outstandingFrom the invoicing tool, the source of truth for money.
- New customersFirst-time bookings, with contact details from the booking tool.
- ExceptionsPossible duplicates, records that didn't match, and any source that couldn't be read this run.
- Report notesWhen each source was last read, so stale data is obvious.
06 · FAQ
Common questions
Which tools can you connect?
It depends on what your tools allow. Many offer exports, APIs or built-in connections; some don't. Checking what your specific tools support is part of the free assessment, and there's no point promising a connection before that.
Do I have to switch software?
The default is no. The aim is to make what you already use work together. If a tool genuinely can't share its data, you'll hear that and the options, including leaving it alone.
Who sees the reports?
Whoever you decide. Delivery is set up to specific people in the format they'll open: email, a shared sheet or a PDF.
What does it cost?
The assessment is free; implementation is quoted separately once the tools, connections and report contents are known. Some connector services carry their own subscription costs, which you'd see before agreeing.
What if a tool changes?
Software providers do change things. The setup is built to report a failed connection rather than fail silently, and the handover notes say what to check. Ongoing support can be discussed at the assessment.