Fixed Price. No Surprises.

Every engagement is scoped and priced before it begins. No hourly rates, no scope creep charges.

90-Day Delivery

From scoping session to live on your first real matter — a structured build inside your existing tenancy.

Onshore

All JurisIT engagements are managed onshore — by AU or UK based consultants who are accountable for your engagement from scoping through to delivery. Client data is held within Microsoft's AU or UK cloud regions throughout.

What we build

The full workflow

We build end-to-end B2B debt recovery automation inside your existing Clio and Microsoft 365 tenancy using Microsoft Power Automate. Nothing new to learn. No additional software licences. Your existing infrastructure, made to work the way it always should have.

Stage	What the automation does
1. Matter opens	Automation triggers from a new debt recovery matter type in Clio. Pulls debtor name, amount, invoice date, due date, creditor details. Runs ASIC company search to confirm entity status and registered address.
2. Letter of demand	Generated from Clio matter data. Compliant with relevant state or territory requirements. Routes to fee earner for review before issue.
3. Demand period tracking	Response window tracked from demand send date. Fee earner notified before deadline. Claim pack prepared and routed to fee earner if no compliant response received.
4. Debtor response handling	Payment in full — matter closes, Clio updated. Payment plan proposed — routed to fee earner for review and negotiation. Dispute raised — routed to fee earner immediately, sequence pauses. Hardship indicated — hardship flag triggered, sequence pauses. No response — claim pack prepared.
5. Claim filing pack	Claim form and supporting documents assembled from Clio matter data. Court fees calculated. Routes to fee earner for review, approval, and lodgement via the relevant online court portal.
6. Post-filing tracking	Service date tracked and logged. Response windows monitored. Default judgment application prepared if no response received within deadline.
7. Defence and directions	If defence filed, matter routed to fee earner immediately. Directions hearing tracked when received. Document assembly support for defended matters; referral pack generated for complex matters.
8. Judgment and enforcement	Post-judgment, enforcement sequence triggered. Fee earner approves each enforcement step. Enforcement options flagged based on matter profile and debtor circumstances.
9. Matter close	Outcome logged to Clio. Recovery amount, method, and timeline recorded. Outcome tracker updated. Client notified via automated letter.

Inside your tenancy

The technology stack

Every component is built inside the Clio and Microsoft 365 tenancy your firm already operates. No new platforms. No additional licences. No data leaving your environment.

Component	Role in the workflow
Clio	Source of truth for all matter data. Matter type, custom fields, and document templates configured during build. All outcomes and correspondence logged back to the matter.
Microsoft Power Automate	The automation engine. Workflow logic, trigger conditions, approval gates, escalation sequences, and notification flows. All flows owned by the firm's Microsoft 365 tenancy.
SharePoint	Outcome tracker register. Matter status dashboard. Document library for filed correspondence and court packs.
Outlook	Automated correspondence sent from the firm's own email domain. Fee earner approval requests and notifications delivered to the assigned fee earner's inbox.
ASIC company search	Automated at matter opening. Confirms entity status and registered address. Results logged to Clio.
Online court lodgement	Fee earner submits the prepared claim pack via the relevant court's online portal. JurisIT assembles the pack; the fee earner retains control of court lodgement.

How it is built

Indicative 90-day build engagement

Phase	What happens
Weeks 1–2 Scoping	90-minute structured session. We map your current workflow, Clio configuration, typical debt values, matter types, and fee earner approval preferences. We review your existing templates or draft new ones. We confirm jurisdiction(s). We agree the scope.
Weeks 3–4 Configuration	Clio matter type, custom fields, and document templates configured. ASIC connection established. SharePoint outcome tracker created.
Weeks 5–8 Build	Power Automate flows built: triggers, demand period tracker, claim pack assembler, post-filing tracker, enforcement sequence. Hardship flag and debtor response routing configured. Fee earner approval gates tested.
Weeks 9–10 Testing	End-to-end testing with sample matters. Fee earner walks through each approval gate. Templates reviewed and approved. Hardship flag scenarios tested. Output documents reviewed.
Weeks 11–12 Handover	Live on your first real matter. Fee earner guidance session. Outcome tracker explained. Referral pack process demonstrated. Documentation provided.

