AvailableFrom Q1 2027
Startups hire me to turn an idea into a product that's live, tested and easy to keep changing. Enterprise teams hire me for the cloud migration, the pipeline or the tech lead they can't staff in time. Either way, you work with the person writing the code.
// startup.tsimport { engineer } from "@cerberus/core";export default engineer({ role: "principal engineer", client: "startup", starts_with: "discovery-sprint", ships: "first-version", cloud: "your-accounts", ci_cd: "from-day-one", handoffs: 0,});// scaleup.tsimport { engineer } from "@cerberus/core";export default engineer({ role: "principal engineer", client: "startup", role: "tech-lead", owns: ["architecture", "pipeline"], cloud: "as-code", hands_to: "your-hires", handoffs: 0,});// enterprise.tsimport { engineer } from "@cerberus/core";export default engineer({ role: "principal engineer", client: "enterprise", role: "senior-engineer", scope: ["migration", "ci-cd"], works_in: "your-policies", measured_in: "time-to-release", handoffs: 0,});What I do
Build
The web and mobile product your customers use, including AI features that work with your own data.
Assistants and automation that answer from your own data, tested and maintained like the rest of the product.
The whole product, from screen to database, built by one person, so changes ship without hand-offs.
iOS and Android apps that stay in step with the web product, without a separate team.
Run & lead
Where the product runs, how changes reach users, and the technical leadership to keep a growing team shipping.
The simplest structure that does the job today and can grow later. Not microservices for their own sake.
Runs on the cloud you already use, written down as code so it can be rebuilt, audited and handed over.
Every change is tested and released the same way, so shipping is routine.
Technical direction, code standards and mentoring, and help hiring your first engineers.
Which sounds like you
For startups
I start with a short, fixed-price discovery sprint that ends in a written scope, plan and estimate — yours to keep whether or not you continue with me. If the first version is funded, I build it, set up the hosting and automated releases behind it, and take it live, ready for later hires to take over.
Start with a discovery sprint →I look at the product and anything that already exists, and write the trade-offs down.
The simplest architecture that does the job today and can grow with you.
The whole product, end to end, on accounts you own, with automated testing and releases from day one. A working demo every week.
Documentation and monitoring in place. Continue on a light retainer, or hand to your own team.
For startups
The product works, the team is growing, and nobody owns the architecture, the pipeline or the cloud bill. I take the lead: set the technical direction, make releases and infrastructure dependable, and help you hire and grow the engineers who take it from here.
Discuss technical leadership →Architecture, code, cloud and how the team ships today.
A technical roadmap the team can follow, with priorities agreed with you.
Release process, infrastructure and standards in place, while reviewing and mentoring the team.
Help hire the senior engineer or CTO who takes over the role.
For enterprise
A cloud migration, a CI/CD overhaul, a service nobody owns, a delivery process that has slowed to a crawl. I work inside your team, your tools and your security policies, own the outcome, and leave it documented for your people.
Discuss an engagement →Systems, pipelines and how work moves to production, including talking to the people doing it.
Written findings and a plan, in order of impact, aligned with your architecture and compliance.
Migrate, automate and fix alongside your engineers, inside your rhythm.
Documented and maintainable. Ownership returns to your team.
Client names stay confidential. Sector, scope and team context are described in full.
A few sentences on the product, where it stands and how your team is set up is enough. You'll get a direct reply within two working days — from me, not a sales inbox.
e.g. A B2B marketplace for industrial spare parts. We have designs and two pilot customers.
e.g. Seed-funded, four developers, deploys are manual and nobody owns the architecture.
e.g. We are moving three services to Azure next quarter and releases still take two days.