TECHNOLOGY ASSESSMENT

Technical insight before an important software decision.

A major change, acquisition or investment in software should not rest on functional impressions or supplier promises alone. We show how the software is built, so you can decide based on what is there.

Discuss what you want assessedSee the three assessments
When assessment is relevant

When a decision needs technical evidence

The outcome is not fixed in advance. An assessment can also show that limited action or no change is needed. Delivery by Link2Leap is never a condition.

  1. 01

    You are unsure whether an application is technically healthy enough to keep investing in.

  2. 02

    A modernisation or replacement is planned and its technical consequences are still unclear.

  3. 03

    You are buying, selling or investing in a software company or product.

  4. 04

    Management and technical teams see the software's condition and risks differently.

Three assessments

Choose the assessment that fits your decision

Each assessment answers a different question. Depth and approach are set out on each assessment's own page.

01

Software Audit

For a broad view of an existing application: technical quality, maintainability, technical debt, testability and development risk.

Explore Software Audit02

Architecture Review

For questions about how the system is built: structure, boundaries, responsibilities, coupling and dependencies.

Explore Architecture Review03

Technical Due Diligence

For technical evidence in an acquisition, investment or other transaction, scoped to what the deal needs to support.

Explore Technical Due Diligence
Which assessment fits

Five questions to choose the right route

We go through these questions together in a first conversation. Sometimes a combination or a smaller scope makes more sense.

  1. 01

    Is the concern the overall technical health of an existing application?

  2. 02

    Is the uncertainty mainly about architecture, system boundaries and dependencies?

  3. 03

    Is the decision part of an acquisition, investment or transaction?

  4. 04

    Which decision should the assessment support, and who makes it?

  5. 05

    How much depth is needed to make that decision?

A software decision that needs technical insight?

Tell us which decision is coming, which software is involved and what you need to know. Together we'll decide which assessment fits and how deep it should go.

Discuss what you want assessed