Technical consulting

Software architecture and technical consulting

Sometimes you do not need a team. You need an honest answer: whether the platform will hold at ten times the load, whether the codebase you are about to acquire is worth the price, whether the rewrite your team is proposing is really necessary. We review, measure and write it up in language a board can read.

What's included

Architecture review

Service boundaries, data model, coupling and failure modes, assessed against where the business is heading.

Code and delivery review

Code quality, test coverage, branching and release process, and the practical reasons your team's delivery has slowed.

Infrastructure and security review

Cloud configuration, access control, secrets, backups and restore testing, and the state of your dependencies and known vulnerabilities.

Performance audit

Profiling the paths that are actually slow (queries, N+1 problems, cold starts, cache misses, front-end Core Web Vitals) with before-and-after measurements.

Scalability and migration planning

Capacity modelling, cost projections and a sequenced migration plan that isolates the risky steps and keeps them reversible.

How we work

  1. 01

    Define the decision

    We agree on the decision the review has to inform. A review with no decision behind it produces a document nobody acts on.

  2. 02

    Access and discovery

    Read access to the repository and infrastructure, plus interviews with the people who run it day to day.

  3. 03

    Assessment

    Static review, profiling and load measurement, with findings ranked by risk and by cost to fix.

  4. 04

    Report

    A written report covering what is fine, what is a real risk, what it would take to address, and what we would do first.

  5. 05

    Walkthrough

    A session with your team and, where useful, a separate one for non-technical stakeholders.

  6. 06

    Optional implementation

    If you want us to implement the recommendations, we can. The review still stands on its own and is priced separately.

Tools and technology we use

  • PostgreSQL
  • AWS
  • Docker
  • Kubernetes
  • GitHub Actions

Frequently asked questions

How long does a review take?
Typically one to three weeks, depending on the size of the codebase and how much of it is in scope. Focused audits, such as a single performance problem or one security question, can be shorter.
Will you recommend a rewrite?
Rarely. Most systems that feel beyond saving have three or four specific problems that can be addressed incrementally, and a rewrite is usually the most expensive way to fix them. When a rewrite really is the right call, we will show you the reasoning.
Do you do technical due diligence for acquisitions?
Yes. We cover code, architecture, infrastructure, security posture, dependence on key people and technical debt, and report in terms an investment decision can use.
Do we have to hire you to implement the findings?
No. The report is yours, written so your own team or another vendor can act on it.
Can you work with our in-house team?
Yes. The most useful reviews are done alongside the team that built the system.

Book a technical review

Tell us what decision you are trying to make and what worries you. We will propose a review scope and the questions it will answer.

Start the conversation