Technical BA outsourcing · Bucharest · UK, EU and US delivery teams

Senior technical business analysts, embedded in your delivery teams.

We place senior Technical Business Analysts and Technical Product Owners into enterprise delivery squads. They write the specification your engineers build from, and the standard we hold to is whether it comes back with a question. English and Romanian.

Book a scoping call How we place technical BAs

Where this work has been done

Technical BA engagements inside these institutions, most of them delivered as a subcontract under a prime: NTT DATA, Qualitance/ALTEN, Investigo/Definia and E-Resourcing UK. NTT DATA appears in the strip as a prime we delivered through, not as a client. We name the primes because vendor management asks first, and because it means the work was done inside enterprises on somebody else's contract.

The dated record

What actually slips the date

Release dates move for reasons that get written down afterwards as "requirements". An acceptance criterion that two people read differently is a defect that has not happened yet, and it surfaces in UAT six weeks after somebody sized it, when the fix costs a sprint, a re-test, and a conversation with audit about why the change was made at all.

We work at the point where somebody has to write down what the system does when the customer already exists, when the third-party call times out, and when the amount comes back negative. Getting that into a form an engineer can build from without a follow-up call is what we sell, and most of it is done by a technical BA embedded in somebody else's delivery team. That is line one, it pays for everything here, and the builds, the pipeline and the academy exist because of it.

Who does the analysis, and who writes the code

Four things we sell. They differ in exactly one place: who writes the code once the analysis is agreed.

Live · the main business

Embedded Technical BAs

Analysis: We do the analysis.
Code: Your engineers write the code.

A senior Technical Business Analyst, Technical Product Owner or delivery-focused Scrum Master joins your squad and works in your tools, your ceremonies and your definition of done. What your engineers get is a specification with acceptance criteria, edge cases, and the integration contracts already argued out. This is most of what we do, and every engagement in the strip above is this.

How we place technical BAs

Live · the pre-Etheria model

Custom software builds

Analysis: We do the analysis.
Code: Our engineers write the code.

We still quote and deliver full custom builds with our own engineers, and we are openly folding the line into Etheria. The page says when a classic build is still the right call and when it isn't.

When a classic build fits

Beta · GA Autumn 2026

Etheria

Analysis: We do the analysis.
Code: An agent writes the code. A named human approves it before it moves.

Our own delivery pipeline, in Beta, with no public client references yet. The product itself lives at etheria.ro.

Who operates Etheria

First cohort Winter 2026/27

Technical BA Academy

Analysis: You learn to do the analysis.
Code: Your team writes the code, as they already do.

Eight instructor-led sessions taught by a practising technical BA, not by a training company. Dates and price are not published yet, and the list sees them first.

Join the list

Who shows up

Theodor Istratescu founded Theta One Digiplex S.R.L. and has been doing the analysis since 2022. He spent over two years as Lead BA and Proxy Product Owner at Raiffeisen Bank Romania, held proxy product ownership on the UNFCCC's Article 6 carbon-accounting portal through NTT DATA, and ran the technical interviews that bank used to hire its own Technical BAs.

Today that is one person. If your programme needs three analysts next quarter, say so on the first call and you get a straight answer about whether we can staff it, rather than a yes that turns into a CV from a recruiter.

Full CV, with dates About the firm

How an engagement starts

Step 1

A 30-minute scoping call

You describe the squad and what keeps coming back. We ask who signs off requirements today, what your definition of done actually says, and where the last release slipped.

Step 2

A named person and a rate

One profile: who they are, what they have delivered, the day rate, and what they would own in your first sprint.

Step 3

A trial period you can end

They work in your tools, your ceremonies and your definition of done. If it is not landing you say so, it ends on the agreed notice, and you keep the specs and the refined backlog.

Whether or not you hire anyone, you leave that first call with a written note on where your requirements process is leaking: which sign-offs are informal, which handovers arrive with no acceptance criteria, and which of your revision cycles look avoidable.

Start with one squad, one quarter.

The smallest thing we do is put one technical BA into one squad for a quarter, under your existing prime contract if you have one, because we have already delivered inside enterprises that way. If it is not working you give the agreed notice, and you keep the specs, the refined backlog and the delivery record.

Book a scoping call Send a brief instead