Due diligence & rebuilds · For private equity

Clarity before the deal, a platform that holds after it.

Before, during and after a transaction, DNA Technology is the team you call in for the technical work that has a date on it: due diligence, stack changes and mergers, rebuilds and migrations. Fixed scope, senior people, and we leave when the job is done, unless you ask us to stay and run it.

  • A PE-owned platform rebuilt in parts
  • 24/7 on a regulated payments platform
  • Senior engineers only, since 2018
See our cases
Your scope
Fixed, and agreed before we startEvery package has a fixed scope and a fixed fee.
Your team
Senior engineers who would own the fixThe people who assess are the people who can build. We work alongside your due diligence advisor.
Your company
Its own team stays in chargeDraft findings go to the CTO first. We plan the engineering team the work needs. We don’t reorganise the company.

Where to start

Find out what you have. Then change it.

Start at the moment you are in. Every package has a fixed scope and ends in a plan. The work that follows is done by the same senior team, or by yours.

  1. Data room open

    Before you sign

    Technical DD Sprint

    The risk
    The investment case rests on technology the deal team cannot judge.
    You get
    A red-flag memo for the investment committee (IC), a cost-to-fix range and points for the share purchase agreement (SPA).

    2–3 weeks, fixed to the IC date · access set by the seller

    After closing: a shorter assessment

  2. First 180 days

    After you close

    Most common first step

    Stack & Risk Assessment

    The risk
    You own technology you saw only through due diligence.
    You get
    What you bought, what will break, what it costs to fix and in what order.

    4 weeks · full access

    Next: a mission team or a rebuild

  3. Hold period

    When you add or scale

    Integration & Build-out Blueprint

    The risk
    Two stacks to merge, or a product that must scale, and nobody has scoped the work.
    You get
    A target architecture, the team it needs, cost and timeline with ranges, and a fixed offer for the first part of the work.

    4–6 weeks · full access

    Next: a fixed-scope rebuild

  4. 12–18 months ahead

    Before you exit

    Exit Readiness Review

    The risk
    The buyer’s due diligence will find the debt and use it in the price.
    You get
    A buyer’s view of the technology, and a fix list that pays back before the sale.

    3–4 weeks · full access

    Next: pre-exit fixes

Do the work

Already know what needs doing, for example a platform that holds back the plan? Start here.

  • Can be your first stepWhen the work cannot wait

    Senior mission team

    A small task force of senior engineers who work in sprints with your tech leads. You set the mission and the time box. The team owns the work, then hands it back to your team.

    After any package, or as your first step

  • When the scope is known

    Fixed-scope rebuild

    We rebuild, migrate or merge the platform in parts. Each part has its own scope, outcome and price, agreed before it starts.

    After an assessment, a blueprint or an exit review

  • When the platform must not go down

    Managed operations

    We run and improve what was built: monitoring, on-call, security and cloud cost, by the people who know the platform best.

    After a rebuild or a mission

The entry offer

Know what you bought in four weeks.

Most funds start here, right after closing, as the first step of the 180-day plan. The fund gets one clear picture. The company’s team gets a ranked list of actions, so the work starts within the first month.

After you closeFor the operating partner, with the company’s CTO

Stack & Risk Assessment

What did we buy, and what should we fix first?

Within four weeks you know what you bought, what will break, what it costs to fix and in what order, with a roadmap a senior team can start on at once.

  1. Week 1DiscoverAccess, documents, interviews
  2. Week 2VerifyHands-on code and cloud review, one release observed
  3. Week 3AssessRatings and risk ranking, draft shared with the CTO first
  4. Week 4PlanRoadmap and readout to the fund

What we look at

  • Architecture and code
  • Cloud, infrastructure and cost
  • Security and compliance
  • Delivery capability and key-person risk
  • Readiness to integrate a bolt-on
  • Delivery and AI: how fast work reaches production, and whether AI tools raise output

