Article Software

Software requirements checklist: what to prepare before you hire a developer

Everything worth preparing before you brief a software developer, grouped into a checklist you can fill in over a week.

In this note

A grouped checklist of what to prepare before briefing a developer, so estimates are comparable and the build starts on solid ground.

7 min read
A product manager writes requirements in a notebook beside a laptop showing app wireframes and paper sketches.

Published by

VSN Editorial

Date

Oct 14, 2026

Read time

7 min read

The quality of a software estimate depends on the quality of the brief. A one-line idea gets you a guess. A clear set of requirements gets you a proposal you can compare, question and hold a vendor to.

This software requirements checklist covers what to prepare before you hire a developer. You do not need technical knowledge to complete it. Most items are about your business: who does what, what rules apply and what must not go wrong. Expect to spend a few sessions on it with the people who do the work today.

You will not have every answer, and that is fine. An honest “we don’t know yet” tells a good vendor where discovery work is needed.

How to gather the answers

Requirements written by one person at a desk tend to describe how work should happen, not how it does. The gaps show up later as change requests. A little legwork before you write anything avoids most of them.

  • Talk to the people who do the work. Ask them to walk you through a normal day and a bad day. The bad day is where the business rules hide.
  • Collect the real artefacts. Forms, spreadsheets, email templates, printed checklists and reports show what information actually moves through the process.
  • Watch one or two tasks being done. Ten minutes of observation often reveals steps nobody thinks to mention, such as copying a reference number between two screens.
  • Note the workarounds. Every “we keep a separate sheet for that” is a requirement or a sign of a missing rule.
  • Agree on words. If finance says “order” and sales says “deal” for the same thing, settle it now. Consistent terms make the brief, the software and the training easier.

Once you have these notes, the checklist below becomes a matter of sorting rather than guessing.

The problem and the goal

Start with why the software should exist. Developers make better decisions when they understand the business reason.

  • One or two sentences on the problem, in business terms (“orders are re-typed into three systems”).
  • What happens today: tools, spreadsheets, paper, people involved.
  • What a successful first release would change, in measurable terms if possible.
  • Who decides on scope, budget and acceptance on your side.

Users and roles

List everyone who will touch the system, including your own staff who will support it.

  • User groups (customers, staff, managers, partners, administrators).
  • What each group needs to do, and what each must not be able to see or change.
  • Rough numbers of users per group, now and in a year.
  • Devices and settings: office desktops, phones in the field, poor connectivity, languages.

Workflows and business rules

This is the heart of the brief. For each important workflow, write the steps in plain language, then the rules that apply.

  • The main workflows, ranked by importance.
  • For each one: who starts it, the steps, who approves, and how it ends.
  • Business rules: limits, calculations, approval thresholds, deadlines.
  • Exceptions you deal with regularly, and how they are handled today.
  • Notifications: who needs to know what, and when.

A short example helps: “A sales rep creates a quote. Quotes above an agreed discount need a manager’s approval. Approved quotes are emailed to the customer as PDF. If the customer accepts, an order is created in the accounting system.”

Data

Software is mostly about data. Be specific about what exists and where it lives.

  • The main records the system manages (customers, orders, cases, assets).
  • Existing data to migrate, where it is, and how clean it is.
  • A small anonymised sample export, if you can share one safely.
  • What data is sensitive or personal, and any retention or deletion requirements.
  • Reports and exports people need.

Do not send passwords, payment details or real customer records in an early brief. Anonymised samples are enough at this stage.

Integrations and existing systems

  • Systems the software must connect to (accounting, CRM, payment provider, email, identity provider).
  • Whether each system offers an API or export, and who owns the account.
  • Which connections are essential for launch and which can wait.
  • What should happen when a connected system is unavailable.

Quality, security and operations

These items are often left out of briefs and added later at extra cost. Write down what you expect, even roughly.

  • Browsers and devices that must be supported.
  • Accessibility expectations, especially for public-facing screens.
  • Performance expectations for key screens or reports.
  • Security and access requirements: sign-in method, roles, audit history.
  • Where the system should be hosted and who will own the hosting account.
  • Backups, monitoring and who responds if something breaks.

Ownership, budget and timing

  • Who will own the source code, accounts, domains and credentials.
  • Approximate budget range, including a contingency.
  • Target timing, and any fixed dates (a season, a contract, an event).
  • What support you expect after launch.
  • Who on your team has time to review, test and give feedback.

A brief does not need to be long. It needs to be specific about the parts that matter.

— VSN Editorial

A one-page brief template

If the checklist feels like a lot, condense it into one page with these headings. It is enough to start a useful scoping conversation:

  1. Problem: what is slow, costly or error-prone today.
  2. Users: who uses the system and what each group needs to do.
  3. Top three workflows: in plain steps.
  4. Data and integrations: what exists, what must connect.
  5. Must-haves for launch: and what can wait.
  6. Constraints: budget range, timing, hosting, compliance.
  7. Open questions: what you do not know yet.

What a good vendor should give back

A complete brief should lead to a better response, not just a lower number. When you share your requirements, look for a proposal that does more than repeat them:

  • Questions that show the vendor read the brief and spotted gaps or risks.
  • A clear list of deliverables, with what is in and out of scope.
  • Written assumptions and dependencies, including what you must provide and by when.
  • Milestones with demonstrations and acceptance checks.
  • Third-party costs, hosting and support listed separately.
  • Ownership terms for code, accounts and data.

If a proposal promises everything in your brief with no questions and no assumptions, treat that as a warning sign rather than good news.

If you are still deciding whether to commission software at all, read our build vs buy guide first. For SaaS products, pair this checklist with how to scope a SaaS MVP.

Key takeaways

  • Explain the business problem before describing features.
  • Workflows, rules and exceptions matter more than screen ideas.
  • Be specific about data: what exists, how clean it is and what is sensitive.
  • Write down quality, security and ownership expectations so they are priced in.
  • “We don’t know yet” is a useful answer; it shows where discovery is needed.

Software requirements checklist: common questions

Do I need a formal requirements document before contacting a developer?

No. A clear one-page brief is enough to start. A good developer will help you fill gaps through questions or a discovery phase. The checklist helps you arrive prepared.

How detailed should business rules be?

Detailed enough that two people would implement them the same way. “Managers approve large discounts” is vague; “discounts above an agreed percentage need a manager’s approval before the quote is sent” is usable.

Should I share real data with a developer during scoping?

Share anonymised or sample data at first. Real personal or financial records should only be shared under an agreement, through secure access, and only when needed.

What if my requirements change during the project?

They usually do. Agree a change process up front: how changes are requested, estimated, approved and scheduled, so budget and timing stay visible.

When your checklist is ready, VSN can turn it into a scoped proposal with deliverables, assumptions, milestones and acceptance checks. Learn about our software and SaaS development work or send us your brief.

Filed under Software

Keep reading

Related notes