Option A
Standard SaaS
It works when your operation matches what the vendor expects. When it does not, workarounds start: unused fields, parallel spreadsheets, reports nobody quite trusts. Your company contorts to fit.
Own Vertical Software · SVP
Install your own operating system.
Vertical architecture that already contains the foundations of an enterprise system and adapts to your company's actual operation. SaaS fits you or it does not. Starting from zero costs what it costs. This is the third way.
Your data, your rules, a vertical body already proven in your sector. Perpetual license of the core if agreed. Implementation in 6 to 12 weeks from diagnosis to go-live.
Why SVP
SaaS forces you to operate as it was designed. Starting from zero makes you pay every time to build the same foundations.
Option B
From-scratch development
Full freedom. And also identity, users, permissions, cases, documents, audit, integrations. Each new project re-implements those pieces before touching the specifics. High cost, long timeline, foundations paid for once more.
SVP · Third way
Own Vertical Software
We start from a vertical body already built for your sector. We adapt it to your actual operation using AVA. The result is yours, runs as you need, and scales without rebuilding the base.
Composition
The common, the differential, the exceptional
It is not a template with your logo. Every implementation separates explicitly what is already productized, what configures without new code, and what develops exclusively. Each part is scoped and billed differently.
The common is productized
Technical infrastructure any enterprise system needs: identity and permissions, organizations and teams, cases and states, documents and versioning, tasks and notifications, audit, integrations, search, rules, model orchestration, consumption control, human review, observability, export.
The differential is configured
Your sectoral data model, your case and document types, your vocabulary and business rules, your approval flows, your corporate integrations, your permission levels, your templates and your state names. Without writing new code. Without generating tech debt.
The exceptional is developed
When something does not fit the vertical body but is part of your strategy, it is developed exclusively. Scoped separately. Integrated into the system. And it stays maintainable because the common core does not change.
Adaptive Vertical Architecture · AVA
How we deliver SVP in 6 to 12 weeks
The 6 to 12 week range covers the full cycle, from diagnosis to go-live with real data. Five phases with verifiable outputs. The budget is closed at the end of phase 2, not before.
Diagnosis
We understand how your company operates today. Who decides what. What data exists, where, in what format. What systems you already use. Where the bottlenecks are and where change would move the needle. Output: structured diagnosis.
Design
We map your sector's vertical body to your actual processes. We define what goes into the common (ready), the differential (configured) and the exceptional (developed). Detailed budget and timeline. Output: architecture document and per-phase closed quote.
Configuration
Dedicated instance live. Master data ingestion. Configuration of permissions, states, flows, rules and integrations. Exclusive development runs in parallel. Output: system running on test data.
Migration
We import real data. Validate integrity. Phased rollout if the sector is regulated. Output: production data in the system.
Operation
Your team takes over day-to-day. Support and evolution under agreement. Emerging changes are scoped and quoted. Security updates applied. Output: system in your hands.
Proven experience
Four vertical bodies already in operation
If your problem fits one of these, adaptation is faster and risk is lower because the patterns are already solved. If your sector is new for us, we design a new vertical body. Either way, total time beats starting from an empty repository.
- Vertical body
Public procurement
Vertical body for tender analysis, proposal management, active procurement tracking and affinity scoring. Usual integrations with public procurement portals, ERPs and official databases.
- Vertical body
Legal procedures
Vertical body for case management, deadline calendars, procedural documentation, contact directory and accessible legislation. Integrations with email, calendars and document management systems.
- Vertical body
International logistics operations
Vertical body for freight forwarders, containers, customs documentation, automatic demurrage and margin-aware budgets. Dedicated OCR to classify incoming documents without human input in the base case.
- Vertical body
Certifications and quality audit
Vertical body for the certification lifecycle, audits, findings, issuance and renewals. Declarative engine that models any standard without changing core code.
Budget
The market sets the range, not a fixed price list
Instead of publishing our own price, we publish the range map already published by Spanish competitors with sources visible, and locate SVP inside that map. Your case is quoted in the free session after the diagnosis.
Where SVP fits
- In the complex enterprise project range (market reference: €40k to €60k+).
- In the platform or advanced enterprise ERP range (market reference: €60k to €100k+).
- Not in the internal MVP or standalone module range, because SVP is not a lightweight tool.
Next step
Ready for a system that scales with you?
30 minutes, no commitment. I listen to your operation, tell you whether SVP fits and in what budget range. If we are not the right fit, I recommend who is.