About us
An Estonian software engineering company, registered since 2009
021 OÜ designs, builds and modernises business systems for clients across the EU and beyond. 16 years of operation, one contracting entity, and a written record of every commitment we make.
021 OÜ was entered into the Estonian e-Business Register on 05.10.2009 under registry code 11728851, and has traded continuously since. Our work is IT consulting and computer programming — EMTAK activity code 62021 — which in practice means custom software, cloud architecture, integration work and the engineering teams that carry it.
We are deliberately a company that writes things down. Clients come to us most often after an engagement elsewhere went wrong, and the pattern is almost always the same: nobody could point at a document that said what was being built. So each of our projects produces a specification, an architecture record and a handover pack — and those belong to the client whether the project continues with us or not.
Being registered in Estonia gives clients a practical advantage beyond the engineering. Contracting is with an EU entity holding VAT number EE101488194, so business customers registered for VAT elsewhere in the Union are invoiced under the reverse-charge mechanism, and the GDPR applies to every engagement by default rather than by addendum.
Registered company details
- Legal name
- 021 OÜ
- Legal form
- Osaühing (private limited company)
- Registry code
- 11728851
- EU VAT number
- EE101488194
- Registered
- 05.10.2009
- Activity code
- EMTAK 62021 · NACE 62.02
- Registered office
- Kaupmehe tn 7-115, 10144 Tallinn, Kesklinna linnaosa, Harju maakond, Estonia
- admin@zero21ou.com
- Phone
- +372 5123-4567
- Time zone
- Europe/Tallinn (EET / EEST)
- Working languages
- English, Estonian
Commitments
What working with us actually means
Written scope, then code
No engagement starts on a verbal brief. The specification, the data model and the acceptance criteria exist as documents you keep.
One team, named
You know which engineers are on your project and you meet them before they start. Nobody is swapped out without telling you.
No lock-in
Source code, infrastructure definitions and credentials are yours. We document what it would take to replace us, and we hand over cleanly if you ever want to.
Honest scope
If a project does not need the architecture it is asking for, we say so in the discovery report — including when that makes the engagement smaller.
Delivery
The same four phases, every time
Phase 01
Technical discovery
A paid or complimentary discovery session, depending on scope. We document the current systems, the constraints and the success criteria in writing before quoting anything.
Phase 02
Architecture & scope
Target architecture, data model, integration contracts and a phase plan. You receive the document whether or not you continue with us.
Phase 03
Implementation
Two-week iterations against the agreed backlog, with a demonstrable increment and a written progress report at the end of each one.
Phase 04
Hardening & handover
Load and security testing, runbook, backup verification, knowledge transfer, and transfer of repositories and infrastructure accounts to the client.