Oakville, Ontario · Serving the GTA
We build the system.
We prove the number.
Automation, reconciled reporting, engineering calculators and technical audits. Every figure is traced back to the system that produced it. The arithmetic closes before anything ships, and anything we cannot verify is flagged rather than guessed.
Fig. 01 — the method
01 — Services
Nine services.
All of them in production.
Each one below is something we currently deliver, not something we would like to. If your problem is not on the list, describe it anyway.
01Spreadsheet auditA same-day audit of one workbook. Broken formulas, hard-coded overrides, duplicate keys and totals that do not tie out…→02Automation auditWe watch the work, list every manual step, and rank them by hours saved against effort to fix. You get a costed order …→03Broken automationA broken script, a failed cron job or an integration that stopped. We diagnose the real cause, fix it, and add the che…→04Reconcilable reportingOne definition per figure, one named source, and an automated check that proves the totals tie out. Reporting that sur…→05Serverless ERPCosts, inventory and reporting in the tools your team already uses. No server, no licence, no migration project. Built…→06Engineering calculatorsYour method, built as a calculator your team can use without training. Sheets or a small web app, with the working sho…→07Estimating reviewA review of how your unit rates and time-and-materials estimates are built. Where the assumptions are, what they cost …→08Supabase securityA review of row-level security, tenant isolation and failure behaviour on a Supabase or Postgres backend. What a user …→09Local search auditA local search audit covering your Google Business Profile, on-page signals, schema and citations. What is stopping yo…→10Website design and buildA site built as static HTML that loads in under a second, passes accessibility, and is structured so search engines ca…→11AI agents that actAn agent that reads from and writes to your real systems, with the guardrails that stop it doing damage and a way to c…→12Long-run extractionRuns that pull thousands of records behind a login without losing the batch when something breaks at hour three. Resum…→13Technical reviewAn independent read of a codebase, a spreadsheet system or a vendor's claims, before you commit money or take over som…→
02 — Why the checking matters
Anyone can make a script run once.
The job is making it keep running, and knowing when it has stopped.
- Every claim carries evidence. If we say a workbook has nine faults, you get the rule that found each one.
- Nothing is published unverified. Our audit tool refuses to write a report containing a finding it cannot reproduce.
- You get the source. Code and documentation are handed over.
- We say when something is not worth doing. That answer is free and it is common.
442
Automated tests passing
across the tooling
across the tooling
14
Years in heavy civil,
on the systems side
on the systems side
9
Services live,
not planned
not planned
5.0
Client review,
5 out of 5
5 out of 5
“Verifying source material, checking existing coverage, and
explaining the trade-offs.”
Client review · 5.0 / 5
03 — What clients say
On the record.
One client review, quoted in full. The three summaries below it describe real engagements and name no client, because nobody is quoted here who did not say it.
Saimon has been excellent to work with. He is thorough, communicative, and consistently goes beyond the basic requirements when researching cases. He does a great job verifying footage sources, checking for existing coverage, and explaining the trade-offs between different options rather than just submitting whatever he finds. I’ve been very happy with the quality of his work and plan to continue working with him.
A construction subcontractor’s costing workbook, edited by three people over four years. The audit found nine faults across two sheets. The one that mattered was a lookup returning the wrong supplier rate on roughly a fifth of the rows. The disagreement it settled had been running for two years.
An invoice export stopped on a Friday and nobody noticed for eleven days. The cause was a rate limit being reported as a permission error, not a broken script as assumed. The fix was small. The failure alert added alongside it has caught two more, both within the hour.
A nine-page static rebuild of a site that looked acceptable and produced nothing. Page weight came down by two thirds, the enquiry form started reaching an inbox somebody reads, and the local search setup was left in place rather than promised for later.
04 — Where we work
Halton
Oakville
Halton
Burlington
Halton
Milton
Peel
Mississauga
Hamilton
Hamilton
Toronto
Toronto
Next step
Tell us what is not working
Describe the problem in a few lines. You get a plain answer about whether it is worth fixing and what it would take, before any money changes hands.
Start a conversation →