The agency sales process for selling software to small service businesses

Short answer: a good agency sales process for selling a service business one app that replaces its stack, plus bots and automations, has seven stages: prospecting, first call, discovery session, a demo built on the prospect's own business, proposal, close, and kickoff. Each stage has one goal and a clear exit criterion, so you always know whether a deal moves forward or stops. With owners of 3 to 25 person businesses, the demo on their own data does most of the selling, and the full cycle often fits in two to six weeks.

This guide covers the process: stages, exit criteria, the call script and follow-up. For packaging and the pitch, read how to sell custom software.

Why small service businesses need their own sales process

In a 10-person HVAC shop, the owner is the buyer, the user, the IT department and the person answering the phone between jobs. So keep every meeting short and useful on its own, earn trust by understanding their business before showing features, and show their own customers and job types on a screen rather than slides.

The seven stages, one by one

1. Prospecting

Goal: get conversations with owners who have the problem you solve.

What you do: pick one or two niches you know (HVAC, plumbing, cleaning, landscaping). Build referral sources that talk to those owners every week: bookkeepers, equipment suppliers, trade associations and your existing clients. A bookkeeper who sees messy invoicing every month is your best source. Offer something in return, such as a referral fee.

Exit criteria: the owner agreed to a first call at a set time.

Typical length: ongoing. Budget a few hours each week.

2. First call (qualify)

Goal: decide in 20 to 30 minutes whether this is worth more of your time and theirs.

What you do: use the script below. Find the main pain, who decides, rough budget and timing. Book the next step before you hang up.

Exit criteria: a real pain the owner wants fixed this quarter, the decision maker is on the call or joins the next one, and a discovery session is booked.

Typical length: one call, scheduled within a week of first contact.

3. Discovery session

Goal: understand how the business really runs, from first phone call to paid invoice.

What you do: walk the workflow with the owner and the office manager. List the tools they pay for, where data gets typed twice, and what falls through the cracks. Ask for real data: a customer list, job types, a recent quote. Our discovery questions list covers this session in detail.

Exit criteria: you can describe their workflow back to them and they agree. You have enough data to build a demo.

Typical length: 45 to 60 minutes, often on site or on video.

4. Demo built on their business

Goal: show the owner their own business in the new app.

What you do: before the meeting, build a first version with their customers, job types and quote layout. When an app can be set up in minutes, you can do this for every serious prospect, not just the big ones. In the meeting, change things live ("add a field for the gate code") and let the office manager drive.

Exit criteria: the owner says some version of "this is how we work" and asks what it costs or how to start.

Typical length: 30 to 45 minutes, within a week of discovery.

5. Proposal

Goal: put scope, price and timeline in writing, in words the owner uses.

What you do: send it within 48 hours of the demo. Lead with outcomes (tools replaced, hours saved), then scope, then price. See our proposal and SOW templates and the pricing guide.

Exit criteria: the owner has read it and you have a date to talk about it.

Typical length: 1 to 2 days. Walk them through it live.

6. Close

Goal: a signature and a first payment.

What you do: answer the last objections, adjust scope rather than price when you can, and agree on a start date.

Exit criteria: signed agreement, setup fee or deposit paid, kickoff date booked.

Typical length: a few days to two weeks.

7. Kickoff and handover

Goal: turn the signature into a team that uses the app every day.

What you do: move the data, run the app next to the old tool briefly, train the team, then hand over the keys. Our software implementation plan covers this stage week by week.

Exit criteria: the team works in the app daily and the old tools are cancelled or scheduled to be.

Typical length: one to four weeks, depending on the data.

Agency sales pipeline stages at a glance

Use these as the stages in your own pipeline. The "odds" column is a rough feeling to help you prioritize, not a forecast. Track your own close rates after a few months and replace it.

A deal stuck in one stage for two weeks with no next step is not a deal. Move it to "lost" or "later".

Qualifying small business owners

Classic BANT (budget, authority, need, timing) works, with a few changes for owners of 3 to 25 person businesses:

• Budget: owners rarely have a software budget. Ask what they pay for tools today and what an extra office person would cost. That is their real budget.
• Authority: the owner decides, but the office manager (or a spouse who does the books) can block. Get them into discovery.
• Need: a pain they feel every week: quotes not followed up, double entry, a schedule on a whiteboard. "It would be nice" is not a need.
• Timing: avoid their busy season. For HVAC, spring or fall beats a heat wave. Ask, "When is a calm month for you?"

Disqualify early and politely. A no on the first call saves you a demo and a proposal.

Copy-ready discovery call script (20 to 30 minutes)

Adapt the words, keep the structure.

