A custom system can fit beautifully and still create the wrong commitment. An existing platform can look ordinary and do exactly what the organisation needs. Begin with the work that must become easier, then compare the responsibilities each option creates.
Write the workflow before the feature list.
Describe three journeys that must succeed. For a member organisation, that might be a renewal, a change to directory permissions and an event registration. Include the exception: an expired card, a changed membership or a full event. A feature list can hide a broken hand-off between otherwise capable screens.
For each journey, name the person who starts it, the information they need, the acceptable result and who handles a failure. Use synthetic records when asking suppliers to demonstrate it. A familiar-looking dashboard is not acceptance evidence.
Put all routes on one horizon.
Choose a period appropriate to the commitment, then compare setup, subscription or maintenance, migration, internal transition time, training and the cost of leaving. Mark unknowns explicitly. A three-year subscription compared with a development deposit is not a useful comparison.
Keep two columns for staff time: one-time transition and continuing operation. Ask what work remains with your team even after the supplier has finished. Do not count a saving unless the old work actually goes away.
Use an evidence ladder.
- Published: the feature is documented, with its limits.
- Demonstrated: the supplier completes your scenario on the relevant plan.
- Accepted: the responsible operator confirms the result meets the written requirement.
- Committed: price, scope, responsibilities and necessary specialist reviews are resolved before signing.
Progress on one rung does not prove the next. The member-portal example shows why a free trial can leave online-payment testing unresolved even when the feature exists on a paid plan.
Ask for the exit while everyone is helpful.
Request a representative export. Open it. Identify which records, relationships, documents and history it preserves and what needs a separate process. An export button is useful; a person who knows how to use the result is more useful.
The appropriate specialist should examine security, contracts and any regulated obligations. Keep those questions separate from the owner's operating decision so an attractive cost comparison is not mistaken for technical assurance.
Five questions to send a supplier.
- Which of our three required journeys needs extra development, and why?
- Which plan, limits and external services does the demonstration assume?
- What is excluded from migration, support and the quoted recurring cost?
- What remains manual for our team after launch?
- Can we inspect a representative export before committing?
When an independent brief earns its place.
Commission one when the commitment matters, there are two or three real routes and a public-source check or clearer comparison could change the decision. Bring the essential workflows, broad cost allowances and the question you cannot settle. A review is most useful before the deposit and delivery date have already decided the answer.
Read the full worked example to see the resulting recommendation and one-page decision sheet.
Your decision, examined
Get a recommendation for your situation.
One defined question, checked public evidence and up to three options. CAD 1,500 plus GST/HST, prepared by your reviewer. Three business days after verified payment.
See the review scopeAsk about your decision