Start with one representative customer job.
Choose a typical piece of work, not an unusually simple demo. For an installation business that might mean a customer with two sites, a quote for several devices, a partial supplier delivery and a support call after installation. Write down who touches that job and where they have to re-enter information. Use the same example when reviewing each platform, so you compare the workflow rather than the presentation.
- Name the customer, site, contact and equipment using fictional data.
- Include an exception: a delayed delivery, extra material or reassigned engineer.
- Ask sales, service and the person preparing billing to review the same example.
Check what the customer record actually connects.
Ask to move from a customer to their sites, contacts, documents, open tickets and installed equipment. Then open the customer from a ticket and check that the context is still available. A useful evaluation is whether a colleague who has never handled the account can understand what was agreed, what has happened and who is responsible next.
- Can one customer have several contacts and service locations?
- Can staff find documents and attachments beside the relevant work?
- Do integrations refer to the same customer, or create another disconnected directory?
Follow the accepted quote into delivery.
Ask the demonstrator to accept a quote and show what happens next. Check whether job creation includes a review of assignment and operational details. Compare the agreed quantities with the materials actually used. If your engineers install fewer devices than ordered, or use additional materials, those differences should remain understandable without rewriting the original agreement.
- Identify where the accepted commercial details are preserved.
- Find the operational record for notes, labour, attachments and materials.
- Check what ready for billing means, and distinguish it from an invoice that has been sent.
Test one serialised device from receipt to support.
If equipment is part of your service, a stock count is not enough. Ask where a received device is held, how its serial number is recorded and how installation links it to a customer. Then simulate a later service request. You should be able to explain which unit is affected and how it relates to the original job. If your business does not handle physical equipment, this may be a lower priority than scheduling or project work.
- Follow a supplier receipt to a stock location.
- Review the material used on the job against the quantity ordered.
- Search for the installed serial number from the customer service workflow.
Evaluate integrations by their outcome.
An integration logo does not tell you which information moves or what staff can do with it. For telephony, ask how a call matches a contact and becomes related activity or a ticket. For network monitoring, ask when an event becomes work, which customer it belongs to and what happens on recovery. Record the required licences, permissions and configuration separately from the platform subscription.
- Request the exact workflow you need, using a realistic example.
- Check what happens when a contact cannot be matched or a connection is unavailable.
- Agree who maintains customer mappings and configuration as the business changes.
Compare the whole operating arrangement.
List the staff who need access and the functions each team uses. Ask about onboarding, data preparation, third-party services, support and any requirements that need a tailored arrangement. A low subscription price is useful only if the package covers the work you need. Avoid assuming an integration includes the connected provider’s own licences.
- Separate monthly user charges from other costs that need confirmation.
- Ask how existing records will be reviewed before a move.
- Decide who will own the rollout, train colleagues and check the first jobs.
Where Rymley fits this evaluation.
Rymley connects CRM, deals and quotes with sales orders, tickets, inventory and customer assets. Its Wildix and UniFi connections bring communications and network events into customer workflows. Use the checklist below to discuss the parts your team needs and compare the Core, Connect and Tailored packages. Specialist requirements should be assessed explicitly rather than assumed from a broad software category.
- Explore the customer and service workflows together.
- Bring one anonymised job and the systems around it to the conversation.
- Confirm package fit against your requirements before choosing.
Your software demonstration checklist
Use this list during your evaluation. Tick the points as you discuss them; selections stay on this page only.