The operational problem
What happens today, who it affects, and the result you expect once the software exists.
Custom quotes
Every project is quoted to fit
We do not publish rates. Each operation has its own scope, integrations, and pace, and the proposal should reflect exactly that.
What we need to quote
A conversation with context, not a feature list
Who will use it
Teams, roles, and frequency of use. An internal system and a public site are designed differently.
What it connects to
CRM, ERP, spreadsheets, APIs, or legacy systems that must keep working.
Deadlines and constraints
Committed dates, applicable regulation, and what cannot change in the operation.
What defines the investment
Five factors we explain in every proposal
Scope
How many flows, screens, and business rules the system must cover in the first release.
Integrations
How many external systems take part and how well documented they are.
Data
Volume, quality, and migration of existing information.
Design
Whether it builds on an existing product or the experience must be defined from scratch.
Ongoing operation
Support, monitoring, and evolution after launch.
What a proposal includes
A document you can review and compare
- 01
Scope by phase, with verifiable deliverables in each one.
- 02
Proposed architecture and the systems it integrates with.
- 03
Estimated schedule and dependencies on your team.
- 04
Assumptions and what is out of scope, in writing.
- 05
Investment per phase and payment terms.
Ways of working
Three ways to engage
Fixed-scope project
Scope, deliverables, and schedule defined before starting. For clear, bounded needs.
By phases
A first definition or MVP phase; the next ones are quoted with what was learned. For new products.
Ongoing partnership
Capacity reserved each month to operate, maintain, and evolve a system in production.
Custom quotes
Tell us what you need to solve
With the context of your operation we prepare a concrete proposal. If the project is not a fit for what we do, we say so too.
Connect scope and capability