Practical resources, no email wall
The checklists and templates we use internally with clients. Take them and use them — including with another vendor, if that is who you end up choosing.
Start here if you are scoping a project
ERP Selection Checklist
Forty-two questions covering process fit, data migration, licensing, customisation limits and exit terms — grouped by what to ask before, during and after a vendor demo.
Request the checklistSoftware RFP Template
A structured request-for-proposal document that gets comparable responses from vendors instead of six documents you cannot line up side by side.
Request the templateCloud Migration Playbook
Assessment, dependency mapping, rehearsal, cutover and the ninety-day cost review — with the questions to settle before you sign anything.
Request the playbookApplication Security Baseline
The minimum controls we ship in every business application, written so a non-technical stakeholder can verify them with their own vendor.
Request the baselineProject Estimation Worksheet
A simple model for sanity-checking a vendor quote: modules, roles, integrations, migration complexity and contingency, with worked examples.
Request the worksheetGo-Live Readiness Checklist
Data validation, user training, cutover rehearsal, rollback plan, support rota and the first-week war room — everything to confirm before you flip the switch.
Request the checklistJargon, translated
If a vendor uses one of these terms without explaining it, ask. A good partner can always explain the trade-off in business language.
Shortcuts taken during development that make future changes slower. Some is deliberate and sensible; the problem is debt nobody is tracking or repaying.
Replacing an old system one module at a time while it keeps running, instead of a single high-risk switchover. Slower on paper, far safer in practice.
One application instance serving many customers with their data logically separated. Cheaper to run and patch; requires careful isolation design from day one.
Continuous integration and delivery — automated build, test and release pipelines. In business terms: fewer manual mistakes and the ability to ship a fix the same day.
Service level agreement — the contractual response and resolution times by issue severity. Check whether it covers response only, or resolution as well.
Servers and networks defined in version-controlled files rather than configured by hand. It means your entire environment can be rebuilt reliably after a failure.
Want any of these sent over?
Email us the name of the resource and we will send it across — no marketing sequence attached.