Case file
From your code to a live link.
Every build runs the same entries in the same order: who is holding the work, and what happens if it fails there.
- 0 minYou
You send the brief and the code
Say what it should do in a few sentences. Upload a zip of your project, paste a public GitHub link or the code itself, or send nothing and we build from scratch.
If it fails hereNothing is charged for sending it, or for the estimate.
- 1 minAI
The code is read and priced
You watch it happen: the zip is opened, the files counted, the stack mapped from your manifests and the code read. The estimate lists what already works, each piece of work left with its hours, the risks, the days and the price.
If it fails hereIf the zip cannot be opened or the repository is private, you are told why and nothing is saved.
- Any timeYou
You accept the estimate
The price is the hours times 400 credits, €26.64 to €39.20 an hour at the bundle rates. Leave pieces of work out first if you want less, and the price follows the hours you keep. Accept it and the credits are taken; the estimate stays on your project if you want to decide later.
If it fails hereUntil you accept, it costs nothing.
- DaysEngineers
We build it
The team gets your brief, your code and the estimate the moment you accept, and builds it. Your project page shows it as building.
If it fails hereIf we cannot take it on, every credit goes back to your balance, with the reason.
- DoneYou
You get the link
The live URL and the full source appear on your project, with a note from the engineers.
If it fails hereIf something we delivered does not work, report it from the project within 30 days and we fix it at no charge.
About the time
- Where the time goes
- The estimate takes about a minute. The build takes the days in the estimate: that is engineers writing, testing and deploying your app.
- Why not just generate it?
- Because generated code tends to stall at the hard part: auth, payments, data and deployment. That is work people do.