Prepare for development
Explain what an application or website needs to do and who it is for.
CNSLT/005Project definition
A clearer idea.
A better-defined project.
We turn your idea into a definition that can be priced and developed: who will use it, what it must do and what belongs in the first delivery. A shared foundation for your team and providers.
Define what matters.
Define the first release.
A proposal that is hard to explain is hard to assess. We turn business needs into user journeys and requirements the people building it can understand.
Request comparable proposals
A definition that makes proposals and estimates easier to compare.
Organise requests
Separate essential needs, later improvements and decisions that remain open.
Check feasibility
Identify integrations or conditions that need checking before committing to implementation.
From a business need
to an agreed scope.
We work through the questions that shape development. The final document sets out what the first version should do and how it will be validated.
Starting point
- Objective
- Users
- Restrictions
DefinitionOutcome
- Requirements
- Priorities
- Scope
From questions
to a practical plan.
These are the elements we define in the proposal. The final scope depends on your starting point and business priorities.
/001Objective and users
We agree on the problem, the people who will use the solution and the key user journeys.
/002Functions and limits
We document what belongs in the first release and what is left for a later phase.
/003Dependencies and requirements
We identify data, access, integrations and decisions that shape the development work.
/004Acceptance criteria
We define how features will be checked and what information is still needed to assess the next step.
/005Handover and continuity
We hand over the access, documentation and guidance covered by the agreed scope. Follow-up or maintenance is defined separately if commissioned.
From a need
to a defined first delivery.
(4)Clarify the objective
We review the need, the people involved and what would change in their work if the project succeeds.
Map the journeys
We define tasks, data and decisions to explain how the solution will be used.
Separate the phases
We prioritise first-version features and identify exclusions and outstanding dependencies.
Prepare the brief
We deliver requirements and acceptance criteria for comparing proposals and checking the delivery afterwards.
Clarity to decide.
Clarity to move forward.
Decisions with context
Recommendations start with how you work. A tool that suits another business may not fit your budget or processes.
Evidence and limitations
We state what has been reviewed, what is outside the scope and what needs further investigation. A focused review is not presented as a comprehensive audit.
No commitment to development
You can use the findings to decide with your team or another supplier. If you continue with SBI Digital, we define a separate implementation phase.
Before we start.
(5)Can I use the result to request a quote from another supplier?
Yes. The specification can support discussions with other suppliers. Each supplier must review their own terms, estimates and assumptions before committing to the work.
Does it include designs or a prototype?
We can include these if they help resolve uncertainty, but they must be agreed in the scope. A functional specification does not automatically include a complete design or development.
Does the first conversation count as a consultation?
The first conversation helps us understand your needs and assess whether we can help. A detailed assessment or review has a scope, deliverable and price agreed before work begins.
Do I have to commission development afterwards?
No. You can use the analysis with your own team. Implementation, coordination with other suppliers or further support is quoted separately if you need it.
Do you need access to all our systems?
We request only what is needed for the agreed scope. We can start with interviews, documentation and demonstrations; any additional access is agreed with a clear purpose and permissions.
Engineering × Design.
For the next step.