Copacetic

About our founder

Why Andrew Is Building Copacetic

Andrew Boyles, Founder & Developer, Copacetic.

Andrew didn't set out to build software for law firms. He set out watching people struggle.

Early in his career at T&M Legal Consulting, he'd walk through departments and see the same thing over and over: files stacked in piles, staff hunting through them for the one document they needed, sticky notes standing in for a task list, emails printed out and physically passed from desk to desk. The firm had Office 365. It had a case management system. Almost none of it was being used properly — not because the tools were bad, but because nobody had ever shown people how to make them work for legal work specifically.

So he did something about it directly. He gave staff access to Slack and Asana and watched their day-to-day communication and file management improve almost immediately. That was the first proof of something he'd end up testing again and again over the next decade: legal teams aren't resistant to better tools. They've just rarely been given ones built for how they actually work.

“Legal teams aren't resistant to better tools. They've just rarely been given ones built for how they actually work.”

But Slack and Asana had a ceiling. They're built to manage projects. A legal matter isn't a project — it's an ongoing, evolving thing with its own deadlines, its own documents, its own accountability. Andrew saw that gap most clearly watching a remortgage team he managed: tight SLAs, documents to collate and submit correctly and on time, and a department head who needed one honest overview of every file in flight and how close each one was to breaching. Generic tools gave the team a board of cards. They couldn't give the department head “here are the twelve files at risk this week.” Making them law-shaped would have meant rebuilding them from the inside — expensive, slow, and still not quite right for the job.

So Andrew built his own. First in low-code, for that same remortgage team. Then again for post-completion. Then, at scale, as Tedius — a virtual PA service he built for consultant solicitors at one of the UK's biggest consultant law firms. Tedius wasn't a side project. It was a full CRM for the sales and admin team, plus a two-way portal where consultant solicitors could send work, track progress, submit information, message the team, and pay bills — alongside an extranet Andrew built so staff had one place with quick, trusted links to the sites they used daily, like Stamp Duty and Land Registry. It worked. It also taught him exactly where low-code hits a wall.

After Tedius, Andrew moved into consulting for smaller firms — and found the same problem, worse. Some firms had no case management system at all. Just Word documents in a folder on one desktop. No backup, no collaboration between colleagues, nothing. If that PC failed, or the one person who knew where everything lived went on holiday, the firm's entire caseload was at risk. He saw firms lose track of data needed to complete matters simply because it was sitting in the wrong file somewhere. That's not an efficiency problem. That's an ever-present risk sitting quietly on top of real client matters.

He saw the same blind spot on the knowledge side. One firm he worked with was actively hiring a knowledge lawyer — and had nothing for that person to do the job with. No system to track legislative changes. No organised precedent bank. In practice, that meant daily manual checks against legislation.gov.uk, no way to summarise what had actually changed, and a “precedent bank” that was really a sticky note or a Word document nobody could say had been checked, updated, or reviewed by anyone in particular. In a profession built on precision, Andrew saw that as a strange thing to accept as normal.

What ties all of this together isn't really about software. It's about how little of a solicitor's training or tooling is aimed at managing the work — time, files, client load — rather than practising the law itself. That's not a criticism of the profession. It's a genuine gap, and Andrew saw it clearly because his own background, outside law, was in operations and people management before he ever specialised in legal tech. Lawyers are trained brilliantly to practise law. Almost nobody trains them to run the operational side of practising it well. Closing that gap doesn't just make a firm more efficient — it gives solicitors more time back for the thing that actually matters: the client.

That's what Copacetic is. Not a replacement for a firm's case management system — a layer on top of it that makes the day-to-day work legible, whether you're looking at an entire firm, a single team, or just the files on one person's desk. Lutey, the AI assistant built into it, exists to help manage that work — never to touch the legal judgement itself. That line matters to Andrew, and it isn't moving.

He's building this in Sunderland, in the North East of England, deliberately. It's where he's from, and he wants to give something back to it. The region has real talent and a history of doing exactly this kind of thing — the North East didn't just take part in the railway revolution, it started it, on the Stockton and Darlington line. Andrew doesn't think that's a stretch to invoke. Seismic changes to how people work and connect have started here before. He'd like this to be one of them.