Document collection that works alongside your CRM

Your CRM runs the deal. It tracks the pipeline, holds the client record, manages the workflow and gets the file where it needs to go.

What it usually does not do well is the part before any of that. Getting the documents in.

Most practice management and CRM platforms include some form of document collection, because it is an obvious thing to include. It is rarely the part the platform was designed around, and it shows the moment your client sends something in the wrong format, or half of it, or three weeks late.

Gatheroo does that one job. It sits alongside whatever system you already run.

What stays and what changes

This is the part worth being clear about before anything else, because “new software” usually implies a migration and this is not one.

Nothing changes in your CRM. Your pipeline, your client records, your workflow, your lodgement process, your reporting. All of it stays exactly where it is. Gatheroo has no opinion about any of it and does not need access to it.

One thing changes. How you ask clients for information, and how you find out what has arrived.

Gatheroo is not a CRM and is not trying to become one. If it ever starts asking you to manage your clients inside it, something has gone wrong.

Where each system does its job

Why collection built into a bigger system tends to disappoint

It is not that the feature is badly built. It is that it was built to serve the system around it.

Collection modules inside larger platforms are usually designed backwards from what the system needs at the other end. A fixed list of items, tied to a stage, producing files in the shape the next step expects. That works when every client is the same shape.

Clients are not the same shape. One has two years of employment history and one has five employers and a period overseas. One has a single income and one has a trust, a company and a rental. One sends a clear PDF and one sends four photos of a bank statement taken at an angle.

A fixed checklist cannot bend around that. So the gaps get filled by email, and once part of the process is running on email, the whole process is running on email. The status lives in someone’s inbox. Nobody can answer “what are we still waiting on” without going and looking.

That is the actual cost, and it is not the chasing. It is the not knowing.

What Gatheroo does with that

Requests are built from your own templates, with the field types the question needs. Address history that lets the client add as many entries as they have. Conditional questions that only appear when they are relevant. Instructions, examples or a short video attached to the question itself, so the client is told what a usable document looks like before they send an unusable one.

The client gets a secure link. No account, no password, no software. They can see exactly what is done and what is outstanding, and they can come back and finish later without starting again.

Reminders go out on a schedule you set, by email and SMS, until the request is complete. Nobody on your team has to remember to follow up.

On your side there is a dashboard showing every open request and where it has got to. Sent, opened, in progress, complete. The answer to “what are we waiting on” is a glance, not an investigation.

Completed information syncs to Google Drive or OneDrive, and Zapier connects it onward to whatever else you run.

What switching involves

Less than people expect, because there is no data migration. You are not moving a database. You are changing where new requests get sent from.

Rebuilding your templates. This is the real work and it is usually an afternoon. Most practices have three to six request types they send over and over. Build those, and you have covered the great majority of what you send.

Testing it. Send one to yourself first. You see precisely what your client sees, which is worth more than any demo.

Requests already in flight. Leave them where they are and let them finish. There is no cutover date and nothing needs to move. New requests go out through Gatheroo, existing ones complete wherever they started.

Your team. There is no rollout project. If someone can build a form, they can build a request.

Most practices send their first real request the same day they start.

The security and compliance side

Gatheroo is built and operated under an ISO 27001:2022 certified information security management system, certificate 1357-I-1. Data is hosted on AWS in Sydney, and Gatheroo is operated by an Australian company subject to Australian law. If you are ever asked in writing where your client data is held, that question has a short answer.

Information is encrypted in transit and at rest. Genuinely sensitive text fields, such as Tax File Numbers, carry AES-128-GCM field-level encryption so those values are never held as plain text. Uploaded files are encrypted at rest with AES-256. The detail is published in the Trust Centre.

Every request carries a timestamped activity log. What was asked, when it was sent, when it was opened, what came back and when. That record builds itself as a by-product of the work, which is the only kind of record that survives contact with a busy week.

No software makes a business compliant. What this does is support your obligations under privacy and AML/CTF requirements by giving you a documented, repeatable process and the evidence that it was followed.

Try it on one client

The fastest way to know whether this fits is to take the request you send most often, build it, and send it to yourself. Ten minutes, and you will see both sides of it.

Try Gatheroo Free | Book a chat

14-day free trial. No credit card required. Set up in minutes.

Gatheroo is not a legal or compliance advisory service. This page is general in nature. For advice specific to your obligations, we recommend engaging a qualified compliance professional.