Start with the quote you already send
Bring a representative document with customer details removed or replaced for the test. Check whether the tool reads the scope, total, tax wording, exclusions, and contact details correctly. Try a less tidy document too: a scan, a multipage file, or a quote with an optional item.
Missing information should be obvious and editable. The system should not silently guess a customer address or treat an optional upgrade as part of the agreed total. Ask how the original document remains connected to the extracted fields so your team can check discrepancies.
Watch what happens after a customer replies
Ask the vendor to show three conversations: an ordinary scope question, a request for a discount, and a clear yes. The first should use verified information. The second should follow your approval rules. The third should stop unanswered reminders and identify the next step.
Then ask a question the system cannot answer. Look at both the customer's message and the task created for the owner. A neat escalation label is not enough if the owner still needs to search several screens to understand what happened.
Understand channels and integration boundaries
Confirm which contact channels are available, what setup is required, and how customer preferences and opt-outs are recorded. 'Supports SMS' might still require a provider account or sending approval. Verify your actual setup before planning a launch date around it.
For integrations, ask what moves in each direction. Importing a quote, reading its status, receiving an update, and writing a changed status back are separate capabilities. Ask which are live today and test a revision to the source quote. A logo on a page is not a description of synchronization behavior.
- What data is imported, and how often?
- What happens when the original quote changes?
- Which system owns the current status?
- Can a failed update be retried without duplicate messages?
- How do staff disconnect the integration or export their records?
Calculate the cost of your normal month
List your typical number of quotes, users, messages, and attachments. Ask what each plan counts, which limits stop work, and which generate extra charges. Include setup effort and the time staff spend reviewing exceptions, not just the subscription price.
Compare that cost with a clearly defined workload you want to reduce. Avoid assuming every open quote will become a sale. A more useful pilot question is whether the tool reduces repetitive follow-up work while preserving accurate replies and clear owner control.
Run a short acceptance test
Choose a small set of controlled test quotes and use your own contact details. Include a missing phone number, an already-sent quote, a never-sent quote, a customer question, a decline, and a go-ahead. Write down what should happen before running the test.
Have the person who will use the software complete the process without coaching. Can they find a customer's message history, understand the next action, and correct the quote? If those tasks are difficult, a longer feature list will not solve the daily experience.
Pursuo is designed around quote follow-ups and approved business answers. If you are evaluating it, bring the same checklist to a demo. Confirm current availability and sending setup rather than treating this guide as a promise that every capability described is included.