A new need is not automatically a new product. If the current panel already holds orders but the report is missing, payment sits apart or there is no partner screen, we look at the system that is running first.
When the code or the API is reachable, the new module sits beside it. Order data stays where it is, and any pause in the work is written into the plan. If there is no access, or the structure can no longer carry the job, we say so and separate the part that has to be built fresh.
The first release is limited to the screen being added. Rewriting the whole system is a different job and is not hidden inside the same proposal.
The team keeps working where it already knows the way. What is new is the step that was missing.
- A technical look at the current system
- A new screen or an API connection
- A move that leaves the data in place
- A from-scratch part written separately