Diligence and advisory
A verdict on a software asset, written for the people paying for it. The judgement we would act on ourselves.
- Starts with
- A scoping call and code access
- Covers
- Architecture, data, team
- Typically
- 3 to 5 weeks
- 01ReadCode, cloud, documents and team interviews.
- 02ReviewArchitecture, data and delivery, risks priced.
- 03ReportRed flags, the cost to fix and a 90‑day plan.
- MarketplaceArchitect as a ServiceSenior cloud architecture judgement in blocks of 40 hours, drawn down flexibly across up to two months. Every block produces written output: decision records, review reports and a roadmap you can act on.See the listing
Same four steps,a week or two years.
In all: 3–5 weeks.
In all: 3–5 weeks.
In all 3–5 weeks. 4 weeks shown.
- FrameWeek 1
- JoinWeek 1
- DeliverWeeks 2–4
- HandoverWeek 4
Architecture, data and delivery are reviewed, with the costs and risks priced.
The work lands in small pieces you can see and use. When the evidence changes, so does the plan.
Frame
Week 1- Day 1
We agree the questions with you, or with your investors.
- Day 1
Join
Week 1- Week 1
Read access to code, cloud and documents, and interviews with your team are booked.
- Week 1
Deliver
Weeks 2–4- Week 2
Architecture, data and delivery are reviewed, with the costs and risks priced.
- Week 3
Findings are checked with your engineers, so nothing in the report is a surprise.
- Week 2
Handover
Week 4- Week 4
A written report: the red flags, what they cost to fix and a 90-day plan, then a read-out.
- Week 4
Hello from Malmö
Adamass
Come with the work that feels heavy. We will make it light.
- IKEA
- Nasdaq
- Tele2
- Thomson Reuters
- The Guardian
- Liverpool FC
- Stabenfeldt
- Eyeradar
