Customer discovery: 5-person HVAC team paying $500/mo for existing tool

[diese-tech]

Context

Cold call discovery from a local HVAC company owner.

The company is approximately a 5-person team and is currently paying around $500/month for their existing software/tool. The exact product name was not captured clearly because of audio/accent/service-call conditions.

Why this matters

This is direct validation of SwiftDispatch positioning:

Affordable growth option between whiteboards and ServiceTitan-level complexity/cost.

A 5-person team paying $500/month suggests small HVAC companies may already tolerate meaningful monthly software spend if the tool is tied to operations, dispatch, customer communication, or workflow management.

Product interpretation

This customer profile is close to the ideal SwiftDispatch wedge:

• Small field-service team
• Real operational need
• Already paying for software
• Likely cost-sensitive but not unwilling to pay
• Potentially underserved if current tool is expensive, bloated, hard to use, or not matched to their workflow

Follow-up questions for future calls

Try to capture:

1. What tool are they currently using?
2. What do they pay per month and are there extra per-user/SMS/payment fees?
3. What do they actually use it for daily?
4. What do they hate about it?
5. What do they wish it did better?
6. Who uses it: owner, office manager, dispatcher, techs?
7. How many jobs/calls do they handle per day or week?
8. What would make them switch?
9. Would they try a demo account if available?
10. What price would feel like a no-brainer for a lighter tool?

Pricing signal

If a 5-person HVAC team is paying around $500/month today, SwiftDispatch may have room to price as the affordable alternative without racing to the bottom.

Potential hypothesis to test:

• Starter around $99-$149/month for very small teams
• Growth around $199-$299/month for teams that need dispatch + SMS + quoting
• Pro/custom below heavy enterprise tools, but not cheap enough to imply hobby software

Acceptance criteria

• Add this discovery note to the customer research log if one exists.
• Follow up with this owner if possible to identify the current tool.
• Use this as pricing validation input, not final pricing proof.
• Ask future HVAC leads what they currently pay before showing SwiftDispatch pricing.

Risk

Do not overfit to one call. This is a signal, not a conclusion. The important insight is that small teams can already have real software budgets when the pain is operational enough.

[diese-tech]

Additional discovery note: stated pain point

Follow-up from the same cold call: when asked about the owner’s specific pain point, the answer was not software cost or dispatch complexity. The owner said the main issue is keeping employees during the busy months.

Interpretation

Do not assume SwiftDispatch directly solves this yet. Employee retention during peak season could be caused by many things:

• pay or incentives
• overtime / burnout
• scheduling chaos
• unclear assignments
• poor communication
• workplace culture
• heat / working conditions
• lack of support from office staff
• admin burden on technicians
• better offers from competitors
• seasonal labor expectations

Product relevance hypothesis

SwiftDispatch may help only if the retention problem is partly caused by operational chaos, such as:

• techs getting unclear job details
• excessive back-and-forth calls/texts
• bad scheduling visibility
• surprise assignments
• too much admin work after jobs
• lack of follow-through from the office
• peak-season overload feeling unmanaged

If the root cause is pay, culture, or working conditions, SwiftDispatch is not the primary solution.

Suggested follow-up questions

For future conversations, ask:

1. Why do employees usually leave during busy months?
2. Is it because of workload, pay, scheduling, communication, or something else?
3. What does a rough busy-season day look like for a tech?
4. How many calls/texts does the office send to a tech per day?
5. Do techs complain about unclear job info or last-minute changes?
6. How do you assign jobs today?
7. Do techs have to do paperwork, quotes, or customer updates manually?
8. What would make a busy-season day less frustrating for the team?

Decision

Treat this as customer discovery, not a product requirement yet. The next step is to learn whether retention pain is operationally driven. If yes, SwiftDispatch can position around reducing chaos for owners, office staff, and technicians. If no, avoid pretending the product solves it.