Professional services firms juggling client intake, documents, and follow-up across tools
About
A practice built for operators, not slide decks
Worktrue is an independent company for growing teams that are tired of retyping, chasing status, and rebuilding the same pack every week. We find the work that should not be manual and build systems your people can explain and trust.
01
Why we exist
Why we exist
Most growing businesses do not need another platform. They need fewer steps between the work and the outcome. Hours disappear into copy-paste between apps, document assembly from memory, and review cycles that follow the same pattern every time. Worktrue exists to take that load off your team so skilled people can spend time on customers, judgment, and the work only they can do.
02
Who we serve
Who we serve
We work with SMB operators and the people who keep the business moving: owners, ops leads, office managers, and small internal teams who know exactly where the process sticks.
Clinics and care practices where admin work competes with patient time
Wholesale and distribution teams coordinating orders, exceptions, and status by email
Any team that can describe a workflow in plain language but cannot get the hours back on their own
Vancouver, Canada
We are based in Vancouver, Canada. Most engagements start remote and stay that way unless you want someone in the room for a working session.
03
Values
What we stand for
Growing teams lose hours to work that should not need a person every time. These commitments do not change because a tool is trendy.
People first
Technology should give your team time back, not create new busywork. Capacity back is the point.
Honest about AI
We use automation and AI where each fits the job. Your team can explain what runs, what flags for review, and what still needs a person.
Prove it works
We test workflows before you depend on them. Exceptions stay visible. Sign-off stays with your people.
04
How we practice
How we practice
We stay close to the work from assessment through delivery: architecture that holds, production reliability, and clear calls on what is worth automating.
- 1
Start with one workflow in plain language before any platform talk.
- 2
Map handoffs and review steps into the path from day one.
- 3
Use automation, integrations, software, or AI only where each pulls its weight.
- 4
Check whether hours actually came back before we call it done.
- 5
Leave you with something you can run, audit, and improve without us in the middle.
05
Who does the work
Headshot placeholder
John Lofthouse
Technology and business leader
John Lofthouse stays hands-on from assessment through delivery: architecture, production reliability, and the call on what is worth automating. His background spans full-stack engineering, infrastructure, security, and applied AI, with prior technology leadership as CTO at Spectra Media Communication Group.
Vancouver, Canada
Recent study
Applied AI and machine learning
Recent study in applied AI and machine learning, including IBM AI Engineering, Stanford Machine Learning, and Google Cloud ML specialization.
IBM AI EngineeringIBM
Machine LearningStanford University
Machine Learning on Google Cloud SpecializationGoogle Cloud
Start with one workflow.
Describe a process in plain language. No email to begin. No passwords or system credentials.
Assess a workflow