We take on
the hard parts
of building
software.

A small design and engineering studio in Zagreb. We build software where a mistake costs someone money or a customer, and take over products that have outgrown their first version.

Bring us in for a whole system, for one difficult part, or as engineers inside your team. The same people stay with you from the first call to long after launch.

Who relies on it?

Businesses that run their day on our software.

Autoklub Siget · Automotive service centre

A service centre that keeps taking bookings after the phones close.

13,000+ bookings a year go through the platform

Their bookings used to be taken by phone and coordinated by hand. We designed and built the calendar the call centre and service desk now share, and an AI assistant that books customers in after closing, under the same rules as the staff.

We built
Scheduling and capacity rules, customer and service history, SMS automation, analytics, the AI assistant
Stack
.NET, Angular, LLM integration
Read the case study

Restaurant · Croatia

A restaurant that takes orders online where the delivery platforms don't reach.

With no delivery platform in their area, the choice was their own app or none. We designed and built it, along with the kitchen board and pickup screen that follow each order to the counter.

Used by
Customers, kitchen staff and front-of-house
We built
The mobile app, the kitchen board, the pickup screen, checkout and payments, push notifications, Live Activities on iOS
Stack
Flutter, React, TypeScript, Supabase, Stripe, Cloudflare Workers
Read the case study
A phone stands on the deck of a small fishing boat, open on the Submania permit portal for 2026 sport fishing permits. In front of it lies a KŠRM Submania membership card marked as active.

Fishing and diving clubs · Croatia

A fishing club that stopped handling permits by email.

Hundreds of applications a year used to arrive by email, and every payment was checked by hand. We built the portal and the system behind it, and the club now only checks the documents.

.NET, Umbraco, Angular, SQL Server

Read the case study
On a desk in front of a frosted glass wall, a laptop shows the AssetLens asset list and an asset's history, a phone scans an asset's barcode during an inventory count, and a handheld barcode scanner stands beside them. Behind the glass, a blurred figure scans items on a shelf.

AssetLens · Asset tracking

A company that knows where every laptop is, and who has it.

Equipment was tracked in spreadsheets and counted by hand once a year. We built a system where every asset has a barcode, a holder and a history. It now runs as AssetLens, a product we keep developing.

.NET, Angular

Read the case study
A tablet on the reception counter of a car workshop shows the CRM dashboard with open work orders, unpaid invoices, open offers and low stock. A car key with a tag numbered 14 lies in front of it; behind, a mechanic works under a car on a lift.

Mechanic CRM · Workshop software

A car workshop that can issue an invoice from anywhere.

The workshop used an older program for the work and a separate tool for invoices. We built one web application for both, with invoices made from the work order and fiscalized.

React, TypeScript, Supabase

Read the case study

Residential buildings · Croatia

A building that's no longer run from a group chat.

Notices got lost in the group chat, and signatures for decisions were collected door to door. We built one app for the whole building: co-owners vote by their ownership share, payment slips make themselves, and every change is on record. The first building to use it has left its WhatsApp group behind, and we now offer it to others as our own product.

Used by
Co-owners, their representative and building managers
We built
Notices, repair requests, voting by ownership share, the reserve fund, barcoded payment slips, bank statement import, signatures, the activity log
Visit the product site, opens predstavnikstanara.com in a new tab

What happens after launch?

We keep it running, and keep building on it.

Most software changes more in its second year than in its first. We fix, extend and look after what we've built, so you never have to explain your system to someone new.

What can your team cover?

, , , and .

Most projects need several of these at once. Pick one to see where it shows up in our work.

Rules that can't be wrong: capacity, fees, tax and payments.

Usually built with.NET, SQL Server, Supabase, Cloudflare Workers

  • Scheduling with capacity per service, breaks and closed daysAutoklub Siget
  • Fees worked out from the permit type, membership and the federation's rulesFishing club
  • Invoices fiscalized under Croatian tax rulesMechanic CRM
  • SMS reminders, transactional email and PDF membership cardsSeveral projects

Do you build websites too?

We build custom websites with the same care as the rest of our work.

We plan the structure, design every page and build it on a CMS your team can edit without calling us. Every site below is live.

You'll know everyone on your project by name.

There's no account manager between you and the code. The people on the first call are the people who design and build your system, and the ones you talk to when something needs to change.

  • Portrait of Nino

    Nino

    Development

  • Portrait of Martin

    Martin

    Development

  • Portrait of Ivan

    Ivan

    Development

  • Portrait of Luka

    Luka

    Development

  • Portrait of Dorotea

    Dorotea

    Design

  • Portrait of Valentina

    Valentina

    Finance

How do we work together?

Bring us in for the whole system, or for the part you need.

  1. A complete project

    You bring the problem and the people who know it. We design, build and launch the system, and stay on after launch if you want us to.

  2. One part of a system

    A booking engine, a payment integration, a mobile app for an existing platform. We build that piece and fit it to what you already run.

  3. An existing product

    To extend it or take it over. We start by reading and running the code, fix what's fragile, then build what's next.

  4. An external engineering team

    Engineers who work in your repository, your tools and your planning, next to your own people, for as long as you need them.

Where do we start?

Tell us what you're building.

A few lines is enough to start. Your message goes straight to the team.

Rather write your own email?

Hi Threennovate,

we need help with

Nothing here is required except a way to reply. No newsletter, no sales sequence. How we handle your message.