Agree the scope
We define the users, screens, connections and test cases. The proposal sets out the price, schedule and responsibilities.
We agree what the application needs to do, who will use it and how it will be tested. Then we design, develop and prepare it for your team to use.
Before development
The scope names the application or module, the tasks it must support and the checks required for acceptance. Additional work is assessed separately.
We define the users, screens, connections and test cases. The proposal sets out the price, schedule and responsibilities.
You can try the application as we develop it. We review the main tasks with your team and record any changes to the scope.
We check the agreed cases, set up access and explain how to use the software. Hosting and support are specified in the proposal.
Hosting and maintenance
We can use Kenea-managed infrastructure or your own environment. The proposal states who controls the domain and code, which backups are included and how to report an issue. Support hours and any ongoing work are agreed separately.
Interactive example
Explore the steps and review points. This illustration does not connect to a real system.
Example process
01 / 05
A document, request or signal enters.
02 / 05
The data and agreed rules are checked.
03 / 05
The point where work stops or repeats.
04 / 05
A person or rule validates what follows.
05 / 05
The result is saved or assigned for review.
Choosing the approach
We check whether your existing software already has the feature you need.
We agree which records move between systems, when they move and how to check the result.
We define the rules, approvals and exceptions before building the automation.
We design the screens, permissions and database needed for the agreed work.