Ceero is the engineering practice of Nicklas Dupont, run out of Copenhagen. Eight years of production software — enterprise consultancies, scale-ups, and our own products — sits behind the judgement here. Today that judgement directs a fleet of specialised AI agents, and nothing they write reaches your repository before a senior engineer has read it.
- Legal entity
- Ceero ApS · CVR DK45441393
- Trading as
- Ceero · ceero.eu
- Based in
- København, DK · remote across the EU
- Engagement model
- Fixed scope, fixed price
The fleet does the typing. A senior engineer stays accountable.
There is no mystery about who does what here. Scope, architecture, review and sign-off stay with the engineer whose name is on the contract. Everything mechanical is dispatched to the agent best suited to it — and comes back through review before it counts as done.
- 01Senior engineer
Scope & architecture
We read the existing code, agree what 'done' looks like, and settle the shape of the solution before a single agent is dispatched.
- 02Agent fleet
Discovery
A low-cost agent sweeps the repository for every caller, convention and edge case, so the expensive thinking goes on decisions instead of searching.
- 03Agent fleet
Build, test, document
Specialised agents work in parallel from that one spec, each on the cheapest model tier that can do its part correctly.
- 04Senior engineer
Review & sign-off
Every diff is read by the engineer who scoped it. Anything that doesn't hold up goes straight back to the fleet — that loop is the whole point.
Eight years of watching good engineering get billed by the hour.
Before Ceero, the work happened inside consultancies and product teams — enterprise CMS platforms, SaaS frontends, mobile apps, and eventually running the frontend team of a Copenhagen consultancy. The engineering was usually fine. The delivery model was the problem.
Clients bought headcount and hoped it converted into progress. Estimates stayed vague because nobody wanted to be held to one. The people who could actually make a call were in three meetings and a status report. Everyone was busy, and the thing still shipped late.
Ceero is the correction. One senior engineer holds the scope and the sign-off, a fleet of specialised agents carries the volume, and the price is agreed before anything starts. You buy a result, not an availability calendar.
Six rules. No exceptions.
The six rules the practice runs on. They sit in the contract, not on a poster.
- R01
Direct communication.
You email us. We email you. No account managers, no project portals, no waiting for a status meeting.
- R02
Estimates under 10 hours.
Anything bigger is a research task with its own estimate. No 'about a month' line items.
- R03
Acceptance criteria, always.
If we can't agree on what 'done' looks like before we start, we're not starting.
- R04
Plain text by default.
Daily updates in writing. Calls only when the writing isn't enough.
- R05
Boring tech first.
Excitement is a smell. Boring choices ship, and they survive the handover.
- R06
No lock-in.
Runbooks, ADRs, and a clean handover. The goal is for you to not need us.
Bring a project, a quote you don't trust, or a system you're stuck on.
First call is 30 minutes, free, and with the engineer who'd actually do the work.