The process analysis
We watch how the work is done today, who enters what, where it breaks. The scope of the first version is whatever saves the most time the fastest, and nothing else.
Custom software, by a studio that runs its own.
We know what software costs after launch, because we run four. We design yours accordingly: maintenance planned for, improvements possible, code and data in your name.
What is delivered.
A tool that replaces the spreadsheet and the messaging group, not one more piece of software alongside them.
The software
Web, mobile or both, on the stack of our own products: Next.js, Supabase or Firebase, Flutter, Stripe, Vercel. Chosen because we run it in production, not because it is fashionable.
Hosting and security
Accounts in your name, backups, role-based access, an action log. Your data sits in a database you can export at any time.
Ownership
The source code, the database and the hosting accounts belong to you from the first payment. You can leave with them and hand them to whoever you want.
How it runs.
In order of magnitude, from 8 weeks for a first version, depending on scope. Not a contractual commitment: the firm schedule is set after the analysis.
- 1
Analysis
one weekInterviews with the people who do the work. A map of the current process. The scope of the first version.
- 2
Design
one to two weeksScreens and data model. A prototype tested with your teams before development.
- 3
Development
from five weeks, depending on scopeDeliveries every two weeks on a test address. You use the tool with real data before the switchover.
- 4
Switchover
one week, handover includedImport of existing data, training, decommissioning of the old system.
- 5
Operation
ongoingMaintenance, monitoring, improvements in batches. That is where the software really begins.
After launch.
What most quotes leave out, and what we live through every week with our own products.
Maintenance
Dependencies age, browsers and phones change, providers alter their terms. Software without maintenance stops working silently. We plan for it in the contract, not in an amendment.
Evolution
The first version is deliberately short. What your teams ask for after a month of use is worth more than what everyone imagined beforehand. Improvements are quoted in batches and delivered in batches.
Ownership of the code and the data
Code repository, database and hosting are in your name. If we disappeared tomorrow, your tool keeps running and another developer can take it over.
What we learn from our products
NightBook, Swapp, Georgia and Rackts teach us every week what breaks in production. Those lessons are in the quote for your software.
See our productsFrequently asked questions.
Why not use off-the-shelf software?
Often you should. If an existing tool covers 80 % of your need, we tell you during the analysis. Custom is justified when the process is the heart of your business.
Who owns the code?
You do, from the first payment. The repository and the accounts are in your name.
Can we start small?
That is the rule, in fact. The first version covers the one thing that wastes the most time, and nothing else.
What happens if you stop?
Your software keeps running on your accounts. The documentation and the code let another developer take over.
A process still running on a spreadsheet?
Describe it in a few lines: who enters what, where it gets stuck. We reply within two working days.