Skip to content

    Free Recommendation

    Tell us what you want fixed

    We will reply with a practical recommendation. Free scoping call included.

    We use these details only to answer you, and we delete enquiries that do not become work after 24 months. The page you sent this from goes with it, so we know which parts of the site are useful. See the Privacy Policy.

    Case Studies

    Work delivered, and what actually changed

    Engagements across Australia, Singapore, Guam and the Philippines. The problem, what was built, and the outcome — without the invented percentages that make most case studies useless.

    Why some clients are not named. Naming a client publicly — with their industry and a description of how they run internally — requires their written permission under the agreements we sign, and as a matter of policy we do not ask for it. Client confidentiality is worth more to the businesses we work with than a logo is worth to us. So each engagement is described on its substance and the client stays unnamed. The work, the systems and the numbers below are real; only the names are withheld. A reference call can be arranged privately if a client is willing to take one.

    Australia
    Anonymised

    A funeral services group

    Funeral Services

    Built with

    Make.comXeroHubSpotGoogle WorkspaceSlack

    The problem

    A finance team was reconciling vendor bills, invoices and support tickets by hand across three systems. The work was accurate but slow, it did not scale with volume, and the knowledge sat with individual people rather than in a documented process.

    What was built

    • —Vendor bill auto-coding — reads the bill, derives the account code from the service type, and matches it to the right ticket
    • —Invoice-to-ticket auto-linking across multiple entities
    • —Automated reminder and escalation workflows for collections
    • —Payroll document generation and duplicate detection before import
    • —Bank reconciliation reporting with drafted follow-up emails for review
    • —Written process and technical documentation for each workflow

    What changed

    • —Repetitive matching work moved off people and into scheduled workflows
    • —Process knowledge captured in documentation rather than held individually
    • —Error-handling and validation added so failures surface instead of passing silently
    Read the full case study
    Philippines

    Mercentra

    Ecommerce & Retail

    Built with

    n8nGoogle SheetsEcommerce platform APIs

    The problem

    Running an ecommerce operation solo meant the operational load — listings, orders, stock, reporting — grew faster than the time available to do it.

    What was built

    • —Product and listing management systems
    • —Order and fulfilment workflows
    • —Inventory reconciliation across channels
    • —Reporting pipelines for sales and margin

    What changed

    • —Operations run by system rather than by memory
    • —The direct experience of being the operator, which is where most of the automation judgement came from
    Read the full case study
    Philippines
    Anonymised

    A bookshop and distribution business

    Bookshop & Book Distribution

    Built with

    Google WorkspaceSpreadsheet automation

    The problem

    Ordering and distribution ran on informal process, so the same questions were re-answered constantly and nothing was written down.

    What was built

    • —Documented ordering and distribution workflow
    • —Digital operations tidied into a consistent structure

    What changed

    • —Day-to-day steps made repeatable rather than improvised
    Read the full case study
    Guam
    Anonymised

    A roadside service business

    Service Business

    Built with

    Workflow automationGoogle Workspace

    The problem

    Jobs moved through the business inconsistently, which made status hard to see and follow-up easy to drop.

    What was built

    • —Simplified job flow with clear stages
    • —More reliable handoffs between stages

    What changed

    • —Job status visible rather than reconstructed
    Read the full case study
    Australia
    Anonymised

    A drafting and documentation services firm

    Drafting & Documentation Services

    Built with

    Workflow automationDocument processing

    The problem

    The steps between a finished draft and a delivered document were manual and repeated on every job.

    What was built

    • —Streamlined draft-to-delivery workflow
    • —Operational documentation for the repeated steps

    What changed

    • —Fewer manual steps between draft and delivery
    Read the full case study
    Singapore
    Anonymised

    A recruitment and placement agency

    Recruitment & Placement Services

    Built with

    n8nDocument processingCRM integration

    The problem

    Hiring and onboarding involved heavy manual back-and-forth, with candidate documents and status chased by hand.

    What was built

    • —Mapped hiring and onboarding workflows end to end
    • —Identified and specified the automation points
    • —Document handling and status-tracking workflows

    What changed

    • —A documented process where there had been an informal one
    • —A prioritised list of what to automate first, by time recovered
    Read the full case study

    A note on the numbers

    You will not find “saved 40 hours a week” on this page. Figures like that are usually estimates presented as measurements, and once you have seen a few you stop believing any of them. What is described above is what was built and what observably changed. Where a client has measured a result themselves and is willing to have it published, it will appear here attributed to them.

    Have a process that looks like one of these?

    The first conversation is about whether automating it is actually worth it. Sometimes the answer is no, and that is a useful answer too.

    Book a scope call See services