The verdict in three sentences
A structured knowledge transfer costs EUR 8,000 to 20,000 excl. VAT and relies on architecture documentation, reproducible environments, a CI/CD pipeline your team can run itself and 10 to 20 days of pair programming. Without it, a new team needs 30 to 60 development days to understand the code, with production incidents along the way. The transfer must be planned in the original contract, not in the last week of the project.
Deliverables of a successful transfer
A transfer is more than handing over a Git repository and a README file. Your team must be able to deploy, troubleshoot and evolve the application on its own. Here are the deliverables to require, with typical effort on the agency side.
| Deliverable | Expected content | Agency effort | Acceptance criterion |
|---|---|---|---|
| Architecture documentation | C4 diagrams, architecture decision records (ADR), data model | 2 to 4 days | An internal developer explains the system unaided |
| Inventory of environments and access | Dev, staging, production, cloud accounts, DNS, secrets | 1 to 2 days | All access transferred to the client's name |
| Documented CI/CD pipeline | Build, test, deployment and rollback pipelines | 2 to 3 days | The internal team deploys to production alone |
| Operations runbook | Backups, restore, monitoring, incident procedure | 1 to 2 days | Restore tested on a staging environment |
| Pair programming on real tickets | Fixes and features done in pairs | 10 to 20 days | 5 to 10 tickets delivered by the internal team |
| Test plan and coverage | Automated tests, datasets, acceptance scenarios | 1 to 3 days | Coverage measured, tests green in the pipeline |
| Exit security review | Secret rotation, revocation of agency access | 1 day | No agency access left active |
Pair programming is the most important item. An agency developer and an internal developer work real backlog tickets together, then roles swap: the internal developer codes, the agency reviews. It is the only way to pass on what documentation does not say, such as shortcuts in the code or fragile areas.
Transfer budget by application size
| Application profile | Agency days | Budget excl. VAT (EUR 700 day rate) | Calendar duration |
|---|---|---|---|
| Simple portal, 1 team, standard stack | 11 to 12 days | EUR 8,000 | 3 to 4 weeks |
| Business portal with 3 to 5 integrations | 16 to 20 days | EUR 11,000 to 14,000 | 4 to 6 weeks |
| Multi-module platform, public APIs | 22 to 25 days | EUR 15,000 to 17,500 | 6 to 8 weeks |
| Complex platform, sensitive data | 26 to 29 days | EUR 18,000 to 20,000 | 8 weeks |
| Option: post-transfer support | 2 days a month | EUR 1,400 a month | 3 months recommended |
These amounts assume an application that is already well tested. If test coverage is weak or documentation is missing, add 20 to 40 % for remediation before the transfer.
With or without a transfer: the real gap
| Indicator | With a structured transfer | Without a transfer |
|---|---|---|
| Ramp-up days | 10 to 20 days, productive in pairs | 30 to 60 days, low productivity |
| Time to first autonomous release | 4 to 6 weeks | 3 to 5 months |
| Production incidents in the first 3 months | 0 to 2 | 4 to 10 |
| Emergency calls to the former agency | Rare, covered by contract | Frequent, at emergency rates |
| Risk of partial rewrite | Low | 15 to 30 % of code deemed unreadable |
| Estimated total cost | EUR 8,000 to 20,000 excl. VAT | EUR 20,000 to 45,000 in lost time |
The clause that protects all this is written at signature: a reversibility clause that sets the transfer deliverables, their price and a delivery deadline, for example 30 days after the client's request. Negotiated at the end of the project, the same service often costs more and the agency has less incentive to do it well.
Mini case study
Laurent, CIO of a 1,400-employee construction group in Lille, had a site and subcontractor tracking portal built. He wants his two internal developers to take over maintenance.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
- With a transfer: 6 days of documentation and environments, 15 days of pair programming, i.e. 21 days × EUR 700 = EUR 14,700 excl. VAT. During pairing, his developers already ship 8 tickets.
- Without a transfer: 45 person-days of ramp-up at EUR 520 loaded, i.e. EUR 23,400, plus 3 emergency interventions by the former agency at EUR 1,500, i.e. EUR 4,500. Total EUR 27,900.
Laurent saves about EUR 13,200 and his team becomes autonomous in 6 weeks instead of 4 months.
FAQ
When should the knowledge transfer be negotiated?
In the original contract, through a reversibility clause listing deliverables and setting the price. Negotiated at the end of the project, it usually costs 20 to 30 % more.
How many days of pair programming should be planned?
Between 10 and 20 days depending on application size. Below 10 days, the internal team does not handle enough real tickets to become autonomous.
Must my internal team know the same stack?
Ideally yes. If your developers are new to the framework, plan 3 to 5 days of prior training, i.e. EUR 2,000 to 3,500 excl. VAT extra.
What should be recovered first?
Access: cloud accounts, domain name, Git repository, secrets and third-party service accounts. Without them, even the best documentation will not let you deploy.
Can the agency stay on for support after the transfer?
Yes, a package of 2 days a month for 3 months, about EUR 1,400 excl. VAT a month, covers questions and complex cases without lasting dependency.
Let's scope your project. Describe the application to take over (stack, code volume, size of your team): we will price the transfer plan, from EUR 8,000 to 20,000 excl. VAT depending on scope, over a 4 to 8 week schedule. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
