Skip to content

Offers · Step 2 of 5

First Fix

In 5 business days: that one thing fixed, a 3-minute recording of it working, and a list of what else we saw.

The one thing your team works around every day: an order that will not convert, a report nobody trusts, invoices that do not reach accounting.

Price

C$4955 business days from access

C$, before GST. Capped at 5 build hours.

Payment
Billed upfront, before day 1.
Comes off your next step
Operations Systems Audit: C$2,500 − your C$495 = C$2,005, within 30 days
Guarantee
It works, or you get your C$495 back.

At SMT Research

28Hour entries per tech in the first month308 entries by 11 techs, counted in Salesforce, 30 days to 1 Sep 2026, after the fix.Counted
Get my 15-minute fix plan

You leave with the one Salesforce fix that gives your team the most time back, and exactly how to get it.

Day 0 to day 5

We fix the one thing your team works around, tested on a copy first.

  1. Day 0You

    Create a named user for us and name the person who uses the workflow.

    You holdYour start date confirmed.

  2. Day 1ShareCo

    We back up every record the fix will touch and repeat the problem on a test copy.

    You holdA backup of every record touched.

  3. Days 2-3ShareCo

    We build the fix on the test copy and test it the way your team uses it.

    You holdThe fix working on a test copy.

  4. Day 4You

    Your person tries it for 15 minutes. One round of changes is included.

    You holdYour go-ahead.

  5. Day 5ShareCo

    We put it live, record it working, and write up what changed and what else we saw.

    You holdThe fix live, a 3-minute recording, a change note and a list of what else we saw.

What you get

Each tile is a small drawing of the real document you receive.

  • The fix, live

    Tested on a copy first when you have one, then checked again once live.

  • A 3-minute recording

    The fix working, start to finish, as your team will see it.

  • A change note

    One paragraph: what changed, why, and how to undo it.

  • What else we saw

    Everything else we noticed while we were in there, in plain words.

  • A backup of every record touched

    Taken before we change anything, so every record can go back the way it was.

Example documents, fictional data.

What we need from you

What we need from you

Access
A named user you create, with the access the fix needs. A test copy of your Salesforce if you have one.
One contact
The person who uses the workflow every day.
Your time
About 1 hour across the 5 days.

What is included

  • The fix, tested on a copy of your Salesforce first when you have one
  • A backup of every record touched
  • A 3-minute recording of it working
  • A one-paragraph change note
  • A list of what else we saw while we were in there

One workflow, report, dashboard or connection your team works around. Up to 5 build hours, one revision.

Not included

  • New record types or screens built from scratch
  • Moving data from another system
  • Anything past 5 hours. We say so on the call, before you pay.

The same work at SMT Research

The field hours flow told crews "Successfully logged" while saving nothing. We made it stop and say why.

Read the full case
28Hour entries per tech in the first month308 entries by 11 techs, counted in Salesforce, 30 days to 1 Sep 2026, after the fix.Counted

The numbers this moves

Measured inside your own Salesforce. SMT’s figure is shown where it was recorded.

  • Quote

    Hours from request to quote sent

    Quotes out the same day, while the customer is still deciding.

    How it is counted: Time between the request logged and the quote PDF sent, per quote.

    At SMT: before, 1 day to 1 week, starting in Excel.

  • Quote

    Quotes followed up on time

    Every open quote gets its follow-up, without anyone remembering to.

    How it is counted: Share of open quotes with a completed follow-up task by its due date.

    At SMT: before, 60 to 70% of the time.

  • Order

    Quotes that convert to an order on the first try

    A won job becomes an order in one click, and says why when it cannot.

    How it is counted: Share of conversions that succeed first time, with the failure reason logged.

    At SMT: after, Reason shown on every conversion; converter rebuilt.

  • Install

    Hours logged on the day

    Hours you can bill and pay from, without chasing anyone.

    How it is counted: Share of hour entries made on the day the work happened.

    At SMT: after, 28 entries per tech in the first month (308 by 11 techs).

  • Invoice

    Hours spent gathering payroll hours

    An afternoon back every pay period.

    How it is counted: Staff time per pay period to compile hours for payroll.

    At SMT: before, About 4 hours per pay period; after, Hours report emails itself.

The next step

Operations Systems Audit, C$2,500. Every department mapped, problems ranked, top five priced.

Next step: your C$495 comes back as credit on the Operations Systems Audit within 30 days.

For your Salesforce person

The technical detail, in one place. You do not need to read this to decide.

  • Typical scope: one Flow, validation rule, report, dashboard or integration error.
  • Built and tested in a sandbox when one exists; every record touched is exported first.
  • Up to 5 build hours and one revision. Deployed with a one-paragraph change note.
  • We work as a named user you create, with the least access the fix needs.

Show us the one thing your team works around.

15 minutes, on us, and you leave with a plan. You see your own Salesforce, live, and get the fix that gives your team the most time back, written down and yours to keep.