Software Development

Start at the rootTo build whatMatters most

Ask about our services, projects, or how we work. Answers come from what is published on this site. For anything else, write to hello@rootid.dev.

AI answers from this site, usually in seconds. They can be wrong, and we save conversations.

Rather talk to a person? Book a call

Trusted by

Services

What we do

We build new products and the systems a business runs on, improve the software you already have, add engineers to your team, and help it put AI to work.

Process

How we work

Four weeks of foundation and design, then features in cycles from week 5, each cycle ending in a release. Launch is one of those releases, and the cycle carries on after it.

Before week 1

Call and proposal

It starts with one call. You tell us what you need and how the work runs today, we ask the questions that decide the build, and we both find out whether we are the right fit.

Then you get a written proposal: scope, timeline and price, in plain language. You know what you are saying yes to before any work begins.

Next Foundation and design
Weeks 1 to 4

Foundation and design

The first four weeks go into understanding and design. We learn how your work runs, who does what and where it gets stuck, and we design the screens with you until they fit it.

Meanwhile the foundation goes in. Sign-in, permissions, audit trail, notifications, documents and files are already built, tested and running in production, so on your project they are set up, not written from zero. By the end of week 4 the design is agreed and the ground is ready.

Next Features, in cycles
From week 5 on

Features, in cycles

From week 5 we build your features in cycles. Features that do not depend on each other are built side by side, and every cycle ends in a release you can open and click, not a slide or a status report.

Your feedback goes into the next cycle, together with the next features. The cycle does not stop at launch: from week 5 on we keep adding, and the system keeps growing with your work.

Next Launch and after
From launch on

Launch and after

Launch is the release that puts the system in front of all your users. It goes live documented, and the cycle carries on as before: new features, released and refined from what your users tell you.

We stay on it: fixes, updates, the years after. Software we shipped in 2020 is still running today.

Next Call and proposal

Work

Our work

Products we designed and built for museums, sports clubs, public institutions, international development, e-commerce, fitness and outsourcing.

All projects

Values

What we stand for

Six things that decide how we work, on every project.

Built to last Quality We build software to last, not only to launch. We write software that someone else can read, test and extend years from now. Every project gets the same foundations, tests, reviews, monitoring and documentation, whether it is a pilot or a platform.
No invented results Honesty We say what will work and what will not. If an idea will not work, or will cost more than it returns, we tell you before you pay for it. Estimates come with their assumptions, and when something slips, you hear it from us first.
Process first Understanding We learn how your work runs before we write code. Software fits a business only when the people building it understand the business. We start with your processes, your people and the questions they need answered, and design from there.
Simple first Pragmatism We choose the simplest thing that does the job well. We use what already exists before we build something new, and we build only what your product needs. Your budget goes into what makes it yours, not into the plumbing.
After launch too Ownership We treat your product as our own, long after go‑live. A launch is a release, not an ending. We stay with the product: we watch it in production, fix what breaks and keep it moving with your business.
AI in daily work Innovation We try what is new, and keep what earns its place. We use AI every day in how we design, write and test software, so you get more done in less time. A new tool or technique goes into your product once it has proved itself in our own work, not because it is new.

Testimonials

What our clients say

The people we build for, in their own words.

  • Awaiting Jasmin’s own words
    Jasmin Bešić General Director Institute for Youth Development KULT
  • Awaiting Emir’s own words
    Emir Kurtić Vice Governor Centralna banka BiH
  • Awaiting Damir’s own words
    Damir Draško Founder & CEO Oratio

Blog

From the blog

How we build software, and what we see at the events we go to.

All articles

FAQ

Questions before you begin

Something else? Write to us

  • How do you price a project?

    Two ways. Hourly when the scope will move, fixed price when it will not.

    Either way the estimate comes broken down per area of work, as a range rather than one number, with the contingency stated as a figure you can see instead of buried in the line items. If part of the scope is not worth building, we tell you before you pay for it.

  • How long will it take?

    That depends on scope, and anyone who answers it in a sentence is guessing. The shape is the same on every project: foundation and design first, then features in cycles, each ending in a release you can open.

    What we can commit to is how the estimate is made. You get an optimistic figure and a realistic one, the buffer declared as a number rather than hidden, and the assumptions that would move either. You know what the date depends on, not just what it is.

  • What if we do not know exactly what we need yet?

    That is the normal case, and it is the part we are best at.

    We start by mapping how the work happens today, where it breaks, and what is actually worth automating. You get that written down and estimated before anything is built. Most clients arrive with a symptom rather than a specification. Finding the real problem is the job, not a preliminary to it.

  • How do you work with clients day to day?

    You work with the people building the system, not an account manager relaying messages. We are in Sarajevo on Central European Time, which covers the European working day and the American morning, and we work in English and Bosnian.

    Expect a steady cadence, decisions written down rather than left in a call, and people who are invested in the outcome. We take on work we intend to still care about a year later.

  • Do we own the code?

    Yes. You own the code, the data and the infrastructure it runs on.

    Repositories, deployments and documentation are handed over as a matter of course. We are happy to host and maintain it, and equally happy to hand it to whoever you choose. Nothing is locked to us, and nothing about the arrangement depends on you staying.

  • Which technologies do you build with?

    Angular, .NET and Azure are where we are deep: mature, stable, long supported platforms, chosen because the systems we build have to keep running and keep changing for years. The foundation is not the part that should ever need replacing.

    Mobile apps are built in Flutter, with native code where a phone demands it.

  •

Start a project

Tell us what you want to build.

Book a 15-minute call. Tell us the idea, and we tell you how we would build it and what it would take.

Book a call or write to hello@rootid.dev
Your call is with a founder, Adi Šoše or Adnan Čutura.