Retail Merchandising Field Service Software: Build vs Buy
Buy if you are a brand field team running one programme with one reporting standard. Repsly, Natural Insight, Movista and FORM were built for that shape and you will be live in weeks.
On this page
Buy if you are a brand field team running one programme with one reporting standard. Repsly, Natural Insight, Movista and FORM were built for that shape and you will be live in weeks. Build when you are an agency past roughly 150 representatives serving clients with different rate cards and different definitions of a completed call, because per client configuration stops fitting inside a product.
What Repsly, Movista and Natural Insight actually do well
If you are a brand field team of thirty running one programme with one reporting standard, buy. Repsly, Natural Insight, Movista and FORM were built for exactly that shape, you will be live in weeks on a subscription, and a build at that size is capital spent to avoid a manageable bill. We say this to prospects regularly and it costs us work.
Give the products their due. Repsly moves a representative through a store call quickly, which matters more than any head office feature, because a slow app is an app your field team learns to fill in from the car park afterwards. Natural Insight is strong on scheduling and coordination across a large distributed workforce. Movista covers execution and workforce management together, and for retailers running their own labour alongside third party crews that combination is genuinely hard to assemble yourself. FORM handles mobile task and photo capture cleanly.
They also carry things a build never gives you free. Two mobile app store submissions a year. Operating system upgrades that break camera permissions in June. Somebody to call at seven on a Monday when a representative's device will not sync and there are nine stores on her route.
Buy while your requirement is a field team executing a programme. Keep reading if your requirement has quietly become a business that sells verified completed work to fourteen different clients.
Where they stop: the completed call is a billing event
Here is the specific workflow no product in this category models properly. In a brand field team, a completed visit is a form submission. In a third party merchandising agency, a completed visit is a line on an invoice, and the rate depends on the client, the store banner, the call type, whether it ran long, whether a second representative was required, and whether that client's own definition of completion was met.
One client counts a call complete at ninety percent survey completion. Another requires one hundred percent plus a manager signature at the service desk. A third wants a before photo, an after photo and a facings count, and will dispute anything missing one of the three. Those are not three report templates. They are three data models wearing the same name.
So somebody exports visit data at month end, cross references a rate card in a spreadsheet, applies the exceptions by hand, and produces an invoice a week later than it should have gone. Then a category manager queries eleven calls because the before photos are missing, and the reconciliation starts again. Agency margin disappears precisely there, because written off calls are rarely counted and almost never fixed.
The second thing that stops is evidence. Clients audit. When a category manager suspects a call was claimed from the car park, a checkbox and a single map coordinate is not an answer. What ends a dispute is several independent signals captured together: geofence entry and exit with the accuracy radius recorded, photos bound to time and place at the moment of capture with a hash stored on the device so nobody can claim a file was substituted, mock location detection, duration measured on the device rather than inferred from sync time, and a visible audit trail of every later edit. Handled well, that protects honest representatives as much as it protects the invoice.
The arithmetic: per representative per month versus a build
Field execution products price per user per month, and in an agency every representative is a user. That is the whole comparison. Take your per user rate, multiply by active headcount including your seasonal peak rather than your average, multiply by thirty six months, and you have the subscription side.
Now add the part that never appears on an invoice. The finance days spent assembling the monthly billing run. The account manager hours spent on disputes. And the write-offs, which is the number most agencies have never actually pulled. Take last quarter, count calls completed against calls billed, and price the difference at your average call rate.
The crossover in our delivery experience sits near 150 field representatives, and it arrives earlier when your client count is high relative to headcount. An agency of 200 representatives serving three similar clients should stay on a product. An agency of 120 serving fourteen clients with materially different completion rules usually should not, because the cost is configuration pain and write-offs rather than seats.
One more figure belongs in it. Time how long it takes to onboard a new client today, from contract signature to first billable call. In a growing agency that duration is the growth constraint, and it is the number that moves most after a build.
What a custom merchandising build actually costs
Bands, from delivery experience rather than a rate card. A first release covering visit scheduling, an offline first representative app with photo and survey capture, geofenced proof of visit and a supervisor review queue runs $55,000 to $120,000 and ships in 10 to 16 weeks. A full platform adding per client rate cards with automated call billing, client portals and data feeds, exception and dispute workflow, territory and route optimisation and certification tracking runs $140,000 to $350,000 phased over 6 to 12 months.
Data migration adds 10 to 25 percent. Historical visit evidence is the part that matters, because open disputes reach back months and a photo you cannot bind to a store and a date is worth nothing in the conversation it exists for.
Year two runs 15 to 20 percent of build cost annually. Mobile operating systems change camera and location behaviour every year, new clients bring new completion rules, and payroll rules move.
What pushes it up: the count of clients with genuinely different completion definitions, since each is configuration to design and test. Native apps on both platforms, where media handling has to be tuned separately. Client system integration, which ranges from a data feed to a retailer portal with no interface at all. Payroll integration, because representatives are frequently paid per call plus mileage and that calculation has to be exact. And shelf image recognition, which is useful and belongs in its own phase.
What keeps it down: your two largest clients only, one mobile platform first if your field team is predominantly on Android, and route optimisation deferred until the visit and billing loop is proven.
The four situations where building wins
- Regulatory fit. Field work is where employment law becomes a software requirement. Under the Fair Labor Standards Act, travel between stores in a working day is compensable time and payroll records must be retained for three years, so your visit and duration data is payroll evidence rather than operational logging. In California, Labor Code section 2802 requires reimbursement of necessary business expenses including mileage and the phone the representative uses. Predictive scheduling ordinances in several cities constrain how late a route can change. And if device attestation touches face or fingerprint data, the Illinois Biometric Information Privacy Act sets consent and retention duties with a private right of action attached. Products give you a notes field for all of that.
- Scale economics. Per user per month across a headcount that doubles at reset season, where the people you most want inside the system are the ones who use it twice a day and each consume a seat.
- A workflow that is your competitive advantage. An agency does not sell labour, it sells verified completed work. If your differentiator is proving the call happened to a standard the client defined, that logic should not sit in somebody else's configuration screen.
- Integration sprawl across three or more systems. The scheduling tool, the representative app, the rate card spreadsheet, payroll, accounting and per client reporting feeds. Every pair is retyping, and the retyping happens in the week you are also invoicing.
Two of those true is a build. One is a better configuration of what you already pay for.
How to decide in a week, with last month's invoices
Four numbers. None of them require anyone to buy anything.
Monday: last month's completed calls against last month's billed calls, by client. The difference is your write-off rate and most agencies are surprised by it.
Tuesday: pull every dispute raised in the last quarter, value it, and group by reason. Missing photo, wrong photo, no proof of duration, wrong store, survey incomplete. One reason usually dominates and it tells you what to build first.
Wednesday: open fifty photos at random from last month and ask whether each one binds to a store and a moment you could defend in front of a client. Not whether it is a good photo. Whether it is evidence.
Thursday: time your most recent client onboarding from signature to first billable call, and ask the person who did it how much was configuration and how much was a new spreadsheet.
Friday: price it. Write-offs plus disputes plus the finance days plus three years of seats at peak headcount. Under roughly $120,000 a year, tighten the process and negotiate at renewal. Above it, build the completion rules and billing layer first and leave scheduling exactly where it is.
If the numbers point to build, start with a paid discovery. Two to three weeks at a fixed fee, and the deliverable is a signed product requirements document holding each client's completion definition, the required evidence set, the rate card logic, the offline sync model and acceptance criteria. No code is written until that is signed, and you keep it either way.
We are wrong for you if you are a brand field team, if you run fewer than sixty representatives, or if you are choosing on hourly rate. Where Digital Heroes fits: more than fifty specialists, over 2,000 projects, our own products including ShopScore, HeroCheckout and Section Vault, and India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. You meet the named team before signing. In merchandising your software is part of what clients evaluate when awarding contracts, so ownership of the repository and the evidence store is settled before development starts, and our record is checkable on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S listing.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
Frequently asked questions
How long before field representatives are working in a custom app?
Ten to sixteen weeks for a first release, then a rollout paced by your field team rather than engineering. Pilot one client and one district for two to three weeks with the old process still running, because that is when you learn the store realities nobody documented, such as banners requiring a service desk check in or receiving windows that block morning calls.
Who owns the visit evidence if a software vendor holds it?
Settle it in writing before kickoff: the repository, the app store accounts, the cloud infrastructure and every photo and geofence record. In merchandising your evidence is what you invoice against and what you defend in a dispute months later, so it belongs in an account you can query without asking permission. At Digital Heroes the client owns all of it from the first commit.
What happens if a client disputes an entire month of calls?
You produce the evidence set that client's contract specifies, per call, in an afternoon rather than a fortnight. That means geofence entry and exit with accuracy, photos bound to time and place at capture, duration measured on the device and an audit trail of edits. Agencies that lose these disputes usually lose them because their proof is a coordinate stored alongside a record, which proves nothing.
Can we build only the billing layer and keep our current rep app?
Often yes, and it is the cheapest first move. Pull completed visit data out of your existing product, evaluate it against each client's completion rules, route failures to an exceptions queue before invoicing, and generate invoices at the correct rate card. You keep the field experience your team already knows and you fix the part that leaks money at month end.
Should an agency with sixty representatives build custom software?
Usually not, and we would say so before quoting. At that size, two or three clients with similar requirements fit inside a product configuration, and the money is better spent winning the fourth client. The case appears when completion definitions genuinely differ per client, when onboarding a client takes weeks of manual setup, or when your write-off rate has become a line somebody defends in a board meeting.
What is the difference between a field service product and a merchandising platform?
A field service product models a service call: one customer, one address, one technician, one duration, one invoice. A merchandising platform models a store call against a client programme, where the same store is visited for four different clients with four different completion standards and four different rates. The gap shows up in billing and dispute handling, not in the app the representative uses.
How much does supporting a second mobile platform add?
Enough to sequence rather than assume. Camera behaviour, background sync, storage handling and location permissions all differ, and the media pipeline is where most of the extra work sits. If your field team is predominantly on one platform, ship there first, run a real season on it, then add the second with the sync model already proven under load.
What happens to open disputes during a migration?
They stay on the old system until they close, and you keep it readable for that period. Migrate historical evidence for the retention window your client contracts require, then run the new capture flow in parallel for a few weeks on one client so you can compare completion decisions side by side. Cutting over mid dispute is how an agency loses a claim it would have won.
Can shelf image recognition tell us whether a reset was done correctly?
It can flag likely mismatches, missing signage and empty facings, and that is genuinely useful. Treat it as a later phase, because it needs volume and labelled examples before it earns trust. The more immediate win is checking photo quality while the representative is still in the store, since a blurred or wrong aisle image caught then is a dispute that never happens.
Do we need offline capability or is caching enough?
You need offline as architecture, not as a feature. Back rooms, walk in coolers and warehouse clubs have no usable signal, so the app requires a full local database, separate sync queues so a forty photo call does not block the survey upload, resumable transfers and deterministic conflict resolution. Storage management on older devices is real work and losing a representative's morning loses the representative.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How much would it cost to build something like ServiceTitan just for my company?
A true ServiceTitan clone would cost millions and you do not need one, because companies that bring this request to Digital Heroes typically use 20 to 30 percent of its features. Building that slice, shaped to your exact dispatch board and technician day, runs $80,000 to $200,000 depending on offline requirements and integrations. The field service builds that succeed copy a workflow, not a product.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
What features should the first version of a custom field service app include?
Version one needs the daily loop and nothing else: job creation, a drag-and-drop dispatch board, a technician mobile app that works offline, photo and signature capture, and invoicing that reaches your accounting system. Customer portals, route optimization, inventory, and reporting dashboards belong in phase two. The test for every feature is whether a dispatcher or technician touches it every day; if not, cut it.
How does custom field service software work when technicians have no cell signal?
Properly built field software stores the technician's entire day on the device, including job details, forms, photos, signatures, and parts, then syncs automatically when signal returns. The hard engineering is conflict resolution: deciding what happens when a dispatcher reassigns a job while the technician is working it offline. That logic has to be designed before the build starts, because retrofitting offline into an app that assumed a connection is close to a rewrite.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
What security and compliance does custom field service software need?
The baseline is encryption in transit and at rest, role-based access so a technician sees only their own jobs, remote wipe for lost phones, and audit logs on anything that touches money. Run payments through a processor like Stripe or Square so card data never touches your servers and the heaviest PCI burden stays with them. If your crews serve regulated sites such as healthcare or government facilities, say so in scoping, because access and documentation requirements shape the data model.
Can a custom field service app sync with QuickBooks and the payment processor we already use?
Yes, and it should be scoped as a named workstream rather than a finishing task. QuickBooks Online, Xero, Stripe, and Square all offer mature APIs, and a two-way invoice and payment sync typically adds $8,000 to $20,000 to a build depending on how items, taxes, and customers map. The decision that matters most is source of truth: agree which system owns customer records and pricing before development starts, or you will reconcile duplicates forever.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
Who can build a custom field service management software system?
Digital Heroes builds custom field service management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other field service management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Saanvi.
Senior Shopify Engineer · B2B · Delhi · 1 post on the site
Published · Last updated .
