crisis_alert
Situation
A licensed Canadian professional operating under a regulatory college — the kind of practice where client funds must be held in trust, drawn down only as work is earned, and reconciled on demand. They needed billing simple enough for a non-technical solo practitioner to run, yet compliant with strict trust-accounting rules, provincial tax obligations, and Canadian data-residency law. The incumbent vendors were predatory, which is what prompted building an alternative. The real problem: make strict compliance invisible to the user without ever letting it slip.
lightbulb
Decision
Built for how this practice's clients actually pay, rather than the card-first default the market assumes. Designed the compliance obligations into the system so the practitioner isn't the one policing them. Kept client data resident in Canada. Rejected: a design built around the wrong payment habit, a manual-first MVP, a cheaper vendor that wasn't a real processor, and convenient US-hosted defaults.
shield
Risk
A compliance error here puts the user's professional standing in regulatory jeopardy, not just their books. The build treats that as the primary risk: the system enforces the rules and keeps a complete record, so correctness doesn't depend on the user remembering to be careful.
check_circle
Change (projected — pre-launch, releasing soon)
For the firm adopting it: billing that's faster and safer to run, with compliance handled automatically rather than manually policed, and built to scale as the firm grows.
