Websites Marketing sites and portfolios your team can run.
Ours: Ginshelf
From the first sketch to production.
Websites, stores, web and mobile apps, complex platforms. You approve the product on a clickable prototype – before the first line of code is written.
Not a deck of mockups – a clickable prototype on your real data. You click through it like the finished product and approve it. Only then do we write code.
What we build
Any product, one team.
Online stores Catalogue, checkout, payments and stock.
Web apps and SaaS Customer portals and subscription products.
Ours: Koru.Farm
Mobile apps iOS and Android, including apps that work offline.
Ours: Koru, Pixel Chain
Complex platforms and ERP Many roles, integrations, migration from a legacy system.
Ours: Pixel Chain
UI/UX design on its own Research, prototype and design system, for teams with their own developers.
How it goes
What you get at every step.
- We start
- with a fixed-price discovery
- You get
- a live product, code in your repositories
- 1
Discovery
Goals, users, constraints. You get: a scope, a plan and a fixed price for the build.
- 2
Design
A clickable prototype on your data. You get: a product you can click through, and you approve it before any code.
- 3
Build
A demo every week, a test environment you can open any time, automated tests on every change.
- 4
Launch
Deployment and monitoring, documentation, team training.
- 5
Support
For the first 30 days after launch, bug fixes are free. After that: fixes, updates, new features – or a clean handover to your team.
Built to hand over
- A senior engineer decidesAI drafts code and tests; every decision that changes the product is a person's. An ordinary week: 248 changes, 9 releases of Koru.
- Your code, your accountsFrom day one, with the rights to the code and design written into the contract.
- No lock-inMainstream technology, so any capable team can pick the product up.
- Support or a clean handoverFree bug fixes for 30 days after launch, then the choice is yours.
Questions
Before you call.
How much does it cost?
Discovery is a short fixed-price project. It ends with a scope and a fixed price for the build, so you know the number before you decide.
How long will it take?
It depends on the complexity: a website and a platform with a dozen roles are very different projects. So we don't guess on the first call – you get the timeline after discovery, together with the scope and the price.
Who owns the code?
You do. Everything lives in your repositories and accounts from day one.
What happens after launch?
For the first 30 days we fix bugs for free. After that, support with us – or a handover to your team with documentation and tests.
What if you disappear? Can another team take over?
Yes. Mainstream technology, plus documentation and tests from day one – the product can go to any capable team.
What if we change our minds halfway?
That's normal – a product gets clearer as it grows. Each change is handled on its own: we tell you up front how it moves the timeline and the price, and do it only once you agree.
How do you choose the technology?
To fit the job and whoever will maintain the product next. We prefer mainstream, proven tools – they make hiring and handover easier.
How is this different from "vibe coding"?
Vibe coding is AI writing code that nobody checks. Here every change goes through automated tests and a senior engineer's review, and the product is approved on a prototype before any code.
For technical teams
TypeScript, React, Next.js, Node.js, Postgres; mobile apps with offline mode; CI with automated tests on every change; browser verification after every AI build; deployed in an EU cloud, on your accounts.
What are you building next?
You talk to Roman, the founder. Free, and if we're not the right fit, we'll say so.