Who this text is for and why
This text is addressed to the purchasing department and the IT manager, who prepare an order for a new feature in a working system. An example could be a new type of permit, an additional report, another integration with the plant's systems, or a change to the flow of reports.
Disputes over scope have a simple mechanism. The client describes the need, the vendor understands it in its own way, and the mismatch surfaces only at acceptance. The recommendations below move the moment of finding the mismatch to the start, when a correction costs the least.
Recommendations 1 and 2: describe the effect for the user and the acceptance criterion
Instead of describing the technical solution, describe what the user should see and do: who, in what situation, which action they take, and what result they should get. A good description fits on one page and can be checked by clicking through it.
For each feature, add acceptance criteria written as testable sentences. For example: after a permit is approved by a second person, the permit changes its status, and the history records who approved it and when. A criterion that can be turned into a test scenario is proof of acceptance and protects both sides.
Length of the pilot before full deployment
Recommendations 3 and 4: integration boundaries and maintenance
State which systems the feature is to work with. InnerWeb is a software producer whose software integrates with the client's existing systems (access control, time and attendance, HR, ERP), so development on the InnerWeb side does not replace the readers or cards of the client. The order should describe this clearly so that nobody assumes a hardware scope.
Agree how the feature will be maintained after acceptance. The documentation lists maintenance options: a server and licences with an SLA, maintenance of transmitters including battery replacement as part of the service, and rental of mobile devices, settled with a monthly subscription. A new feature is part of the same model, not a separate commitment without support.
Recommendations 5 and 6: change control and testing before deployment
Ask how the vendor controls changes to the code. A good standard is static analysis, style checks and unit tests on every change, with the merge blocked until the result is green, plus a second, independent review of the change against its description and the domain rules. In our documentation the second-review mechanism is described as designed and built, but in the state of August 2026 not yet deployed to production. We state this openly, because an honest account of the current state is part of a good contract.
Require that the acceptance criteria of the new feature are included in the browser test package as scenarios. The feature is then protected against regression at every later update, and acceptance after a change comes down to running the ready tests.
Recommendations 7 and 8: pilot and settlement
For a larger feature, consider a pilot. The system is offered on subscription with a one-time implementation cost, and a pilot runs from 3 to 6 months before full deployment. The pilot is an opportunity to check the feature in real work before extending it to the whole plant.
Development prices are set individually, after analysing the scope, and every amount depends on complexity and integrations. To compare offers, ask for a breakdown: analysis, development, testing, deployment, maintenance. A breakdown makes comparison with other vendors easier and shows whether tests and maintenance are included in the price at all.
- a description of the effect for the user on one page
- acceptance criteria as testable sentences
- a list of systems and the integration boundary
- agreed maintenance of the feature after acceptance
- a description of the vendor's change control
- acceptance criteria in the browser test package
- a 3 to 6 month pilot for a larger feature
- a price breakdown into analysis, development, testing, deployment and maintenance
Typical sources of disputes and how to prevent them
The most common dispute concerns words such as adjusted, simplified or convenient, each of which means something different to the client and to the vendor. A real example prevents them: one realistic scenario, a screen and the expected result. The second dispute concerns changes made during delivery. An agreed route for reporting changes, with an assessment of their impact on scope and timing, prevents it.
The third dispute concerns acceptance. If the acceptance criteria are turned into test scenarios, acceptance is the result of a test rather than an opinion. The fourth dispute concerns who maintains the feature after deployment. The answer should be in the contract, together with the response time for reports.
Video
Frequently asked questions
Does developing a feature mean replacing readers or cards?
No. InnerWeb is a software producer and integrates with the client's existing systems, so developing a feature does not replace access control hardware.
How is maintenance settled after deployment?
The documentation lists the options: a server and licences with an SLA, maintenance of transmitters including battery replacement as part of the service, and rental of mobile devices, settled with a monthly subscription.
Why a pilot for a new feature?
A pilot lasting from 3 to 6 months lets you check the feature in real plant work before it is extended to the whole site.
Let's describe the scope of the new feature together
Bring the need and we will prepare with you a description of the effect, acceptance criteria and a pilot proposal. Pricing is individual.
Let's talk