Customer follow-up / Compare approaches
A better process, new software, or managed follow-up?
A practical way to choose the right amount of change.
Compare responsibilitiesKeeping a working process is a valid outcome.
01 / Name the gap
Choose the job before the tool.
If nobody knows who should follow up, another place to store the inquiry may not be the first fix.
Start with one recent request. Can your team identify the current step, the person responsible, the next action and a time to check it? If not, use the inquiry worksheet to find the missing piece before comparing products.
This guide compares three approaches: improving a staff process, using software, and having an agreed customer path implemented and maintained with outside help. They can overlap. A managed setup still needs tools and a team; software still needs decisions about how it will be used.
The useful outcome
Choose the smallest change that addresses the actual gap. Keeping a working process is a valid decision.
02 / Compare responsibilities
Three approaches. Different work.
Compare who will do the work after the choice is made. This is an educational decision framework, not a ranking of named products or a promise about any provider.
Scroll the table sideways to compare all three approaches.
| Decision | Improve the staff process | Use software | Managed implementation |
|---|---|---|---|
| What changes? | Your team agrees a clearer record, owner and routine in existing tools. | You add or configure a tool for the specific missing capability. | You and the provider agree which customer process to set up, the setup work, and who looks after each part. |
| Who defines the path? | A named person on your team. | Your team, with whatever setup help is actually included. | Your team and provider agree it together in writing. |
| Who keeps it current? | Your team maintains the record and routine. | Your team owns use and upkeep unless a separate service covers it. | The provider maintains covered work; your team keeps its agreed decisions and follow-through. |
| What must be checked? | People can find the same record, accept the handoff and handle an exception. | Required capabilities, compatibility, access, adoption and total commitments. | Written scope, dependencies, checks before launch, support boundaries and ongoing cost. |
| When might it fit? | The tools are sufficient and someone can reliably own the routine. | The process is understood and a specific missing tool capability is the constraint. | The path needs implementation and covered maintenance that you want a provider to help own. |
03 / Keep what works
When a better routine is enough.
If the same team can work from one clear record and reliably take the next step, start there. You do not need a new subscription to agree who calls a customer back.
- Choose one existing place for the current record.
- Assign one person to the next action, with a backup for absence.
- Record when to review it and what changes or stops the action.
- Check a real handoff together instead of assuming everyone interprets the record the same way.
Keep this approach if it makes the work clear and is maintainable. Reconsider if the routine depends on repeated manual copying, information is inaccessible to the right people, or an important action still has no owner. Those observations identify questions to investigate, not an automatic reason to buy.
04 / Check the capability
When software is the missing piece.
Write the required job in plain language before making a feature list. “The office needs to see the latest appointment time” is more testable than “we need everything connected.”
- Capability: does the proposed tool support the exact job?
- Compatibility: what must remain in your current systems, and what would move?
- Ownership: who configures it, trains the team, checks failures and updates the process?
- Commitment: what setup, recurring service, usage, additional work and exit terms apply?
A demonstration of one feature does not establish the whole customer path. Ask to see a normal handoff and a relevant exception, such as a customer changing an appointment after a reminder was prepared.
05 / Know the boundary
When implementation needs an owner too.
Outside help can be appropriate when the team wants a defined customer path implemented and maintained, rather than taking on all of that work itself. Evaluate the agreed service, not the breadth of its label.
BusinessOS starts with a page for one service, with messages and reminders to help your team follow up. We help choose the service, build or improve the page, and look after the agreed setup each month. Your written scope lists what is included.
Your team still talks to customers, prices the work, makes the sale, and delivers it. Advanced AI, phone services, SMS, more services, and custom work are separate scope decisions.
Questions worth asking
What is being installed? Who handles an exception? What stays with our team? How will we check it before use? What is covered each month, and what would be additional work?
06 / Make a proportionate decision
Bring evidence, not a bigger wish list.
Write down one recent inquiry, the point where clarity was lost, and what you have already tried. Then compare the approaches against that situation.
- If the current routine works, keep it.
- If one capability is missing and your team can manage it, evaluate that capability.
- If implementation and covered upkeep are the missing responsibilities, discuss a managed path.
- If demand, service fit or capacity is the real constraint, investigate that instead.
For a focused fit discussion, book a Local Growth Call. If you already have a call booked, use the preparation guide rather than booking again.
This comparison is a practical choice framework. It contains no tested cost-saving, revenue or product-superiority claim.
Compare the work, not just the feature list.
Use the blank approach-comparison worksheet (CSV) to compare a better staff routine, a software option and a managed proposal against the same customer task. An honest blank is more useful than a guessed checkmark.
For each responsibility, mark included, excluded or unknown and record the actual source. “The demonstration showed it” is evidence of a demonstration; it is not confirmation that setup, daily use or ongoing maintenance is part of your purchase.
Fictional example: An office needs one reliable current estimate. Its existing tool can hold the document, but nobody has agreed who confirms the current version. Buying another attachment feature would leave that responsibility unanswered. A process change may be enough; if a proposal includes implementation help, ask exactly who will define, check and maintain the version rule.
Keep the full commitment visible: setup, recurring service, usage, additional work, dependencies, support boundaries and exit arrangements. Do not fill these from another provider’s example or assume a blank means free. Ask the responsible person to resolve material unknowns before deciding. This worksheet organizes questions; the actual approved offer and agreement determine the service.
Compare the payments listed for the same period
An annual subscription, a monthly fee and your team’s own work are different things. Put two proposals against the same whole-month window. Keep missing prices visible, and keep estimated hours separate from money.
Use the same agreed start, currency and scope for both. Month numbers are relative to that start; this does not verify calendar invoice dates. Record each source and the date you checked it in the approach comparison worksheet. “Known” below means entered by you, not independently verified.
Prices start blank. An unstated charge is unknown, not free. Select “confirmed no separate charge” only when it applies to the entire chosen period. This tool calculates in this page; its own code does not send or save the entries.
A worked example, with invented numbers
These are educational inputs, not JetSynapse or vendor prices. Compare 12 full months in USD. Proposal A has no separate setup charge and one 480 annual payment in month 1, with that schedule confirmed through month 12. Its known subtotal is 480. Usage and other charges remain unknown.
Proposal B has 180 setup inside the window plus 90 each month, starting in month 1, confirmed through month 18. Inside the 12-month window: 180 + (12 × 90) = 1,260. If you separately assume 600 total units at 0.10 each, modeled usage is 60. The subtotal including that assumption is 1,320; it still excludes unknown other charges and taxes.
At a six-month window, A still includes the full 480 annual payment. It is not prorated to 240. B’s known setup and recurring subtotal becomes 720. At month 13, A’s next annual price is unconfirmed: keep the known 480 and list the extra month as unpriced. Do not silently renew it.
Team effort is separate: A’s estimated 8 setup hours plus 1 hour per active month over 12 months is 20 hours. B’s 3 setup hours plus 0.5 per month is 9 hours. Neither the smaller subtotal nor the smaller hour estimate tells you which proposal covers the work you need.
Method: count full scheduled payments from the first payment month, stopping at the earlier of the chosen window or the last confirmed month. Add only known in-window amounts. Flat-rate usage is price × assumed total period units, never multiplied by months again.
This is a bounded payment worksheet, not a complete-cost quote. It supports 1–36 whole months, unchanged fixed payments every 1, 3, 6 or 12 months, and whole-cent flat usage rates. It does not interpret partial months, tiers, allowances, minimum charges, changing prices, credits, tax rules, currency conversions, renewals or cancellation terms. Use a confirmed whole-period amount or leave unsupported charges unknown. Review scope and exit questions separately.