Marcus Biel.

Software handover and ongoing development

Bring in a new team to take over your software

Perhaps your developer is leaving, you’re changing suppliers, or you need help finishing a project that has stalled.

I review the application, find out what it takes to run and change it, and plan the handover with you.

I’m Marcus Biel. I’ll lead the handover and work on the code with your team.

If you need a new development partner

Your business depends on the software, but you need help fixing bugs, adding features or maintaining its technical foundations.

These are common reasons to bring in a new partner.

  • The developer who built the application is moving on.
  • People still use the application, but it’s no longer adequately maintained.
  • A project that is already underway needs a new development partner.
  • New requirements stay on the backlog because the team lacks capacity.
  • You need to know what’s actually working before you invest more.

I check what you already have, what needs immediate attention, and what the incoming team needs before it can ship a change.

What can a new team safely take on?

For an initial conversation, a short description of the application and its main technologies is enough. Before the assessment, I’ll ask which questions you want answered and confirm what I’ll look at. I’ll tell you which documents and access I need.

Depending on the scope, I look at the following areas.

  • the source code and the state of work in progress
  • the frameworks, libraries, and services it relies on
  • documentation and technical requirements
  • the development environment, builds, and tests
  • data storage, integrations, and external services
  • hosting, deployment, and access
  • known bugs and planned features

I check how to build, run, test, and release the application. That tells you what a new team can take on straight away and what needs work first.

What you get from the assessment

Your written assessment covers the following points.

  • what works today
  • missing access, documentation, or decisions
  • technical issues that could hold up the handover
  • what needs attention first
  • a proposal for the first phase of work

You decide which responsibilities to hand over. I then quote for the handover and the first phase of development.

Plan a software handover

From initial assessment to ongoing development

There are two decisions for you to make. After the assessment, you choose the work to commission. Once you’ve seen the first changes, we agree who should handle ongoing development, maintenance and operations.

  1. 1. Gather the documents and access

    I confirm the scope of the review with you. I list anything missing, from the repository and release notes to hosting details and permissions. If your current developers are available, I involve them in the handover.

  2. 2. Assess the software

    I check how to build, run, test and release the application. I examine the code, dependencies, data and integrations within the agreed scope. You receive a written assessment with priorities.

  3. 3. Choose what to hand over

    You use the assessment to decide which tasks come first and what I’ll own. I give you a proposal for the handover and the first phase of development.

  4. 4. Make the first changes

    I set up the development environment, verify the build and release process, and document what the next developer needs. Then I tackle the agreed work, such as a critical bug, an unfinished feature, or an integration. You check the result against the agreed requirements.

  5. 5. Agree on ongoing support

    I’ll help you set priorities, assign responsibility for development, maintenance and operations, and agree on availability.

What I can do after the handover

Fix bugs and add features

I investigate bugs and build features in the order agreed with your team.

That includes implementation, relevant checks and preparing the changes for release.

Update aging components

When dependencies or legacy structures make development difficult, I can plan and carry out focused improvements.

I specialize in modernizing Java applications.

Explore Java modernization

Connect existing systems

You might need to connect the application to a new ERP, CRM, portal, or external service.

I build new integrations or adapt existing connections to the new requirements.

More about APIs and system integration

Which applications can you take on?

I specialize in Java applications and backends, their data flows and associated web applications.

Whether I can take on your application depends on the stack, the state of the application, and the work you need done.

For a first conversation, tell me briefly what the application does and which technologies you use. We’ll work through the technical detail together.

How I helped an automotive team modernize a Java monolith

Have a prototype you want to keep building?

A prototype, including one built with AI, can show exactly how a workflow should feel. The next question is which parts are ready for everyday use.

I look at the code and workflows, including storage, access, integrations, tests and deployment.

Together we decide what we can keep, where more work is needed, and what to build first. That becomes the starting point for development and support.

Request a code or architecture review

Who will look after your application?

I’m Marcus Biel. I’ve been developing Java applications since 2001 and work on architecture as well as code.

When I joined an automotive team working on a Java monolith, we introduced tests through its REST API so we could check the application as we changed it. Read the modernization case study.

I work remotely across Germany, alongside your developers or with specialists I bring in for the project.

More about working with me
Marcus Biel
Marcus BielSoftware developer and architect

Questions about handing over a software project

Can we continue to use the existing software?

Often you can. I first check what the application does reliably and what you need it to do next.

I’ll explain which parts you can keep using and where changes would pay off.

What happens if the documentation is incomplete?

I start with the existing documents and examine the relevant functions and relationships in the code.

People who know the business help me understand actual usage and important rules. The assessment identifies what information is still missing.

I account for onboarding when planning the work.

Do you need all the access credentials at the outset?

For the first conversation, a description of your situation is enough.

We agree what documents and access are needed for the technical review. If source code or essential access is missing, I identify what needs to be made available first.

Does our previous supplier need to be involved?

A handover with the outgoing team can save time. They can explain design decisions, how they deploy the software, and what work is unfinished.

What I can establish independently depends on the code, documents, access and people available. I account for gaps when planning.

What does a software handover cost?

The estimate depends on the size of the application, its stack and documentation, and what it takes to build, test, and run it.

We agree on the scope of the review first. Once you know what state the project is in, I can estimate the handover and the work that follows.

Can you provide ongoing support?

I can continue developing the software and take on agreed support tasks.

We agree on what support covers, who handles day-to-day operations, and how to prioritize new requests.

What’s next for your application?

Tell me what the application does, who looks after it today, and where you need help.

We’ll work out what an incoming team needs to know and where a review should start.

Prefer to talk first? Call +49 171 1151013 or message me on LinkedIn.

Discuss a software handover