Thorn Industries
001 · How we work

The principles
every engagement runs on.

We start with an assessment: one to three weeks, fixed fee. It produces a plan. Implementation is optional, and it's a separate contract. The rules below hold throughout. They're not aspirations. If we can't honour them on a project, we say so before signing.

01
Pricing

Plain pricing, published ranges

Our service pages name the price ranges for every service. No "bespoke" quotes buried on page 40. When we send you a fixed-fee proposal, the numbers sit inside the published ranges. If they don't, we tell you upfront why.

02
Accountability

Named accountability, end to end

Every project has one technical lead. They sign the proposal. They run the assessment. They show up on site. They stay on the project from the start through to handover. We don't sell you one team and then put another one on the work.

03
Contracts

No contract splitting

Article 11 of Law 98/2016 forbids splitting contracts to dodge procurement thresholds. We won't propose it. If your project crosses a threshold, we run the SEAP procedure that matches its size. It takes a few weeks longer. It stays clean.

04
Ownership

Open standards, your data stays yours

Open formats, exportable schemas, no clauses that tie you to one supplier. If you ever want to move everything elsewhere, 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.

05
Where data lives

Your data stays in Romania. That's the rule.

Public-sector data layers run on Romanian infrastructure (Romarg, ClausWeb). Where compute can sit elsewhere without exposing data, we use EU providers (Hetzner) and tell you exactly where each component lives. No mystery, no offshore surprises.

06
Honesty

We say what we won't do

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's being sold. If your problem isn't the kind of work we do, we tell you on the first call and, where we can, point you to someone better suited.

07
Documentation

Documentation as deliverable

Every project ships with written documentation: architecture, runbooks, decision log, handover notes. Not because it looks good, but because the next person to work on the system needs to understand it without us in the room.

002

These principles
sound like a fit?

Then a conversation is probably worth thirty minutes. Tell us what you're working on.

Start a conversation