Skip to content

Work

Systems we built, and how they work

Explore the workflows, integrations and implementation methods. Client financial information is withheld under NDA.

Bring us a problemSee the service lines
Case studies
10
Service lines
4
Window
Jun to Sep 2026
Built for
SMT Research
Field Operations
Select rangeTodayWeekendsManage crewHistoryUndo‹ 8 to 12 Sep ›
Mon 8
7–11
11–3
Tue 9
7–11
11–3
Wed 10
7–11
11–3
Thu 11
7–11
11–3
Fri 12
7–11
11–3
RR
BRiverside2 @4h
BRiverside1 @4h
BRiverside2 @4h
VHarbour
BHarbour3 @2h
BHarbour1 @4h
THarbour
MK
BKingsway1 @4h
BKingsway2 @2h
!Kingsway1 @4h
!Kingsway
BKingsway2 @4h
BFraser1 @4h
BFraser1 @4h
TFraser
OD
AAbsent
AAbsent
AAbsent
AAbsent
BRiverside2 @4h
BRiverside1 @4h
BRiverside1 @4h
BRiverside2 @2h
VTravel
GS
BFraser3 @2h
BFraser2 @2h
BFraser2 @4h
TFraser
BHarbour1 @4h
BHarbour1 @4h
BHarbour2 @4h
BHarbour
DA
TKingsway
BKingsway1 @4h
BKingsway2 @2h
BKingsway2 @4h
VTravel
AAbsent
AAbsent
BRiverside1 @4h
BBookedTTentative!CriticalAAbsentVTravel4 cellsMK · Tue 7–11 to Wed 11–3EditClear
Depiction · The docket scheduler. One row per crew member, two shifts a day, a fortnight at a time. Drag a range to book it, and every cell carries its status, its site and its timed tasks.A conflict has to surface before dispatch, not after. Absence, travel and a critical job are all distinct states, and each carries a letter as well as a colour so the board survives being printed or read by someone who cannot separate the two.

The engagementSMT Research

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
Read the case studiessmtresearch.ca
The SMT Research team in their Vancouver office

The SMT Research team, Vancouver. Published with their permission.

What sits inside these ten builds
Apex and LWCSalesforce MobileOffline field flowsData migrationCustom metadata configurationAgentforceNamed credentialsGeocoding at scaleRevenue forecastingInventory and stock controlAccounting integrationMFA and device sign-inApex test coverageManaged packages
Measured in production, June to September 2026
10Systems builtTechnical case studies from one engagement.
4Service linesThe categories represented in this portfolio.
28Configuration recordsProvince and tax-class rules in custom metadata.
16Archive objectsDedicated objects for legacy system history.

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 development
    28Configuration recordsProvince and tax-class rules stored in custom metadata.

    Tax rules maintained as configuration

    Tax calculation rules need a shared configuration source that works with both formulas and Apex.

    • SMT Research, Vancouver
    • Jun to Sep 2026
  • FeaturedArchitecture and consulting
    3Systems connectedA technical integration count. Client financial results are confidential.

    A forecast with an explanation behind every row

    Forecasting combines operational and accounting records through a shared key, with a documented method on each forecast row.

    • SMT Research, Vancouver
    • Jun to Sep 2026
  • Custom development
    GeocodingAddress-to-coordinate workflowTechnical capability. Client sales distribution is confidential.

    Salesforce records on an interactive map

    An interactive map connects Salesforce records to locations and gives users a direct path back to the underlying record.

  • Implementation and migration
    16Archive objectsTechnical schema count. Transaction values and financial findings are confidential.

    Legacy history connected to Salesforce

    Historical records belong in dedicated archive objects, linked to current records without triggering operational automation.

  • Implementation and migration
    ValidationAt the integration boundaryTechnical capability. Client accounting data is confidential.

    An accounting integration with explicit validation

    A two-way accounting integration validates record mappings and data precision at the boundary between systems.

  • Implementation and migration
    Audit trailOn stock changesTechnical capability. Stock quantities, valuations and production volumes are confidential.

    Inventory movement with an audit trail

    Inventory workflows connect receiving, transfers, field use and replenishment with a traceable record of each change.

  • Custom development
    5 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 Agentforce
    3Telephony feeds connectedTechnical implementation only. Client operating costs are confidential.

    Call summaries connected to Salesforce records

    Three telephony feeds joined on one key, and every answered call turned into a speaker-labelled transcript with owned action items with source references.

  • Architecture and consulting
    LedgerAppend-only event historyTechnical capability. Client deposits, balances and billing outcomes are confidential.

    Billing workflows with traceable ledger entries

    Billing workflows connect ledger events, document generation and review controls without exposing client account data.

  • AI and Agentforce
    87Findings 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.

Contact us to find out more

Your org has a version of one of these.

1 business dayTo a written read on your orgA written diagnosis whether or not you hire us, before any money changes hands.
Start a diagnosticWhat we do
Client confidentiality

The systems are public. Client financial information is confidential.

These case studies describe technical capabilities and implementation methods. Client financial figures, ratios and findings are withheld under NDA.

Illustrations use fictional demonstration data. They do not represent client results.

Next step

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.

Start a diagnosticHow we work
  • Reply within one business day
  • Written diagnosis whether or not you hire us
  • Vancouver, British Columbia