Scope

What can be included

Item	Notes
Letter of demand template set	Drafted for the relevant state or territory. Fee earner approves at sign-off. Includes National Debt Helpline reference where appropriate.
Demand period tracker	Automated from demand send date. Fee earner notified before deadline.
Debtor response routing	Five response paths configured: full payment, payment plan, dispute, hardship, no response. Each routes correctly.
Claim filing pack assembler	Claim form and supporting documents generated from Clio data. Court fees calculated. Routes to fee earner for approval and lodgement.
ASIC company search	Automated at matter opening. Entity status and registered address confirmed. Results logged.
Hardship flag and routing	Configured to detect hardship indicators in debtor responses. Pauses sequence. Routes to fee earner. National Debt Helpline confirmed in subsequent correspondence.
Post-filing tracking	Service date, response windows — all tracked and flagged.
Default judgment preparation	Application prepared on deadline breach. Routes to fee earner for approval and lodgement.
Enforcement sequence	Post-judgment. Enforcement options flagged based on matter profile. Fee earner approves each step.
SharePoint outcome tracker	All active matters visible. Status, amounts, key dates, court stage, enforcement stage. Principal view.
Referral pack	Generated when matter escalates beyond automated scope. Structured handoff to specialist.
Fee earner guidance session	Live walkthrough of the complete workflow with the fee earner(s) who will use it.
Build documentation	Flow diagrams, approval gate guide, template maintenance instructions.
Retainer option	Ongoing maintenance retainer available: template amendments, flow modifications, new matter type additions, quarterly compliance review.

What is not included

Court appearances or advocacy — fee earner or instructed barrister
Payment plan negotiation — fee earner
Consumer debt recovery — outside scope of this product (ACL and NCCP compliance required)
Formal insolvency proceedings — referral pack generated, matter exits sequence
Multi-jurisdiction builds beyond the primary build state — available as separately scoped add-ons
Ongoing template updates post-handover without a retainer

Getting started

The scoping session

Every B2B Debt Recovery engagement begins with a 90-minute scoping session. This session maps your current workflow, Clio configuration, and practice profile. It produces a one-page automation blueprint and the basis for a fixed-fee proposal delivered within five business days.

The scoping session is not a sales call. It is a working session. You leave with a clear picture of what automation will look like inside your firm, what it will cost, and what you will own at the end of it.

We cover	Why it matters
Current debt recovery volume and write-off rate	Establishes the baseline and the ROI case. The automation is justified when the gap between current write-off and recoverable debt exceeds the build cost.
Typical debt value range	Determines which court track most matters will fall into and shapes the workflow scope.
Matter types	Trade invoices, professional fees, commercial rent, estate debts — each may have different demand requirements or claim trajectories.
Existing Clio configuration	Confirms what is already in place (matter types, custom fields, templates) and what needs to be built from scratch.
Existing demand templates	If compliant templates exist, we adapt them. If not, we draft and the fee earner approves at sign-off.
Fee earner approval preferences	Who approves what, at which gates. The workflow is configured to match the firm's supervision structure.
Primary jurisdiction	NSW Local Court is the primary build jurisdiction. Firms operating in VIC, QLD, or other states can have those jurisdictions scoped as add-ons.
Retainer interest	Whether the firm wants ongoing maintenance post-handover or prefers to manage the system independently.

Next steps

What happens next

Submit an enquiry via jurisit.com.au/contact
We respond within one business day to schedule the 90-minute scoping session
Scoping session confirms workflow, Clio configuration, jurisdiction, and approval structure
One-page automation blueprint and fixed-fee proposal delivered within five business days
You review, ask questions, and decide whether to proceed
If yes: 90-day build engagement begins

B2B debt recovery automation for Australian law firms