Build or buy a field sales app? A plain guide for sales leaders
Somebody on your team has said it: "We could just build this ourselves." Maybe it was you. Maybe it was the developer who already built your quoting tool, or the owner who knows a guy.
It's a fair idea. Sometimes it's the right one. Here's how to decide whether to build or buy a field sales app, starting with a hard truth: reps skip tools that make their day longer, whoever built them. This guide walks through what an in-house app has to do, what it takes to keep it running, and when building really is the better call.
The short version
- Building the first screen is the easy part. Getting reps to open it every day is the hard part.
- Plan on the app needing a person behind it for as long as reps use it.
- Build if you have a developer you can keep, one narrow job to solve, and a team that already wants the tool.
- Buy if you need reps using it this quarter, or if the one person who understands the app might leave.
Step 1: Write down what the app has to do
Before anyone opens a code editor, put these on one page. Be honest about which ones you need.
- A phone app reps open between stops. Not a web page that's hard to use in a truck. Something a rep can use in two minutes in a parking lot.
- Notes that land on the right account. A rep says "Mike at the fleet on Route 9." Which Mike? Which fleet? Matching messy names to real accounts is a hard problem.
- Follow-ups that turn into tasks. If a visit ends with "call him Thursday about the brake order," that has to become something a person sees on Thursday.
- A manager view. What did each rep see this week, and what came of it? Managers need this to coach. It shouldn't feel like a spy camera, or your reps will stop using it.
- A connection to the systems you already run. Your DMS, ERP, or sales system holds the account list and the sales history. The app has to read from it and write back to it.
- Someone who owns it. Login problems, new phones, new reps, new reports. Somebody gets the text at 6 a.m.
Step 2: Count what it takes to build
You don't need a spreadsheet. Ask these and write down the answers.
Who builds it, and who's their backup? One developer is a plan until they take another job. Ask what happens to the app the day they leave.
Who tests it with real reps? Reps in heavy-duty truck dealerships work in trucks and shops, and they don't have time to report bugs. Someone has to ride along or call them and ask.
Where are you publishing it? A phone app that reps install from the App Store needs an Apple developer account, which Apple lists at $99 a year. Apple reviews every app, and its review guidelines say an app that no longer works as intended, or that you're no longer supporting, "will be removed from the App Store." If you'd rather give the app only to employees, Apple has a separate enterprise program for private distribution, and organizations "may be eligible" to enroll. Either way, someone has to handle it each time a phone update lands.
What does "done" look like? A first version is the start. A version reps still use after six months takes ongoing work: the fixes, the requests, and the new phone models.
Step 3: Test the part nobody likes to plan for
Here's the question that matters most: will reps open it?
Reps don't skip tools because they're lazy. They skip them when the tool makes the day longer. A tool that asks for 10 fields after a long day goes back to the yellow notepad.
If you build, plan for this from day one:
- Let reps try it with a few real visits before you roll it out to everyone.
- Keep the first version to the one thing reps said they want: usually capturing a visit fast.
- Keep it optional at first. Let reps see it save them time before anyone asks them to use it.
- Ask reps after two weeks what they stopped doing, and fix that first.
Most of this isn't code. It's watching how reps work, and that work doesn't stop at launch. It's also the part a buying decision can take off your plate.
When building is the right call
We're a company that sells a field app, so you can take this part with a grain of salt. But we'd rather you make the right call than the wrong one. Build it yourself if:
- Your process is unusual. If your sales visits follow a workflow no product supports, a custom tool may fit better.
- The job is narrow. One form, one report, one handoff. A small tool can do that well.
- You have a developer you trust and can keep, with time set aside for the long haul, not just the launch.
- Your reps already asked for it, and they helped design it.
When buying saves you the headache
Look at buying if:
- You want reps using something this quarter, not next year.
- The person who'd build it is also the person who keeps everything else running.
- Managers need to see the field now, and the rest of the list can wait.
- You've watched a homegrown tool go quiet after the person who built it moved on.
What if you already run a sales system?
You may already run a system that holds your accounts, and the question is whether to add a field layer on top. That's a reasonable middle path.
Many systems are built around the office: accounts, orders, reports. They're strong records. They're less comfortable in a truck cab. A field layer, like Voze, sits on top, captures what the rep heard at the stop, and sends it to the record you already trust. You keep your system of record, and reps get something made for their phones.
Voze is built for that. It's an app for outside reps that captures visit notes by voice, and it connects through Zapier to the systems teams already run. For larger teams we build a custom connection. Voze is a preferred partner of Procede, Karmak, and MaddenCo and works with CDK. See the dealer integrations. If you want to see how it works with your setup, we're glad to show you.
A quick checklist before you decide
Take this to your next meeting. Write yes, no, or not sure next to each line.
- We can name the person who owns the app for the next three years.
- We know who covers for them.
- Reps helped decide what the app does.
- We've priced the ongoing work, not just the first build.
- Our app can match messy account names to real accounts.
- Managers can see what happened in the field without anyone feeling watched.
- We know how the app connects to our DMS, ERP, or sales system.
- We're okay if this takes longer than planned.
Mostly yes? Building may be a good fit. A lot of "not sure"? That's useful information, and a good reason to look at what's already built. More guides for sales leaders are on the Voze blog.
Want a second opinion?
Talk it through with us. Bring your list and your questions. If building is the right call for your team, we'll tell you.