Three ways to work with us
We charge for outcomes, not for hours. The model depends on who carries the scope risk.
For product under continuous evolution
- Assigned, stable team with no rotation
- Fixed monthly capacity, priorities you set
- Deliveries every two weeks
- Includes engineering, design and quality assurance
- Three-month minimum commitment
For well-defined scopes
- A prior assessment that defines the scope
- Price and date per phase, not one global figure
- Scope changes quoted separately, no surprises
- Warranty on what is delivered
- Useful when budget is already approved
For what is already in production
- Infrastructure and deployment operation
- Monitoring, alerting and incident response
- An hours pool for product evolution
- Negotiated service level agreement
- Optional extended coverage
Always included
- Initial assessment at no cost
- Repository and intellectual property in the client's name
- Architecture and decision documentation
- Automated tests and continuous delivery
- Direct access to the team that builds
- Demonstrable fortnightly deliveries
- No abusive lock-in clauses
Frequent questions
Why do you charge for outcomes rather than hours?
Because the hour does not measure what the client buys. A team that delivers the same in half the time is worth more, not less.
Does the assessment cost anything?
The initial assessment, the one that defines the scope of work, does not. A deep technical assessment of an existing system is billable work.
Who keeps the code?
The client, from the first commit. The repository is in their name and architecture documentation is delivered with each phase.
Do you work with clients outside Colombia?
Yes. We work in Spanish and English and have experience operating with teams in different time zones.
What if I want to stop early?
On a dedicated team, with the agreed notice. On a fixed-scope project, the current phase is settled. We do not charge termination penalties.
Can you take over a project someone left half finished?
Yes, and we do it often. It starts with an assessment of the real state of the code before committing to a date.
Let's build a proposal
Tell us the context and we reply with the model that fits best and a concrete figure.
