13 · Straight answers to fair questions
- 01
A studio of one lead, without the single point of failure
Your project never depends on one person being there. The code lives in your own repository from day one, it is documented and tested as it is written, it only uses mainstream technology, and a senior developer from our network can take it over.
- 02
Code written by AI agents, decisions made by a senior
Agents write fast, but they do not decide. Architecture and security choices are made by a senior engineer, every feature is covered by automated tests that run at each change, and a dedicated security review comes before every release.
- 03
A quote before we start, and no blank cheque after
You get a global quote before the project starts for everything that can be estimated, and a provisional budget for what cannot. A two-week sprint costs around €5,000 on average, and you can ask for a financial update at any time, or get one at every sprint.
- 04
Two to three months to production, something to see every two weeks
Count two to three months for a first version in production. You will not wait that long to see it, though: a working version is demonstrated every two weeks, and a test environment stays open to you from the start.
- 05
Custom software is no longer the expensive option
Sometimes you should not, and we will tell you when an existing product does the job. But AI and modern development have changed the cost of custom software so much that there are few reasons left to keep bending your business around a tool made for someone else.
- 06
No tech team needed: one person, half a day a week
No technical skills at all. We need one person who knows how your business really runs, available about half a day a week to answer questions and try what we build. The technical side, from architecture to hosting, is ours.
- 07
After launch: we stay as long as you want, and not a day longer
We host, maintain and keep improving your product for as long as it suits you. And because the code, the documentation and the training are yours, you can take it over or hand it to someone else whenever you choose.
- 08
The spreadsheet that runs your company
Not as long as it works. But a file that only one person understands, with a macro that fails every other week, is a risk your turnover depends on. Replacing it starts with watching how you use it, not with a demo.
- 09
A feature request is a symptom, not a prescription
Because a user knows where it hurts, not what cures it. "I want a PDF export" usually means "I lose my Monday writing a report". We build for the reason behind the request, which is often a smaller and better solution.
- 010
You do not need a specification to call us
No, it is the right moment. A company with a problem and no solution is exactly who a studio should work for. Asking the right questions, cutting half the ideas and saying no before you pay for a yes is the most valuable part of our work.
- 011
The best software work is the kind you never notice
For nothing breaking. Software that works goes unnoticed, which makes the work behind it look unnecessary. We make that work visible: the problems avoided, the decisions taken, and what would have happened otherwise.
- 012
AI is not useless. It is mostly used for the wrong things
A chat window is the least interesting use of AI. The same technology reads carbonised scrolls and designs new medicines. In a company, its value shows when it is wired into your own data and tools, on a problem that actually costs you time.
- 013
A release should never be an event
It is the opposite. Fear of releasing comes from large, rare releases and tests that test nothing. Small, frequent releases are easy to check and easy to undo, which is why we should be able to release on a Friday at 5 pm without trembling.