# Our method: in the deal and in software

Two disciplines, one standard: results you can use straight away. In a deal that means reliable statements for price, contract and plan. In software it means applications that run.

## Transaction Advisory: From the data room to the exit

Every transaction follows the same basic structure, yet no two are alike. Our approach comes from more than 120 technology due diligences and aligns every phase with one question: what does IT mean for the value, risk and timeline of the deal?

1. **Capture:** Data room, management interviews and system landscape in the first days. A clear question list instead of bundled requests.
2. **Assess:** Red flags, dependencies on the seller, CapEx and run-rate model. Every finding tied to its effect on price, contract or plan.
3. **Decide:** A clear statement for the investment committee, plus TSA needs and points for the SPA and the integration plan.
4. **Execute:** Separation or integration with a Day 1 plan, TSA governance and a shared cockpit, from signing to the end of the TSA.
5. **Create value:** Costs, processes, digitalisation and growth through to exit, with advisory board support if you wish.

- **Numbers, not traffic lights**: Every risk gets an order of magnitude in euros and months, not just a colour.
- **Deal language**: Results prepared so that the investment committee, lawyers and management can use them directly.
- **Day 1 from the start**: The due diligence already lays the groundwork for the separation concept and the 100-day plan.
- **Tools, not slides**: A structured question list, a valuation model and INCISION as the shared platform for TSAs, tenders and risks.

## A virtual development team for AI-assisted software

> Our virtual development team consists of 13 specialised AI agents under a lead architect. It is fully set up and adapted to each client: to their rules, architecture, security requirements and systems. A human owns requirements and approvals, the agents deliver code, tests and documentation in a fixed quality process.

- **Lead architect**: assesses complexity, plans the architecture, signs off
- **Requirements**: turns wishes into acceptance criteria
- **Backend**: business logic, interfaces, data processing
- **Frontend**: interfaces, state, responsive behaviour
- **Database**: schema, access rules, migrations
- **Integration**: APIs, ERP and CRM integration, webhooks
- **Security**: authentication, hardening, veto before every release
- **Quality**: tests, edge cases, validation
- **UX and design**: user flow, design system, accessibility
- **DevOps**: deployment, environments, monitoring
- **Review**: code review, refactoring, performance
- **Documentation**: README, decisions, release notes
- **Learning**: records lessons so mistakes happen only once

- Code review
- Refactoring
- Performance
- Security audit
- Tests
- Lint and types
- Documentation
- Architecture review