Before committing budget, understand what you are going to build — or what you need to fix
You trade a large, unknown risk — the budget that blows up mid-build — for a small, known cost. Estimating without it is a shot in the dark.
- 30-min call — free, no commitment
- 100% credited if the project moves forward
- The material is yours, even if it doesn't
Discovery unlocks the project
You asked for an estimate. Anyone can throw out a guess — but a number you can trust takes a process. Ours is short and fully online: from the conversation to a technical plan on the table.
- 1
You ask for the estimate
Describe the idea or the problem in a couple of lines through the form. We confirm the next step within 24 business hours.
- 2
A 30-min call
You walk us through the project briefly. This first call isn't meant to solve anything — it's to gauge the size and point you to the right Discovery level (Light, Standard or Deep). It's free and with no commitment.
- 3
Discovery proposal
The recommended tier with scope, timeline and the Discovery fee settled — no range, no surprise. 100% credited if the project moves forward.
- 4
Discovery: the real size
The technical study reveals the true scope of the work and becomes documentation — requirements, architecture, a flow diagram — with the value range and deadlines. That's when the estimate stops being a guess and becomes a value proposal, with expectations aligned.
You leave with:
- Scope and risks mapped
- Justified technical recommendation
- Range estimate
- Clear next steps
Two paths, one starting point
Discovery is the build's Phase 0
The blueprint before the build: requirements, architecture, and roadmap before committing the budget. At kickoff it becomes the skeleton of the repository — and you move in steps you see running.
- Discovery
- POC
- MVP
- 1.0
Discovery is the diagnosis
Performance, bugs, code review, audit, legacy: measurements, prioritized bottlenecks, and the root cause — with an actionable plan, not guesswork.
Three levels of depth
Ranges vary by service. In the 30-min call — free — we settle your tier and the Discovery fee, fixed, before any commitment.
Discovery Light
Focused technical decision: choose a stack, evaluate an RFP, code review, or a small, well-defined project.
$2,000 – $4,000
- 5–10 business days
- 1h kickoff + analysis
- 8–15 page document
- 1h presentation
Discovery Standard
Deep project analysis: scope, architecture, stack, and 3 priced alternatives.
$4,000 – $9,000
- 2–3 weeks
- Kickoff + 1–2 sessions
- Code/infra review
- 20–35 page document
Discovery Deep
Multi-stakeholder: workshops, process mapping, phased roadmap, change management.
$8,000 – $15,000
- 3–4 weeks
- 2–3 kickoff sessions
- Workshops
- 35–60 page document
- 2 presentations
Ranges by tier — your service decides where you land. Your Discovery fee is settled in the 30-min call (free); the project's qualitative range (the build) is refined within the Discovery itself, and the Discovery is 100% credited if the project moves forward.
Why start with Discovery
The biggest source of failure in software projects is not bad code — it is a misunderstood scope. A fixed proposal without a diagnosis is an expensive guess: scope shifts mid-flight, cost overruns, and the relationship sours.
Starting with Discovery flips that: you trade a large, unknown risk — the overrun that costs double down the line — for a small, known cost now. And there is no trap: if the project moves forward, the fee is 100% credited; if it does not, the material is yours to execute with anyone. You leave with clarity either way.
The three depth levels
You don't have to guess the tier — we frame it in the 30-min call. What changes between them is depth and the format of the deliverable. To build from scratch, the usual starting point is Standard; small, well-defined projects are handled by Light.
Discovery Light
A single, focused decision, in days. To build: a technical opinion — recommendation, evaluated alternatives, risks, and an effort range (choosing a stack, evaluating an RFP, a focused code review, or scoping a small, well-defined project). To optimize: a quick audit of one dimension — measurement, three to five bottlenecks, and quick wins. An 8-to-15-page document, with a kickoff and a presentation.
Discovery Standard
The usual starting point for building from scratch — and for teams that already have a product and need to evolve without breaking what works. To build: a lean SRS with a mini-SAD — requirements, high-level architecture, a justified stack, risks, roadmap, and three priced packages. To optimize: a full diagnosis with root cause and a ranged execution plan. Includes a code/infra review and a 20-to-35-page document.
Discovery Deep
For strategic, multi-stakeholder, high-impact projects. It delivers the full SRS + SAD — with strategic DDD, data model, integrations, threat surface, ROI per phase, change management, and an executive presentation. This is where RFP review and tenders come in; legacy modernization always lives here. A 35-to-60-page document, with workshops and two presentations.
Ready to understand your project?
Describe your scenario in the contact form and we return a feasibility read with the recommended Discovery level within 24 business hours. The initial diagnosis is free.
FAQ
Why not just send a development proposal directly?
Because a proposal without a diagnosis is guesswork. Scope shifts, costs explode, the relationship sours. Discovery makes sure we are talking about the same thing — with scope, risks, and a range on the table — before any larger commitment.
Build or diagnose — what is the difference?
It depends on the nature of the work. To build something new (custom software, AI, modernization), the deliverable is the spine of the project: requirements, architecture, a range estimate, and a roadmap. To optimize what already exists (performance, code review, audit), the deliverable is a diagnostic report: measurements, root cause, prioritized bottlenecks, and recommendations. Both come out of Discovery.
Is the Discovery fee credited toward the project?
Yes. When the project moves forward with ConsoliDados, the Discovery fee is fully credited toward the execution budget — 100% applied, in any tier or family.
What if the project does not move forward after Discovery?
You keep all the produced material — whether the build plan (architecture, estimates, roadmap) or the diagnostic report. You can take it to another vendor or run it internally. The deliverable is yours.
How long does it take?
From about a week at Light to three or four weeks at Deep, depending on the depth and your team's availability for the requirements sessions.