Most FSM software sales processes are designed to move you toward a decision, not to help you make the right one. Demo environments look perfect. Case studies feature the best-case scenarios. Pricing conversations happen after you're already emotionally invested.
These 12 questions cut through the sales process and get to what actually matters for your operation.
TL;DR
- Ask these questions during demos, not after signing -- vendors are most responsive before the contract is signed
- Watch for vague answers, deflection to "our team will handle that," or inability to demo live
- The best vendors welcome difficult questions because they know their product handles them well
- Testing core features yourself (mobile app offline mode, QuickBooks sync, payment collection) is more valuable than any sales assurance
- Budget 2-3 demo sessions to properly evaluate 2-3 platforms side by side
The 12 Questions
1. "Can you show me exactly how my workflow would work from job request to payment collection?"
What you're looking for: A live walkthrough using your actual workflow -- not a generic demo. Ask them to start with a new job inquiry, dispatch it, show the technician mobile experience, and collect payment.
Red flag: "I can show you the highlights, and our implementation team will walk you through the rest." Vendors who can't demo the complete workflow often have gaps they're hiding.
2. "What does QuickBooks integration actually do -- and what doesn't it sync?"
What you're looking for: Specific answers: "Customer records sync both ways. Invoices push to QuickBooks when a job is marked complete. Payments reconcile automatically. Here's what doesn't sync: [specific list]."
Red flag: "We fully integrate with QuickBooks." Ask again specifically: "What doesn't sync? What manual steps remain?" Vague claims about integration usually mean a shallow connection.
3. "Show me the technician mobile app in airplane mode."
What you're looking for: Full access to job details, the ability to update status, capture photos, and complete forms -- all without connectivity.
Red flag: "Our app requires an internet connection for most features." In field service, you will have cellular dead zones. An app that doesn't work offline will fail technicians at the worst moments.
4. "What is the total cost -- including onboarding, payment processing, and any add-ons I'll need?"
What you're looking for: A full cost breakdown: base subscription, per-technician fees, payment processing rates, onboarding or setup fees, SMS/email fees, and the cost of integrations like QuickBooks.
Red flag: "Let's start with the base price and discuss the rest later." The rest is often where the real cost lives. Get a full number before you're invested in the platform.
For more detail on pricing structures, see the FSM pricing guide.
5. "How long will implementation actually take, and what do I need to do?"
What you're looking for: A realistic timeline based on your team size, a list of what you need to prepare (customer data export, staff training time, integration setup), and honest acknowledgment of common delays.
Red flag: "We can have you up and running in a day." For any business with existing customers and workflows, this is unrealistic. You need data migration, configuration, and training time at minimum.
6. "What does your customer support look like -- and what happens on a Sunday afternoon when my dispatcher is stuck?"
What you're looking for: Clear SLA: response time, available hours, support channels (phone, chat, email), and whether dedicated support is available at your tier.
Red flag: "Email support with 24-48 hour response." Field service businesses run 7 days a week. Emergency support gaps are real operational risk.
7. "What is the realistic timeline from signup to my first technician using the mobile app on a real job?"
What you're looking for: Specifics: "Most businesses our size have technicians on their first real job within [X] days. Here's what the process looks like..." See also our FSM onboarding guide for what a good onboarding experience looks like.
Red flag: "It depends on your situation." Every answer depends on your situation. Ask what the typical case looks like for a team your size.
8. "Can I export all my data if I decide to leave? In what format?"
What you're looking for: Full data export in a standard format (CSV, JSON) for customers, jobs, invoices, and photos. No lock-in on data you created.
Red flag: "That's something our team would help you with." This is your data. You should be able to export it without vendor assistance at any time.
9. "What has changed in the product in the last 6 months, and what's on the roadmap?"
What you're looking for: Specific feature releases, demonstrating active development. A roadmap (even a general one) showing the direction of the product.
Red flag: Vague answers about "many improvements" without specifics. Check the public changelog if one exists. A product that hasn't shipped meaningful features in 6-12 months is often in maintenance mode.
10. "What percentage of customers at my plan tier actually use [key feature you care about]?"
What you're looking for: An honest usage stat. If 40% of customers never activate the AI scheduling feature you're paying for, that tells you something about real-world utility vs. demo utility.
Red flag: "We don't share those metrics." That means you're buying on faith. Ask instead for a reference customer at your tier who uses the feature heavily and request an intro call.
11. "What are the most common reasons customers leave your platform?"
What you're looking for: Honesty. "Some customers outgrow us and need more enterprise features. Others find the implementation more involved than expected." Genuine answers reveal the platform's actual limitations.
Red flag: "Honestly, we have very low churn." Check G2 or Capterra for recent reviews from churned customers -- they'll tell you what the vendor won't.
12. "Can I talk to two or three customers similar to my business?"
What you're looking for: Fast introduction to reference customers in the same trade, similar size, and with similar needs. The conversation you have with a reference customer is more valuable than any demo.
Red flag: Long delays in providing references, or references who clearly scripted their feedback. Ask reference customers the same hard questions you asked the vendor.
How to Structure Your Evaluation
Run demos with 2-3 platforms in the same week so comparisons are fresh. For each demo:
- Send the vendor your specific workflow questions in advance
- Ask for the same technician mobile app demo for each platform
- Ask all 12 questions above and score the quality of answers
- After each demo, have your team rate the platform on: usability, feature coverage, and confidence in the vendor
Use the FSM complete guide to fill in any feature gaps you're uncertain about.
FAQ
How many vendors should I evaluate? Two to three is the right number. One is not enough for comparison. Four or more creates decision fatigue and the evaluation process itself becomes a distraction from running your business.
Should I take the vendor's "free trial" offer? Yes, but structure it. A free trial without clear goals is just a software tour. Define 3-5 specific workflows you want to test before starting the trial, and test each one in the first few days.
How do I know if a vendor's pricing is fair? Compare against the ROI you calculated for your business. A platform that costs $300/month but saves you $2,000/month in labor and efficiency is priced fairly even if a competitor charges $100/month. See the FSM ROI calculator guide for a structured approach.
Ready to streamline your operations? Start your 14-day free trial — no credit card required.