Avenryx Systemsguides
How to scope a custom software project before you spend anything
Scope is not a list of features. It is a set of decisions about who the system serves, what it must not do, and which parts of the process are allowed to change.
Outcomes
- Name the single outcome the project must deliver
- Define the first release by user type, not feature count
- List integrations and confirm their APIs exist
- Decide what stays manual for now
- Agree acceptance criteria before design
- Identify the compliance obligations early
- Set a change-control process on day one
- Plan the second phase so phase one can stay small
Problems this solves
Scope written as a feature list
Describe the workflow and the outcome; features are the answer, not the question.
Exceptions left out
The exceptions are where most of the effort sits, so they belong in the scope from the start.
No priority order
Without ranked priorities, everything becomes phase one and the budget is decided by omission.
How delivery runs
- 01
Describe the current process
One page per workflow, including who does what and where time is lost.
- 02
State the target
A measurable operational outcome, not 'a modern system'.
- 03
List systems and data
Every system involved, how it is accessed, and the state of its data.
- 04
Rank ruthlessly
Must-have for phase one, wanted later, explicitly out of scope.
Realistic timeline
Week 1
Workflow documentation and system list.
Week 2
Prioritisation and a written scope with explicit exclusions.
What moves the price
Integration count
Usually the largest driver; list every system honestly up front.
Role count
Each additional user role adds screens, permissions and test cases.
Data migration
Historic data quality is the most common source of overruns.
Where projects go wrong
Scope written without the users
The people doing the work daily know the exceptions; scope written only with managers misses them.
No exclusions listed
What is out of scope must be as explicit as what is in.
FAQ
Questions buyers ask
Who should be involved?+
The people who do the work daily, plus one decision-maker who can settle disagreements quickly.
How detailed should it be?+
Detailed enough that two suppliers would quote roughly the same number.
You already have the idea. Let's define what comes next.
Available in 12 languages