Make · Case Study
Two Systems, One Set of Numbers
The problem
Two systems, one truth, kept aligned by hand. The team cross-referenced Asana tasks against Xero records manually, and every mismatch meant detective work.
Who this is for
Agencies and consultancies running delivery in one tool and money in another, with someone reconciling the two by hand. Worth building once the mismatches take longer to investigate than the entry took to make.
What I built
A bi-directional sync in Make so neither system drifts:
- Changes flow both ways between Asana and Xero
- Iterator processing handles records in bulk
- Text aggregation builds consolidated financial reports
- Attachments upload automatically to the right records
Demonstration outcome
Demonstration disclosure: this is a portfolio build. The workflow behavior described here is not a measured client business result.
Both systems stay in sync automatically. No manual cross-referencing, no drift between tasks and financials.
Practical guides
Plain checklists for lead follow-up and booking workflows.
How to Test a GoHighLevel Lead Follow-Up Before You Switch It On
A pre-launch checklist for coaches and consultants to stress-test a GHL lead workflow with edge cases before real leads hit it.
How to scope one lead-to-booked-call automation install
A practical guide for coaches and consultants on GoHighLevel: how to define the scope of a single lead-to-booked-call install so the build is testable, boring, and safe.
When to Stop the Robot and Call a Human: A Handoff Checklist for GoHighLevel Booking Workflows
A buyer's guide for coaches and consultants on deciding which leads a GoHighLevel workflow should route to a person instead of an automated sequence, plus a worked hypothetical example and a build checklist.