TLC
The Laravel CRM behind TLC, an Australian lender of payment plans for medical, dental, lifestyle and wedding costs, and the production systems it runs on.
A long-term engagement with TLC (Total Lifestyle Credit), a Sydney-based, ACL-licensed lender. I built the Laravel CRM its team runs the business from, designed and documented the broker API that brings applications in from partners, and look after the servers underneath.
TLC
TLC — Total Lifestyle Credit is a Sydney-based lender, licensed under the Australian Credit Licence, that offers personal loans and payment plans for the costs people would rather not put off: medical and cosmetic procedures, dental work, IVF, weddings, vehicles, veterinary care and more, from $2,001 to $70,000. Over 193,000 Australians have applied through it.
What I built
- The CRM. TLC runs on a CRM I built in Laravel: the system where applications arrive and customers and their loans are looked after, built around how TLC’s team actually works.
- A broker API. Loan applications don’t only come from TLC’s own website. I designed and documented a token-authenticated JSON API that lets brokers and partner businesses submit applications straight into the CRM. It is strict about its input — every field validated, every list of options fixed and case-sensitive — so what arrives is ready to assess, and a partner sees exactly what was wrong when it isn’t.
- The infrastructure. As the administrator, I configure and maintain the servers it runs on, automate deployments, keep software patched, and make sure backups exist and restore. In a business that handles personal and financial information, that part isn’t optional.
What a long partnership is worth
- Continuity. Since 2020 I’ve known the system’s history — why a setting is the way it is, which part was fragile three years ago — and that makes every change safer and faster than it would be for someone arriving fresh.
- One person who sees both sides. Many problems live in the gap between application and infrastructure: a slow page that is really a database configuration, a failed deploy that is really disk space. Owning both closes the gap.
- Reliability first. New features never come at the expense of a stable, secure production system.
- No surprises. Plain-language communication about what changed, why, and what’s next.
The details of client work stay confidential. To talk about a platform of your own, get in touch.