The economics, counted conservatively
06 · Economic effect An ROI canvas for a company with four projects underway. We count only the técnico's code-search time; avoided subsanaciones stay in reserve — though that is where the real money is.
| Parameter | Value | Source / assumption |
| Process and class | compliance screening of design solutions — class B | litcore framework, block 2 · lever: risk/errors + time |
| Volume | 4 projects underway, ~10 code questions per project per month | [estimate] — refined during the audit |
| Search «before» | ~30 min per question: PDFs, editions, commentary | [estimate] — measured during the audit |
| Search «after» | minutes: an answer with the quote and edition | [estimate] — fixed in the pilot |
| Time lever | 40 questions × 0.5 h × €40/h ≈ €800/month | [estimate]; the técnico's rate — your real one |
| Avoided subsanaciones | weeks and months of permit time — reserve | permits run 12–24 months (ASPRIMA [I]); not monetised |
| Costs | Pro from €2,490 + €149/mo | «from» price — approved by the owner |
PAYBACK≈ 5 months. Pro at €2,490 with 40 questions a month and a €40/h técnico rate, on a 40/70/100% adoption curve over 3 months [estimate] — inside half a year. A single avoided requerimiento saves months of permit time and pays the setup back on its own, but that is reserve and stays out of the maths.
Adoption: code questions go into the system instead of being shelved as «I'll ask later»Time: minutes instead of half an hour per code questionQuality: discrepancies caught before filing; every reference verifiable in a minuteConvenience: the técnico gets specific references, not a «look through the whole project»
Not financial advice: the calculation is a proposal built on market reference points; final figures are fixed after the audit and a pilot on your projects.
Want this calculated on your numbers? Request a proposal →