01
Product engineering
The application itself — web, mobile, desktop and the services behind them.
Novi Sad, Serbia · Est. 2021
We help your
company thrivee
Thrivee is a small senior engineering team that builds software alongside the people who own it — web, mobile, desktop, data and AI. You keep the product and the direction. We take the work you have run out of hours for.
Taking new engagements
delivery graph running
- Founded
- 2021
- Based in
- Novi Sad, RS
- Overlap
- CET · UK · US East
- Practices
- Product · Data & AI · Platform
- TypeScript
- React
- Next.js
- Astro
- Vue
- Node
- Swift
- Kotlin
- React Native
- Flutter
- Electron
- Tauri
- Qt
- .NET
- Go
- Rust
- Python
- PyTorch
- dbt
- Airflow
- Kafka
- Spark
- Postgres
- pgvector
- Snowflake
- BigQuery
- MLflow
- Docker
- Kubernetes
- Terraform
- AWS
- GCP
- GitHub Actions
- Playwright
- Grafana
- OpenTelemetry
What we do
A full software team, with a specialism.
Three practices. Product engineering is the bulk of it — the web, mobile and desktop software itself. Data and AI is where we go deepest. Platform is what keeps both shipping.
02
Data & AI
Pipelines, models and LLM features that survive contact with production.
03
Platform & reliability
Infrastructure, delivery and testing — so shipping stops being an event.
Where we come in
The date does not move.
So the capacity has to.
The pattern is always the same. Scope was set when the team had room. Then hiring slipped, or the architecture needed one more rewrite, or two people went on leave in the same fortnight. The launch date stays where it is, and the backlog quietly stops moving.
Adding a generalist agency at that point usually makes it worse — the onboarding cost lands exactly when nobody can afford it. So we do the opposite: senior engineers who already know this stack, in your repository, contributing inside the first week.
How we work
Four commitments we would rather be held to than described by.
Senior only, on the actual work
The people on the call are the people in the pull requests. No pyramid, no handover to a junior bench after the contract is signed.
We embed, we don’t colonise
Your repository, your standards, your review process. We adapt to how your team already works instead of importing a methodology.
Write it down
Decisions, trade-offs and runbooks land in your docs as we go. When the engagement ends, the knowledge stays behind.
Make ourselves unnecessary
A good engagement ends with your team faster than before. We would rather be re-hired for the next hard thing than quietly become load-bearing.
- 01
Call
Thirty minutes on what has to ship, what is in the way, and when the date is. No deck, no discovery theatre.
- 02
Written plan
A short document: the slice we would take, how we would sequence it, what it costs, what we would need from you.
- 03
In your repo
We work where your team works — same branch strategy, same review bar, daily written updates.
- 04
Hand back
Documentation, a walkthrough, and a team that can carry it without us. That is the deliverable.
Engagement models
Pick the shape that fits the problem.
Every one of these has a defined end. None of them quietly turn into a retainer you forgot to cancel.
01 2–6 weeks, fixed scope
Sprint rescue
A date you cannot move and a backlog that says otherwise.
02 Monthly, part or full time
Embedded engineers
Sustained capacity without a six-month hiring cycle.
03 Project, milestone-based
Build & hand-off
A system you need built once and then want to own.
04 1–2 weeks
Technical due diligence
Investing in, acquiring, or inheriting a codebase.
Who you are working with
A small team, on purpose.
Thrivee was founded in 2021 in Novi Sad, and has stayed deliberately small. Fewer people means the engineer who scoped your work is the engineer who writes it, and nothing gets lost in a handover between a sales team and a delivery team.
It also means we turn work down. If a project needs a capability we do not have, saying so early costs you a week — finding out in month three costs you the quarter.
Wealth is having time.
What kind of software do you build?
All of it — web applications, mobile apps for iOS and Android, desktop software, backends and APIs, data platforms, and machine-learning and LLM systems. Data and AI is where we are most specialised, but it is a practice inside a general software engineering company, not the whole of what we do.
How quickly can you start?
Usually within one to two weeks of a signed scope, sometimes sooner for a short rescue. If we cannot staff you with the right people in a timeframe that helps, we will tell you that instead of taking the work.
How do you charge?
Sprint rescues and due diligence are fixed fee against a written scope. Embedded engineers are a monthly rate per engineer, billed in advance, with one month notice on either side. No hidden onboarding fees, no minimum term beyond the first month.
What timezone do you work in?
We are in Novi Sad, Serbia — CET / CEST. That is a full working-day overlap with the UK and Europe, and a solid morning-to-early-afternoon overlap with US East Coast teams. We keep meetings inside your working hours, not ours.
Next step
Tell us what has to ship, and by when.
One call, no deck. If we are not the right team for it we will say so, and usually point you at who is.
Start a conversation branislav@thrivee.io
Typical reply within one business day · CET / CEST (UTC+1 / UTC+2)