Services

Software Development Services, measured in objects, not adjectives.

Five crafts, one small senior team: 50+ shipped projects across 10 countries since 2020. Below, the object each craft put into the world, where it landed, and the number it moved.

The manifest

Five crafts. Here is what each one has put into the world: the object, where it landed, and the number it moved. Every craft links to its full story. We only take on builds scoped to pay for themselves, and we would rather say so here than at the end.

01 / 05 Our own product

Custom Software Development

An invoice arrives at a company that runs Arhivix. By the time anyone opens the folder, it has a type, a supplier, a tag, and a legal retention date. Nobody filed it. It filed itself.

That is Arhivix, the document platform we build and run ourselves. Not a client deliverable: our own product, in production at 500+ companies, classifying 92% of everything uploaded without a human touch. When we sell custom software development, this is the standard we mean, because we hold our own product to it every day.

One object on this page is ours. Arhivix is the product we build, run, and answer for. The other four were commissioned, paid for, and shipped to the clients who own them. We will always tell you which is which.

Chapter 01 · our own product

Chapters 02 to 05 · client work

02 / 05 Client work

Web Development

A customer pays for a training program on pakzprogram.com. Checkout clears, the course portal opens, the first lesson starts to play. Nobody at Pakz Studio had to touch a thing.

We designed and built that storefront for Pakz Studio from scratch: configurator, secure checkout, course portal, no template underneath. It went from nothing to live in two months. Since launch, orders are up 32%, engagement up 38%, time on site up 27%. The deliverable was never the website. It was the order that arrives on its own.

From a browser tab to a physical board above a court.

03 / 05 Client work

Mobile App Development

Courtside, an operator taps two points into a phone. Above the court, the LED board changes. There is no lag a human can notice.

BELGRAND builds LED display systems. We built the iOS and Android apps that control them: native clients syncing in real time with the existing desktop software, match logging automated, plus a few extras nobody asked for that the client now depends on. That is our definition of mobile development. Not an app in a store: a score on a board.

Also from this bench: MaxPlayer, built for E Galactic, taken from seed to 1M+ users worldwide.

Some objects light up a board. Some go out on company letterhead.

04 / 05 Client work

AI Development

The customer who asked for a price this morning has a number before the day ends. Last year, the same question took three days, and the answer leaned on last year's scrap rate.

At FENIX TEAM PLAST, a windows and doors manufacturer, we automated the path from site measurement to CAD to fabrication. Quoting dropped from about three days to the same day at above 99% accuracy, fabrication defects fell 35%, and the build paid for itself in under four months. That is what AI development means here: a number your sales team can send, not a demo a vendor can show.

Same craft, different desk: Srećna Trojka's bid preparation went from 18 hours to 6, and their win rate climbed 14 points.

None of these objects work if the person holding them cannot read them.

05 / 05 Client work

UX/UI Design

A cyclist on EuroVelo 11 opens the app to find the next protected nature area on the route. No manual, no onboarding, nobody to ask. The screen explains itself or it fails.

EcoBikeNet is an EU co-financed app we designed and built for the Provincial Secretariat for Urban Planning: more than 15 protected natural areas mapped along EuroVelo 11, across an engagement that ran more than two years. Design is the craft hiding inside every other chapter on this page. The Pakz numbers above are design numbers too: engagement does not rise 38% because the code compiled.

The method

Every phase ends in an object too.

We do not send status reports and call them progress. Each phase of an engagement ends in something you can open, click, or reject.

  1. Discovery a fixed-price proposal with scope and milestones
  2. Design a clickable prototype, in about 48 hours for MVPs
  3. Development a working build you can click through, every week
  4. Delivery the object itself, in production, with docs your team can run

A focused MVP takes about 6 weeks.

Start a conversation

What is the object you need in the world?

Free 30-minute call. Describe the thing that should exist, and we will tell you what the first shippable version looks like, what it costs, and how long it takes. If it is not worth building, we will say that too.

We take on builds scoped to pay for themselves. The same filter the manifest gave you up front.

Book a Free Consultation