These are not aspirations. They're operating rules. If we can't honour them on a particular engagement, we say so before signing.
Our service pages name the price ranges for every offer. No bespoke quotes hidden until page 40 of a proposal. When we send you a fixed-fee proposal, the numbers will sit inside the published ranges or we'll tell you upfront why this engagement is an exception.
Every engagement has one technical lead. They sign the proposal. They run the discovery. They show up on site. They stay on the project from kickoff to handover. We don't sell you to one team and subcontract delivery to another.
Article 11 of Law 98/2016 forbids splitting contracts to dodge procurement thresholds. We won't propose it. If your scope is larger than one threshold, we run the right SEAP procedure for the right size. It takes a few weeks longer. It stays clean.
Open formats, exportable schemas, no vendor lock-in clauses. If you ever decide to migrate away from us, we hand you everything that's yours. Code, data, infrastructure-as-code, runbooks. The kind of handover we'd want if we were on your side of the table.
Public-sector data layers run on Romanian infrastructure (Romarg, ClausWeb). Where compute can sit elsewhere without exposing data, we use efficient EU providers (Hetzner) and tell you exactly where each component lives. No mystery, no offshore surprises.
Each service page has a "what we don't do" section. It's not false modesty. It's the fastest way to make sure both sides know what they're buying. If your problem is outside our scope, we tell you on the first call and, where we can, point you to someone better suited.
Every engagement ships with written documentation: architecture, runbooks, decision log, handover notes. Not because it's nice to have, but because the next person to touch this system needs to understand it without us in the room.
Then a conversation is probably worth thirty minutes. Tell us what you're working on.
Start a conversation