What you get

  • A two-page summary for the fund
  • A risk and readiness report, rated per area, with evidence
  • A prioritised roadmap with effort ranges
  • Cost to fix and cost to run, including cloud savings
  • A delivery baseline the fund can track
  • A readout with the fund and management

What we need from youAn executive sponsor in the company, and access to code, cloud and tickets within three working days of the start.

Not includedThe fixes themselves, penetration testing beyond automated scans, and legal or commercial due diligence.

What comes nextYour team runs the roadmap with us advising, or a mission team or a rebuild takes it on. You decide after the readout.

How the work runs

Work in parts. Stop after any of them.

You never commit to a whole programme up front. The work is split into parts, and each part has its own scope, outcome and price, agreed before it starts. After each part you decide what happens next.

  1. First part

    The outcome that matters most

    Scope, outcome and price agreed before we start. Often 3–6 months.

    Continue, change course or stop
  2. Next parts

    The rest of the plan

    Each one scoped and priced when you are ready for it.

    Hand over or keep us on
  3. Afterwards

    Your team, or managed operations

    We hand the platform back, or stay to run it.

What stays after we leave

New technology your team can keep running

A rebuild only pays off if it lasts. We work with AI agents in every step, and we leave the company with more than new code.

What you get

  • A platform documented as we go, so the knowledge stays in the company
  • Ways of working with AI agents that your engineers learn in the work, not in a course
  • Practices we have already used on other rebuilds and migrations, not experiments on your system
  • An engineer radar for your team: where each engineer stands with AI-native work today, and where to grow next
  • No surprises at the readout. The CTO sees our draft findings before the fund does.
  • We plan the team, not a reorganisation. We shape the engineering team the plan needs, together with its leaders.
  • You own what we build. Delivery work belongs to the company. EU delivery under Swedish contracts.
  • Remote, with visits when it counts. Our team works from the EU and travels to you for the kick-off, key workshops and the readout.

Why DNA Technology

We build and run platforms like the ones you buy.

Our engineers have taken over, rebuilt and run other companies’ platforms, including PE-owned ones. That is what we bring to an assessment, and why our estimates hold.

An advisory report

Tells you what is wrong

It rates each area and lists the risks. The cost to fix is an estimate, and another team does the work later, often with a different estimate.

An engineering assessment

Tells you what it costs to fix, because we would fix it

Engineers who would own the fix estimate the cost of every finding. Our assessment works alongside your due diligence advisor, and the same team can start the week after the readout.

  • Consumer platform · PE-backed

    A legacy product, rebuilt in parts

    For a PE-owned consumer platform, we rebuilt an older product on a modern stack, moved its data onto the company’s main platform, and used AI to speed up a manual review process. For the same company, a two-week, read-only review of its AWS production environment ranked every finding by impact.

    Rebuilt in parts · AI-assisted

  • Payments · PCI DSS · DORA

    A payments platform in four European countries

    We built the AWS platform from day one and run it around the clock with a platform team and a security team. We led the PCI DSS certification end to end.

    24/7 operations · regulated

  • Online marketplace · PE-backed

    A large classifieds marketplace

    We started with one specialist and grew to a team of four senior engineers working on AWS, DevOps and refactoring inside the company’s own platform teams.

    AWS · DevOps · refactoring

  • Since 2018Senior engineers onlyArchitects, platform, SRE and security engineers
  • AWS partnerSelect TierFor rebuilds and migrations on AWS
  • Regulated workPCI DSS, 24/7 operationsOn platforms that cannot go down
  • LocationStockholm HQ · Engineering in PolandEU delivery. A reference call on request.

For operating partners: we use the same assessment format in every company, so you can compare your portfolio on one scale.

Get started

Start with the company as it is today.

Tell us where you are in the deal and what worries you. We will propose the package that fits, its scope, and the date it ends.

No fund behind you? The same work fits a CEO or CTO facing a merger, a rebuild or an investor’s due diligence.

Careers

Senior people, real ownership, no layers.

View open roles (opens in a new tab)