Services / New applications

A new application, built the way it should have been from the start.

A sales platform, a customer portal, a process tool, a compliant multi-tenant product. You have the business need and no system for it yet. We take it from idea to production in 2-3 week iterations, with a specification you review before code is written, and that stays the source of truth afterwards.

Describe your idea Prefer to talk? Book a 30-minute meeting

Two or three sentences are enough. Written reply within 2 business days, no obligation.

8 of 13 reference projects built from scratchEU-based teamIT-liability insuredNDA on request

Why new projects go wrong

The risk is rarely the technology. It is coding before anyone wrote down what the system should do.

The scope is a conversation, not a documentEveryone remembers the kick-off differently. Six months later the software matches the tickets and not the business.Discovery gives us a shared, written basis before any code. The specification then grows with your experts at the depth the system needs; for a larger system that means weeks of workshops, and we say so up front.
Nobody owns the specification once coding startsDecisions live in chat threads and tickets. The system drifts from what was agreed and nobody can say what it does today.The specification is under version control alongside the code and updated with every iteration. What the system does is always one document away.
One big release, lateMonths of work, then a launch nobody can roll back.A demo and a release every 2-3 weeks. You steer scope iteration by iteration; every release is measured against the spec, tested and reversible.

How it works

Discovery, specification, iterations, run.

Code got cheap; we generate most of it, AI-assisted, against the specification. The effort, and the senior people, go into knowing what to build and proving that it was built.

Step 1

Discovery

2-4 weeks. A strong basis to start from: domain understanding, system outline, main risks, first backlog, and a realistic plan for specification and delivery. Not a finished spec; a plan for one that fits your system.

Step 2

Specification

Built with your experts at the depth the system needs: data model, business rules, screens, integrations, edge cases, in business language. Weeks for a tool, months for a platform. Reviewed and versioned from the first draft.

Step 3

Build in iterations

2-3 week sprints against the specification. Each delivers working software and the updated spec; each release is demoed, tested and reversible. You prioritize; the spec accumulates.

Step 4

Run, or hand over

The system is fully owned by your team, documentation included. Or we keep running and evolving it under an SLA. See application maintenance.

Why we say iterated development, not agile: agile was built for a world where code was expensive and had to be rationed into small bets. Now code is cheap; what needs iterating is understanding. Specify, build, verify, adjust, every 2-3 weeks.

The specification

Precise enough to build from. Plain enough to review.

It is not a 200-page document written before line one. It is a living set of business rules, data definitions, screen descriptions and integration contracts, kept under version control in its own repository alongside the code. Your experts review it in business language. Our engineers and our AI tooling build from it. Every release names the spec version it implements.

What you get out of it, whatever happens later: system documentation that is never out of date, audit evidence, and the ability to change vendor without losing what the system knows.

Specification excerpt for reviewspec/orders.md @ v0.7

Rule 4.2Orders above 10,000 EUR require a second approver of level 2 or higher. Confirm threshold with finance.

Rule 4.3Customers outside Hungary without a VAT ID are routed to manual review.

Rule 5.1Customer discounts are capped at 15 percent regardless of tier.

Open question 5.2Should a discount cap apply to framework contracts? Decision owner: sales director.

Illustrative. Rules, questions and decisions are tracked under version control alongside the code.

Commercial model

Scoped first steps. Then the model that fits your governance.

Discovery

2-4 weeks with defined outputs. Duration and cost are agreed before it starts, and you keep everything it produces.

Specification and build

Fixed-price phases, sprint budgets or time-based, agreed up front. Whichever your procurement and your risk appetite prefer; the spec makes any of them measurable.

Run

Monthly fee per application under an SLA, if you want us to keep running it. Optional, and you can leave with the full repository at any time.

New builds

Systems we built from the ground up.

All 13 reference projects →

Have an idea for a system that does not exist yet?

Describe it in two or three sentences. You get a written reply within 2 business days: how we would approach it, what Discovery would cover, and a rough effort range.

Prefer to talk? Book a 30-minute meeting

Describe your idea