Work
Systems we built, and the numbers they moved
Each of these is a working system in a production org. The figure on the card is the one that mattered to the person who paid for it.
- Case studies
- 10
- Service lines
- 4
- Window
- Jun to Sep 2026
- Built for
- SMT Research
The engagement
Ten systems, one org, four months
SMT Research monitors building envelopes across North America. Everything below was built inside their production org, alongside the people who run it.
- Docket scheduler
- Field service and mobile
- Revenue forecasting
- Inventory and production
- Quoting and tax engine
- Accounting integration
- Archive and migration
- Sales mapping
- Agentforce and AI
- Reporting and dashboards
The SMT Research team, Vancouver. Published with their permission.
Case studies
Ten systems in one production org
Two are featured because the finding mattered more than the build. Filter by service line, then read the one that looks like your problem.
10 of 10 case studies
- FeaturedCustom development31%Of quote lines carried no tax code5,997 of 19,255 lines. 5,182 of them sit on Canadian job sites.
A tax engine rebuilt from 28 rows of configuration
The client told us the tax was calculating by product instead of by province. We tested that against all 2,335 order line items and it was not true. Six other defects were, and we priced each one.
- SMT Research, Vancouver
- Jun to Sep 2026
- FeaturedArchitecture and consulting$2.7MOf finished work that had never been invoicedThe gap between what one system called installed and another called invoiced, on a book all three agreed the size of.
A forecast the CFO can defend line by line
Three systems agreed on the size of the book and disagreed on how much of it was done. The gap was work physically finished and never billed.
- SMT Research, Vancouver
- Jun to Sep 2026
- Custom development100%Of the order book placed on a mapFrom a starting point of zero. The book was recorded at 254 orders carrying an address and the geocoding run at 252 of 252. We have not reconciled the gap.
An order book on a map, and the customer who was a fifth of it
Every order had an address and none had coordinates. Once they were mapped, one account turned out to be 20% of the book and the default view was hiding another 35%.
- Implementation and migration0Failed records across 16 archive objects1,553 sales orders, 8,478 order lines, 3,438 purchase orders, 2,862 invoices and 14,889 stock movements loaded.
An ERP retired without losing a transaction
Sixteen archive objects populated with zero failures, and two phantom invoices caught and removed before they touched a live record.
- Implementation and migration16%Of live invoice lines carried unsafe decimal precision21 of 135 lines replayed. Caught at the accounting boundary, with no Salesforce field narrowed.
A two-way accounting sync that refuses to guess
Receivables, payables and timesheets sync both ways on a fifteen-minute cycle. Every rule that could round, merge or classify a dollar is written down and refuses to guess.
- Implementation and migration$6.99MOf inventory value made visible for the first time395 priced SKUs in the warehouse, plus stock on job sites. Priced stock only.
Where the inventory value actually is
One question drove the whole design: where is the inventory value now. The answer required a state machine, an audit trail on every movement, and an honest note about two parallel ledgers.
- Custom development5 to 6Systems a field technician checked each morningThe recorded before state. No after count was measured, so we do not publish one.
Five to six systems every morning, and a flow that logged nothing
Field crews were opening five or six systems before starting work, and a logging flow was telling them it had saved data when it had saved nothing.
- AI and AgentforceUnder $0.01To transcribe, summarise and action a ten-minute callAbout 20k tokens on a fast model. Model cost only, excluding the telephony subscription.
Conversation intelligence without the per-seat price
Three telephony feeds joined on one key, and every answered call turned into a speaker-labelled transcript with owned action items for fractions of a cent.
- Architecture and consulting5 of 45Projects with any deposit accounting before we startedDeposits were held on roughly 45 projects. The org tracked them on five orders.
Deposits, holdbacks and progress claims that reconcile
Deposits, the standard 10% construction holdback and statutory declarations had no home in the org. The ledger that fixed it stores every amount as a positive number and puts the sign in the type.
- AI and Agentforce87Findings anchored to a file and a line, overnightNine agent result blocks from one audit of a live org. They condensed to five root causes, all fixed the same day.
An overnight audit that names the file and the line
Point agents at an org overnight and get back findings anchored to a file and a line, a costed backlog, and the exact click path to verify each item as the real user.
Your org has a version of one of these.
Every number here was measured, and every mechanism is exact.
Every system here ran in a live production org and every figure was measured rather than estimated. All ten are described by what they do and how they were built.
Sourced from docs/research. Every figure cites a file and a section.
Bring us your hardest Salesforce problem
Tell us what is broken. You get a written read on it within one business day, before any money changes hands.
- Reply within one business day
- Written diagnosis whether or not you hire us
- Vancouver, British Columbia