Opening (2 minutes) "Thanks for making the time, [Name]. I know mornings are busy, so I'll keep us to 25 minutes. I help [trade] businesses replace the pile of apps they pay for with one app that fits how they already work: calls and texts, quotes, schedule, jobs and invoices, plus a bot and automations that handle the follow-up."

Agenda (1 minute) "Here's what I'd suggest: I ask you a few questions about how things run today, you ask me anything you want, and at the end we decide together if a next step makes sense. If it doesn't, that's fine too. Sound good?"

Questions (15 to 20 minutes)

1. "Walk me through what happens from the moment a customer calls until you get paid."
2. "Where do you write things down? Paper, spreadsheets, an app?"
3. "Which tools do you pay for each month? Roughly how much in total?"
4. "Where does the same information get typed twice?"
5. "What falls through the cracks today? Quotes not followed up, callbacks missed?"
6. "If you could fix one thing this year, what would it be?"
7. "Who else would use this every day? Who should be part of the decision?"
8. "Is there a time of year when a change like this would be easier?"
9. "If this worked, what would it be worth to you each month?"

Recap (2 minutes) "Let me check I got it right. You're paying for [tools], your office retypes [data] into [tool], and [pain] is costing you [effect]. The one thing you'd fix first is [priority]. Did I miss anything?"

Next step (2 minutes) "Here's what I'd suggest next. Send me a few things, like your customer list and a recent quote, and I'll build a first version of your app with your own data. Then we meet for 45 minutes and you see it working. Does [day] at [time] work, with [office manager] there too?"

Handling common objections

"We already use Jobber" (or another field service tool). "Makes sense, a lot of shops do. What do you like about it, and what do you work around?" Show their workflow, not a feature list. If nothing hurts, let them go.

"We use QuickBooks for everything." "Keep it for the books. The question is what happens before the invoice: the quote, the schedule, the job. That's where the double entry lives." Check that the app you sell connects to their accounting tool before you say so.

"Spreadsheets work fine for us." "They do, until two people edit the same one, or the person who built it is on vacation." Ask to see the spreadsheet. The pain usually shows in a minute.

"It's too expensive." Go back to the discovery numbers: tools replaced, hours saved, jobs not lost. If it is still too high, cut scope, not price: start with one module.

"My team won't use it." "Then let's plan for it." Involve the office manager in the demo, keep only the screens they need, train in one short session, and check in two weeks after launch.

"I don't have time to switch." "You won't do the switch, we will. We move your data and you keep your current tool until the new one is ready." Then propose the calm month they named on the first call.

Follow-up cadence after the proposal

Most proposals are not refused. They are forgotten. A simple cadence:

• Day 0: send the proposal and book a short review call.
• Day 2: short message: "Any questions so far? Happy to walk your office manager through it."
• Day 5: share something useful, such as a short screen recording of the demo app with a change they asked for.
• Day 10: call. Ask directly: "Is this still a priority, or should we look at it later?"
• Day 20: final note: "I'll close your file for now. If things change, I can reopen it in a day."

Each follow-up should add something new.

Track all this in your own CRM

Run your agency on the kind of tool you sell. It doubles as your demo.

• One pipeline with the seven stages above, and the exit criteria written in each stage's description.
• One deal per prospect, with the source (bookkeeper, supplier, client referral) so you know which channel pays.
• A task for every next step, with a date. No deal without a next step.
• Notes from each call on the deal, so anyone on your team can pick it up.

Doing this on Alori

On Alori, your agency gets its own CRM where you can set your pipeline with the stages above, log each prospect as a deal and keep tasks and notes on it. The app you sell replaces the client's stack in one place: customers and deals, quotes, booking, schedule, jobs, invoices, employees, calls, texts, email, campaigns and the website, with a bot that answers customers and runs automations. For the demo, you can build the prospect's app as a client account, then hand the account over by inviting the owner when they sign. If you turn on white label, the client sees your agency's name and logo. Alori bills the client directly and you earn the markup you set on what they pay. Calls on Google Meet or Zoom can be recorded with the Alori Recorder Chrome extension, which saves a transcript as a meeting in your app. More in the Partner Program and the Partner playbook.

FAQ

How long is a typical agency sales cycle with small businesses? Often two to six weeks from first call to signature. It is shorter when the owner feels a weekly pain and the demo uses their own data, and longer when you start in their busy season.

Should the demo be free? Usually yes, but only after a discovery session where the owner confirmed the pain and shared data. Some agencies charge for discovery and credit it against the setup fee.

What is the most important question on a discovery call? "Walk me through what happens from the moment a customer calls until you get paid." The answer shows where the double entry and the lost jobs are, which is what you sell against.

How many follow-ups should I send after a proposal? Four or five over about three weeks, each with something new: an answer, a short video, a call. Then close the file politely and keep the door open.