Skip to content

Join us

We're always looking for talented engineers.

View open positions

Next events

Want to join one of our next events? Check our calendar.

View calendar

About this service

Build scalable, maintainable software with our experienced engineering teams. We deliver high-quality code and best practices that help your product succeed.

Go to service

Newsletter

Investor Insights

Field notes from technical due diligence, for people who invest in software companies.

Every few weeks we write to the investors we work with about what we have seen inside software companies recently: the claims that held up, the ones that did not, and the questions that would have surfaced the difference earlier. Reading it requires no code.

Written by the team behind 190+ technical due diligences for investors across Europe.

Get the next issue

Free, every few weeks, unsubscribe in one click. We send a confirmation link first, so nobody can sign you up without your say.

Every issue

Four short parts, written to be read between two meetings

Three things we saw

Findings from recent technical due diligences, with the company names removed and the lesson kept.

Three questions for your next board meeting

Each finding turned into something you can ask a founder or CTO without reading a line of code.

A word from Andreas

Our CEO Andreas Creten on whatever is on his desk that month, from the price of a GPU to why roadmaps drift.

Where to meet us

Leadership dinners, conference talks and the occasional book launch.

From the latest issue

Claims and artefacts

Issue ten looked at what happens when the sentence on the slide and the thing it describes quietly part company. Three findings from this summer, names removed.

A speed claim can be honest and still miss most of the journey.

Response times in thousandths of a second, measured only inside the company's own software. The customer's trip to it and back was never timed.

Process words can describe their own absence.

“Agile” meant the owner deciding in conversation what got built next. Nothing reviewed a change before customers saw it.

The roadmap in the board pack and the work that happened are two different documents.

A plan approved, an urgent request landing on top of it inside the week, and nobody pricing the switch.

Subscribers get the full issue, including the three questions to take into the board meeting. The archive stays with subscribers, so the next issue is the first one you will see.