Technical decisions whose cost shows up a year later, made with someone who has built them.

Code and architecture audit, technology selection and a modernisation plan. You get concrete recommendations and decisions, not another report for the drawer.

Describe your project
Two people discussing a system architecture in front of a laptop screen

When it makes sense

  • You are choosing a technology for a new product and want an opinion from someone who is not selling a particular solution.

  • A system that used to work now slows the company down: every change takes long and breaks something else.

  • You are taking over code from another vendor and do not know what state it is in.

  • Your team is arguing about architecture and you need an independent assessment.

  • You want to know whether to modernise, rewrite or leave the system alone.

How we work

  1. Talk about the goal

    We establish which decision you need to make and what matters for it: cost, time, risk, people.

  2. Review

    We read the code, architecture and configuration, or compare technology options. We talk to the people who know the system.

  3. Recommendations

    You get a short document: what is good, what is a risk, what to do first and roughly what it may cost.

  4. Plan and support

    If you want, we help carry out the plan: we lead the changes ourselves or support your team.

An example from our own product

In our Japanese learning apps we had to decide how to add AI without sending user content to an unknown place. We chose our own AI backend protected by Apple App Attest, with no storage of user content, plus control of cost and abuse.

See the Japanese learning apps
The "Today" screen of the Japanese learning app

Questions we hear most often

Will I get a finished report?

You get a short document with recommendations and an order of actions, plus a call where we go through it with you and your team.

How long does an audit take?

For a typical system, from a few days to two weeks. We give the timeline after the call about the goal.

Do you only advise on the technologies you use yourselves?

We are most confident in Java, Kotlin, Spring Boot, Next.js and Swift. In other areas we will say plainly where our knowledge ends.

Do I have to commission the implementation from you afterwards?

No. The recommendations are yours and you can carry them out with your own team or another vendor.

Tell us what you are facing.

One sentence about what bothers you most today is enough. We will work out the rest in a call.

Describe your projectExample: Japanese learning apps

Other services

System integrationThe same data is typed into two places, and a report is stitched together from several exports.Product developmentYou have an idea for an app or platform and need a team that will take it all the way.Engineers for your teamYou have a team, but you lack capacity or experience in a particular technology.