Your business depends on systems nobody fully trusts.
Microsoft Access databases. Excel reporting. SQL pipelines. When the tools your business runs on become slow, brittle, or hard for anyone else to support, the whole operation feels the drag.
Twenty years fixing these problems inside major Canadian banks. Now working directly with small and mid-sized businesses — without the overhead or the translation layer.
Book a Free 15-Min CallThe kinds of problems I solve
Real situations businesses bring to me when a system or process still matters but has become harder to explain, support, or improve safely.
Access & VBA Automation
Inherited database becoming slow, unstable, or difficult to support after the original builder moved on.
Review the setup, identify structural weak points, clean up problem areas, and clarify how the system actually works.
Less firefighting, clearer ownership, and a system the business can support with less guesswork.
Excel & Data Cleanup
Month-end reporting takes a full day of manual copy-paste. Formulas are broken. The numbers keep getting questioned.
Fix the formulas, consolidate the data, and rebuild the process so reports update in minutes instead of hours.
Reliable numbers, faster turnaround, and a process that doesn’t fall apart when someone else has to run it.
SQL & Reporting
Queries that run slowly, reports that do not reconcile, and data that people keep questioning.
Trace the problem back to the source — whether that’s the query logic, the data structure, or the process feeding it.
Faster queries, accurate reports, and a data pipeline that is easier to explain and support.
AI & Your Data
The business is collecting data but it sits unused. AI tools can’t make sense of messy spreadsheets and inconsistent formats.
Audit what you have, clean and restructure it, and build a repeatable workflow so AI tools can actually read your data.
Usable data, a working AI workflow, and answers from your own information — without hiring a data analyst.
Experience that travels
The problems change. The approach doesn’t.
Inherited system A reporting team at a major financial institution inherited a critical Access database when its original developer moved to another department. The system worked — until it didn’t. Each time it broke, they’d negotiate borrowed hours from that developer to get through the month. Ownership was unclear. The business logic was poorly documented. When I got in, the reason was clear: thousands of lines of VBA holding up a system with almost no normalized structure underneath. There was no clean rebuild path. Instead, we stabilized the highest-value functions and documented those components thoroughly. They stopped borrowing time from another department just to survive each month.