An offshore project has just been delivered. The Japanese client has a list of improvements and must decide whether to commission them separately or keep a dedicated development team. For SIers, CTOs and DX project managers, a useful question is whether the same team needs to carry its knowledge of the system and business into the next releases. Consider three factors before deciding.
Map the work after go-live
Put known requests on a timeline and separate work that is ready to start from ideas still awaiting clarification. If the next item is a one-off upgrade with a clear goal, scope and endpoint, consider project-based outsourcing. If several releases are planned for the same system, identify where knowledge from one release matters to the next and when the team may run out of ready work. A long wish list alone is no staffing plan.
Check who can keep setting priorities
A dedicated team needs someone on the client side who can choose the next work, confirm business rules and respond when the team is blocked. Try ranking the next release: what goes first, what can wait, and who decides when priorities collide? If no one can handle this regularly, narrow the scope or put decision-making in place before committing dedicated capacity.
Compare total effort over the same period
For individual projects, include clarification, estimates, handover and ramp-up if the team changes. For a dedicated team, include the cost of retaining capacity, the client’s time spent managing priorities and possible gaps between releases. Compare both models over the same period and against the same expected outcomes. Track one-time transition effort and unconfirmed assumptions separately, so a unit rate is never compared directly with a total cost.
Hypothetical example: improving an order management system
A Japanese SIer has just delivered an order management system. The client needs a one-time delivery note format change and plans to revise order approval rules over several releases. The note format change could be a separate project with its own acceptance criteria. A dedicated team could take on the approval flow if a priority owner and ready work are in place. Agree on a review date, look at accepted improvements and work ready for the next release, then decide whether to retain or reduce capacity or return to project-based commissioning.
Choose a setup with TECHNEST
TECHNEST has years of experience designing and developing business systems for the Japanese market. Share the work you expect after go-live and who can prioritize it. We can use those two inputs to discuss a project, a dedicated team or a combination of both.




