Dedicated Team or Another Contract Extension? How to Size an Ongoing Development Need
If the same development work has outlived its first contract term, the contract is no longer a reliable measure of the need. Estimate how long the work will really continue, check where its knowledge lives, and compare options over that same period on equivalent terms. If the need is continuing, plan a continuing team around it.
Nextwo ·
This guide is for technology, procurement and finance leaders at Saudi companies who keep renewing short contracts for the same development work.
Picture a team that brings in two developers on a three-month contract to clear a backlog. Three months later the backlog has changed but not shrunk, so the contract is extended. Then extended again. Each renewal is approved on its own, under time pressure, and each one asks the same narrow question: extend or stop?
That question hides the one that matters. The contract term describes how the capacity was bought. It says nothing reliable about how long the work will last.
The short answer: if the same work has outlived at least one renewal and is still on your roadmap, treat it as a continuing need. Plan a continuing dedicated team around it, with costs compared like for like and knowledge that stays in your systems. Keep short terms for work that has a real end and an owner who takes it over.
Why the contract term is the wrong measure
Short terms are a sensible way to buy capacity for a gap you expect to close. The problem starts when the gap does not close and the buying model stays the same.
Each renewal then repeats the same costs: another approval cycle, another round of uncertainty for the people doing the work, and another moment when someone may leave and take undocumented knowledge with them. Because each decision is made at the end of a term, there is rarely time to step back and ask whether the arrangement still matches the need.
The two worksheets below are designed for that step back. Fill them in with the engineering lead who owns the work and, where possible, the procurement or finance owner of the contract.
Worksheet 1: How long will this work really continue?
Answer each question from evidence (the backlog, the roadmap, support tickets and the renewal history), not from the current contract.
| Question | Evidence to check | Points to a continuing need when |
|---|---|---|
| What does this capacity actually work on? | Tickets and commits over the last term | The work is spread across a product, not one deliverable |
| Is there a defined end deliverable with acceptance criteria? | Statement of work, project plan | There is no end deliverable, or it keeps moving |
| How many times has it been renewed, and was the original end date met? | Contract and approval history | It has been renewed at least once and the end date has passed |
| What does the next 12 months of roadmap need from these skills? | Roadmap, planned releases | The same skills appear in later releases |
| Will someone need to maintain what is being built? | Support model, ownership map | Maintenance would fall to the same people or skills |
| What happens if the capacity stops at the end of this term? | Ask the product and engineering owners | Delivery stalls or knowledge is lost |
Then classify the need:
- Temporary: a defined deliverable, a clear end, and a named owner who takes over afterwards. Short terms fit.
- Continuing: no defined end, a roadmap that keeps needing the same skills, and a result someone must maintain. Plan for a continuing team.
- Mixed: a stable core of continuing work with temporary peaks. Plan a continuing core and buy the peaks separately.
Worksheet 2: Where does the knowledge live?
Continuity is not only about keeping the same people. It is about whether the knowledge needed to run and change the product survives a change of people. List the knowledge this work depends on and mark where it is recorded today.
| Knowledge item | Recorded in your systems? | If the person left at renewal | Action |
|---|---|---|---|
| Architecture and design decisions | Partly, in old tickets | The reasons behind decisions are lost | Start a decision log in your repository |
| Business rules and edge cases | No, held by one developer | Rework and defects | Document rules alongside the code and tests |
| Deployment steps and environment access | Partly, in chat history | Releases depend on one person | Write a runbook and review access |
| Integrations and external contacts | No | Delays when an integration breaks | Record owners, contracts and escalation paths |
| Known defects and workarounds | Yes, in the tracker | Low risk | Keep it current |
| Test data and test cases | Partly | Old defects return | Move them into the shared test suite |
The entries above are illustrative; replace them with your own. Every row marked no or partly is a cost you pay again each time someone leaves, whatever the contract model. A continuing team stops each short contract end from being a fresh point of risk. People can still leave in any model, and written knowledge is what reduces the cost when they do.
Compare like with like
Once you know the real duration, compare options over that period, not over one contract term. A comparison is only fair if both sides cover:
- The same period: the duration from Worksheet 1, for example 12 or 24 months.
- The same roles and seniority: not a senior engineer against a junior one.
- The same scope: what is included, such as employment costs, benefits, workspace, equipment and management.
- The same responsibility split: who directs the work, who accepts it and who handles people operations.
- Your internal costs: approval cycles, onboarding of replacements and knowledge transfer, estimated by your own team.
Use your own quotes and estimates. A general savings percentage from any source, including a supplier, is not a substitute for a comparison of your roles, your period and your scope.
A simple way to see the repeated costs is to count events rather than money. In a hypothetical case where a contract for the same two developers is renewed every three months for a year, the year contains four purchasing decisions: the first contract and three renewals. If one developer changes at any renewal, there is at least one handover and one onboarding. Your team can put its own time estimates against each event.
What a continuing dedicated team changes, and what it does not
A continuing dedicated team is planned around the need you measured, not around the next renewal date. The team stays on your products over time rather than ending with each contract, so knowledge builds up in your own repositories, documentation and tools.
In Nextwo's dedicated team model, the team works from Jordan or Egypt, only on your products, in your tools and processes, and reports to your technical leadership. You choose who joins, set technical direction and priorities, and accept delivered work. Nextwo supports team planning, recruitment and candidate assessment, employs the team and runs payroll, HR and workplace operations. Nextwo quotes each team for its roles, seniority and scope, and handover and documentation practices can be agreed in the proposal.
What it does not change: you still need someone who sets priorities and accepts the work, people can still leave, and the agreement, not the name of the model, sets the actual terms. That is why Worksheet 2 matters in every model.
When short terms are still the right choice
- A defined deliverable: a migration or integration with a clear end and acceptance criteria.
- A peak on top of a stable core: extra capacity for a launch while the core team continues.
- A brief specialist need: a skill you need for weeks, not for the life of the product.
- An exploratory phase: a short test before you commit to a direction.
In each case the test is the same: is there a real end, and who owns the work afterwards?
A worked example (hypothetical)
A hypothetical company runs a customer portal with two backend developers and one QA engineer on three-month contracts. The contracts have been renewed several times.
Worksheet 1 shows no end deliverable: the roadmap has portal releases planned through next year, and the same people fix production issues between releases. The need is continuing. Worksheet 2 shows that the deployment steps sit in one developer's chat history and that several pricing rules are documented nowhere. Every renewal is a knowledge risk.
The company compares a continuing team of the same three roles against further renewals over 24 months, with the same seniority, the same included costs and its own estimates of the internal time each renewal takes. It decides to plan a continuing team for the portal and to bring in a separate short-term specialist for a payment-gateway integration that has a clear end date. In parallel, it writes the runbook and moves the pricing rules into the repository, so the knowledge stays with the company whoever is on the team.
Next step
Complete both worksheets for the capacity you renew most often. If they show a continuing need, plan the team around that need: the roles, the period you compared and the knowledge that must stay in your systems. Nextwo's dedicated team page explains how a dedicated team works under your direction and what Nextwo handles.
Frequently Asked Questions
How many renewals should trigger this review?
There is no universal number. A practical trigger is the first renewal after the original end date has passed with the work still going, or the second renewal of the same capacity for the same work.
Is a continuing dedicated team always cheaper than renewing short contracts?
Not necessarily. The answer depends on the roles, seniority, period and scope you compare. Use a like-for-like comparison of your own quotes and internal estimates instead of a general percentage.