Skip to content

Resources

Software project checklists for decision-makers

Use these whether or not you engage us. They make any vendor conversation more productive and any estimate more accurate.

Before you ask anyone for a quote

  • Write one paragraph on the problem, in business terms. What costs time or money today?
  • List who will use the system and roughly how many of each type.
  • List the tools you use now and which ones the new system must connect to.
  • Separate must-haves from nice-to-haves. Be strict: most first versions need fewer features than you think.
  • Collect three examples of real work: an actual order, a real report, a typical customer question.
  • Decide who on your side will make decisions and how quickly they can respond.
  • Have a budget range in mind, even a rough one. It changes which approaches make sense.

Before you launch

  • Domains, hosting, app store and analytics accounts are registered in your company’s name.
  • Every form has been tested and its messages reach someone who checks them.
  • Old website URLs redirect to their new equivalents.
  • Backups are running and someone has actually tried restoring one.
  • Users are trained, and there is a short written guide for new staff.
  • You know who to call if something breaks on launch day, and when they are available.
  • Privacy policy and cookie notices match what the system really collects.

Before you sign a support or AMC contract

  • What counts as a bug and what counts as a change?
  • What response time applies, and does it cover weekends and holidays?
  • Are security updates and hosting monitoring included?
  • How many hours of small changes are included, and what happens to unused hours?
  • What happens to your data and access if the contract ends?

Longer guides

The articles behind these checklists.

Worked through a checklist and have questions?

Send us what you have. Rough notes are fine.

Request a quote

Request a quote

Loading form
Ask a question

Ask a question

Loading form