Highbury
Build
Websites and applications that outlive their launch.
- Marketing sites and landing pages
- Web applications
- iOS and Android
AWS architecture, AI systems and software delivery for companies in Germany. You work directly with the engineer who writes the code.
East Stand, Highbury · 1936
Certification
11 years
Prior consulting work across automotive, energy and telecommunications, including identity and access architecture spanning more than 3,000 AWS accounts.
You scope the work with someone senior. The build goes to whoever is free. A year later the person who understood the system has moved on, the documentation is thin, and the next change costs more than the original build did.
That gap is structural in an agency — it is how the model pays for itself. It cannot open here. The engineer who scopes your project stays on it, and is still the one answering when the change is needed.
Named rather than listed, because the range is deliberate. A project that spans two of them is still one engagement, with one person accountable for it.
Highbury
Websites and applications that outlive their launch.
Highbury
Shops that survive their second year.
Highbury
AWS architecture that holds under load.
Highbury
AI that ships, not AI that demos.
Highbury
The manual steps between your systems, removed.
Most projects cross two or three of these. Describe the problem and you will get an honest read on whether it is worth doing.
Two products taken end to end and still running — the same hands you would be hiring.
Founder
An AI toolkit for job applications: automated applying, a desktop client, and the pipeline behind both. Built, shipped and operated solo.
careerwerk.comCo-founder · Tech lead
NexHub, a platform for global mobility, tax and compliance. Next.js and Payload at the front, FastAPI and a hybrid vector–graph retrieval layer behind it, all on AWS.
nexiam.netThree steps, and the same person at every one of them.
A call, then a written scope: what gets built, what it costs, and what it explicitly does not include. Before anything starts.
Work happens in your repository, with something running to look at every week. No status theatre, no demo built for the meeting.
Infrastructure as code in your own accounts, documentation written as it goes. You can take the whole thing elsewhere at any point — that is the test of a real handover.
Thirty minutes, no obligation. Bring the problem rather than a specification — working out what actually needs building is part of the job.
Rather write first? The form reaches the same place.