Offers · Step 4 of 5
Build Sprint
In 4 weeks: one priced backlog item live, tested as your real users on desktop and phone, and your floor trained on site.
You know what to fix. You need it built, working for your office and your crews, and your people using it.
Price
C$ per sprint, before GST. Less your audit credit on the first.
- Payment
- Half at the start, half at handoff.
- With your credit
- C$6,000 − C$2,500 from your Operations Systems Audit = C$3,500
- Guarantee
- Anything we built that breaks in the first 30 days, we fix free.
At SMT Research
You leave with the one Salesforce fix that gives your team the most time back, and exactly how to get it.
Week 1 to week 4
We build one priced item, check it as your real users and train your floor on site.
- Week 1Together
We agree the checklist: who uses it, on which screen, and what done looks like.
You holdA written checklist of what done means.
- Week 2ShareCo
We build on a test copy. You see it working in a 30-minute weekly demo.
You holdA working build to try.
- Week 3ShareCo
We test it logged in as each of your users, on desktop and on phone. Your people try it.
You holdEvery checklist line ticked, desktop and phone.
- Week 4Together
We put it live and spend a half day on site training the people who use it.
You holdIt live, your floor trained, a one-page guide and a recording.
- 30 days afterShareCo
Anything we built that breaks, we fix, on us.
You holdA build that keeps working.
What you get
Each tile is a small drawing of the real document you receive.
The build checklist
Tested as your users on desktop and phone. Every line ticked before go-live.
Half a day on site
We train the people who use it, at your plant, on their own screens.
A one-page guide and a recording
For the next person you hire, so the training does not walk out the door.
A change log
Every change, dated, with who checked it.
Example documents, fictional data.
What we need from you
What we need from you
- Access
- A named user with build access, and a test copy of your Salesforce. We set one up with you if you have none.
- One contact
- One owner who signs off the checklist.
- Your time
- About 2 hours a week, plus a half day on site for the people being trained.
What is included
- The build, with tests and a change log
- Checked logged in as your real users, on desktop and phone
- A half-day on site training the people who use it
- A one-page guide and a recording
- A 30-day warranty: anything we built that breaks, we fix free
One of: up to 3 connected workflows, one QuickBooks or inventory system connection, or half a crew scheduler (a full one is 2 sprints).
Not included
- Licences and middleware fees
- Changes inside QuickBooks or your inventory system
- Anything not in the priced backlog item
The same work at SMT Research
Pulled orders, stock, projects and crew schedules out of separate tools and spreadsheets into one Salesforce, connected QuickBooks, and put crews on their phones.
Read the full caseThe 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.
Materials
Sales entered twice
One entry per sale. Stock and orders agree without re-keying.
How it is counted: Documents still created in the old inventory tool each month (target 0).
At SMT: before, Every sale entered twice; stock count "infinite"; after, Real counts and a record of every stock change.
Schedule
Systems a tech checks before leaving the yard
The day on one page, on the phone.
How it is counted: Count of apps and sheets a crew member opens to start the day (ask five techs).
At SMT: before, 6 systems; after, 1 page: the order, on the phone.
Install
Field users working from their phones
Crews log hours and materials where the work happens.
How it is counted: Field users with a mobile sign-in in the last 30 days, out of all field users.
At SMT: after, 78% use the phone tools (14 of 18), Sep to Nov 2026.
Invoice
Days from install complete to invoice sent
Finished work billed the same week, not when someone gets to it.
How it is counted: Days between the install marked complete and the invoice created in QuickBooks.
At SMT: before, Invoices exported to QuickBooks by hand as CSV; after, Post every 15 minutes.
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
Monthly Support, C$1,800 a month. Fixes, answers, one item shipped a month.
For your Salesforce person
The technical detail, in one place. You do not need to read this to decide.
- Built in a sandbox, deployed with tests and a change log, in your version control if you have one.
- Verified logged in as each affected user profile, on desktop and in the Salesforce mobile app.
- Integrations use the vendor API or your existing middleware; licence and middleware fees are yours.
- A crew scheduler is two sprints: data model and booking first, phone view and change history second.
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.