Commercial fleet & field services
Field-service operations platform
The problem
A multi-site operator was running scheduling, work orders, site records, and invoicing across spreadsheets and paper worksheets. Nothing reconciled, and month-end was a manual rebuild.
What we built
We built a multi-tenant operations platform: scheduling and work orders, mobile capture of signed site worksheets, billing accounts, employee records, mileage calculation from real routing data, and financial reporting. Access is role-based with mandatory multi-factor authentication, and scheduled jobs handle the recurring work.
- Work orders tied directly to invoices
- Signed worksheets captured and stored against each job
- Profit and loss, balance sheet, and expense reporting in-app
- Multi-factor authentication across both portals
Commercial services
Accounting platform migration
The problem
After years on an in-house system, the business needed to move its financial operations onto mainstream accounting software without losing history or breaking the audit trail.
What we built
We planned and executed a phased migration: rebuilding the service catalogue, transferring invoices and payments, splitting deductions across the correct liability and expense accounts, and attaching hundreds of supporting documents to the right records. Every figure was reconciled against the source system and variances were flagged for review rather than quietly absorbed.
- Hundreds of invoices reconciled line by line
- Payments split correctly across loans, credits, and expenses
- Supporting documents attached to source records
- Open variances surfaced for owner review
Insurance
Compliance-first CRM for regulated advisors
The problem
Advisors and agencies needed a CRM that treated Canadian privacy obligations as a core feature, not a checkbox — while still being pleasant enough that people would actually use it.
What we built
We built a multi-tenant CRM with client and household records, policy tracking, quoting, and calendar sync — layered over a compliance engine handling consent capture, subject access requests, document acceptance with tamper-evident records, retention rules, and suppression lists. Tenants are isolated at the database level with row-level security and cross-tenant write guards.
- Consent and privacy workflows built into daily use
- Subject access, correction, and withdrawal handling
- Tamper-evident records of document acceptance
- Strict tenant isolation with row-level security
Financial data integration
Replacing a retiring data provider
The problem
A platform relied on a third-party banking data provider that announced it was shutting down its API, putting a core feature at risk.
What we built
We put a provider abstraction layer between the platform and the vendor so the underlying provider could be swapped without touching application code, built a validated statement parser as an interim path, and designed the review workflow that matches incoming transactions against existing records before anything is committed.
- Vendor-neutral integration layer
- Interim import path so the feature never went dark
- Human review step before transactions post
- Migration plan staged to avoid downtime
