Requirements & scope
A clear description of the users, workflows, priorities and agreed features.
Services / 01
For teams that need a tool shaped around their work: a customer-facing web application, an internal system or a connection between existing services.
Discuss a projectYou know what needs to happen, but your current tools do not support it. Requests are handled in messages, the same information is entered twice, or a new service needs its own application.
The exact deliverables, responsibilities and release plan are agreed before development begins.
A clear description of the users, workflows, priorities and agreed features.
Screens and interactions that show how people will complete their tasks, reviewed before implementation.
The agreed web application or internal tool, with connections to existing systems where access and APIs allow.
Checks against agreed workflows, deployment and guidance for using and managing the delivered system.
Each step makes the next decision clearer. Scope, timing and responsibilities are shaped around the project.
Talk through the problem, the people involved and the tools you use today.
Define priorities, deliverables, responsibilities and how the result will be accepted.
Review the user flows and build the agreed solution in stages, with feedback along the way.
Check the key workflows, integrations and access with the team before release.
Put the system into use, share operating guidance and agree any next phase or support.
A short description of the problem, who experiences it and the tools you currently use is enough for a first conversation. A finished specification is not required. Share example workflows without confidential customer or personal data.
We first review the systems, available APIs, permissions and data formats. Where integration is possible, we plan around the tools you already use. Any limitations or necessary changes are discussed before committing to the scope.
They depend on the workflows, features, integrations and available access. We clarify these during discovery and agree the scope and delivery plan before development. New requirements are discussed as changes to that plan.
Handover covers how to use and manage the delivered system. Maintenance, hosting responsibilities, further development and response arrangements are agreed for each project; ongoing support is not assumed to be included.
Tell us what you want to build or what could work better.