Technology consulting
An honest read on your codebase, your architecture, and what to do about it.
Overview
A second opinion, written down
Sometimes the useful thing is not more delivery — it is knowing whether the current approach will hold, what the real risks are, and which of them are worth money right now.
Every engagement ends with a written report: what we found, what it costs you today, and a prioritised plan your own team can execute.
- A fixed-scope review, usually one to three weeks
- Findings ranked by business impact, not taste
- A plan your team can run without us
- Straight answers about build versus buy
- Follow-up support if you want it
What’s included
What we review
Code review
Structure, test coverage, and the specific places changes are most likely to break things.
Architecture
Whether the current shape supports the next two years, and what to change if not.
Performance
Where time and money go — queries, caching, jobs, and infrastructure spend.
Security and compliance
Dependency risk, access control, and data handling reviewed against real threats.
Backup and recovery
Whether your restore actually works, tested rather than assumed.
Database planning
Schema, indexing, and migration strategy for the volume you expect next.
Process
How the engagement runs
-
01
Scope
- Agree questions to answer
- Access and context
- Fixed timeline
-
02
Investigate
- Code and infrastructure review
- Team interviews
- Measurements, not opinions
-
03
Report
- Written findings
- Prioritised plan
- Walkthrough session
Stack
Tools we reach for
- Ruby on Rails
- PostgreSQL
- Redis
- Docker
- AWS
- Datadog
- Brakeman
- Bullet
Let's talk about what you are building
Tell us where you are — an idea, a half-built product, or a system that needs a steadier hand. We will reply with a practical next step.
