LEGAL — CONVEYANCING PRACTICES
Conveyancing runs on chasing. Most of it can be systematic.
Sub-sale and developer transactions are among the most repetitive, deadline-driven, document-heavy processes in Malaysian practice. That makes them unusually well suited to systematising — provided nothing touches privileged material. It doesn't.
What we keep finding.
Enquiries arrive on four channels and are handled inconsistently. Phone, WhatsApp, web form and email, with no single view of what came in this week.
The whole transaction is a chase. Documents from clients, redemption statements from banks, consent from the developer or land office. All tracked in someone's head or a spreadsheet.
Junior staff interrupt seniors constantly. "How do we handle a strata title with a pending consent?" The answer exists in the firm’s own practice, but it isn’t written anywhere findable.
E-invoicing arrived on a finance function that wasn’t ready. The LHDN mandate created real work for practices with a part-time bookkeeper.
Today
- Enquiry invaries
- Manual response1 day
- File opened2 days
- Document chase3-8 weeksManual, per matter
- Completion—
After
- Enquiry ininstant
- Auto-acknowledge & triage10 min
- File opened4 hrs
- Structured chase enginetracked & escalated
- Completion—
Where we can help.
Enquiry intake and triage — unified capture across channels, classified by matter type, routed with an automatic acknowledgement
Document chase engine — what's outstanding, from whom, with escalating reminders and a live status view per matter
Deadline and milestone tracking — completion dates, consent applications, statutory periods
Internal knowledge assistant — the firm's own procedures, checklists and precedent index, queryable in plain language
E-invoicing and MyInvois workflow — validation, submission, and an exception queue
Client status updates — automated progress notifications so clients stop calling to ask
Firm AI policy and staff guidance — what your people can and cannot use, written down and trained
New joiner onboarding — procedures induction without consuming a senior's week
What we don't work on
We do not touch privileged material. No client files, no matter documents, no correspondence on a live matter, no title documents, no substantive drafting, and nothing that would be produced in court. We do not provide legal advice or opine on whether an AI use is professionally permissible — those are questions for your firm and the Bar. If a project requires access to privileged material, we will tell you it’s out of scope and point you to legal-technology vendors built for it.
What do we tell our professional indemnity insurer?
That nothing we build has access to privileged material, that everything runs in the firm's own accounts under the firm's own credentials, that every system produces an audit log, and that any output reaching a client passes through a fee earner first. The data boundary is a written contractual term, not a policy statement. We're happy to put that in a letter your insurer can read.
How this usually starts.
Process Survey
Two to three weeks.
Priced after the session.
Three to five core processes drawn, every opportunity scored on effort and impact, and a costed twelve-month roadmap. You own it whether or not you work with us again.
Team Training
One to two days.
Priced per cohort, not per head.
Your team learns to use AI on their actual work, and leaves with a prompt library built around your processes. Your documents, not demo data.
Build
Three to four weeks.
Priced after the survey.
One to three workflows built, tested, documented and handed over — and where nothing off the shelf fits, a custom application built the same way.
Every engagement is scoped and priced after the session, against work we've both seen. If your problem doesn't need us, we'll tell you, and point you at something cheaper.
Start with ninety minutes.
Book a Process Room Session. We'll draw one process properly and tell you honestly whether AI belongs in it.