Vibe coding: what does the application cost after the prototype?
A fictional budget model compares two six-month scenarios and shows the effect of ongoing support, without inventing rates or AI savings.
Define the application before comparing prices
The fictional case is a request tracker used by ten people, with test and production environments. It calls no AI model during operation. AI was used to write code; that does not imply an inference bill for every visit.
The comparison covers six months after the prototype. Scenario A retains a generation platform and its tools. Scenario B assumes export is possible and uses chosen hosting. v0’s GitHub integration is documented; export of this project and its actual conditions were not tested. The scenarios therefore remain economic assumptions to validate.
Separate cost items and period
Coût = jours de reprise × valeur/jour
+ mois × (jours de suivi × valeur/jour
+ hébergement + outils + IA à l’exécution)
+ évolutions décidées hors suiviTakeover covers access, independent execution and the first agreed fixes. Ongoing support covers a defined capacity, without on-call duty in this example. Hosting and tools are counted separately; enhancements outside scope are added when agreed.
Two entirely fictional scenarios
- A, platform retained: 2 takeover days, 1 support day per month, illustrative value of €500 per day, €50 monthly hosting and €40 monthly tools. Over six months: €4,540.
- B, export assumed available: 4 takeover days, the same support and illustrative value, €35 monthly hosting and no retained generation subscription. Over six months: €5,210.
- In both cases: no AI called at runtime, no additional enhancements, amounts excluding tax; incident costs beyond the available capacity are excluded.
These figures are neither Antoine Le Louët’s rates nor a vendor’s prices. The supporting script checks only arithmetic. The €670 difference comes from the chosen assumptions: it demonstrates no general saving in favour of a platform.
Test what changes the decision
One additional support day per month adds €3,000 over six months at this illustrative value. That variation exceeds the difference between the scenarios. Define what support includes and what might increase it rather than comparing subscriptions alone.
If the product actually calls a model, add volumes, billing units and the cost observed on representative use. Check official prices on the quotation date. If export is unavailable or requires an unassessed migration, comparison B remains incomplete.
To request an estimate, provide the uses, period, accounts and features needed after the prototype. Have takeover unknowns estimated separately and set a date to revisit assumptions.