Pricing plans shaped around how the work will be delivered
Choose from a defined project quote, dedicated monthly capacity, a fixed-fee discovery or a managed support retainer. We confirm the right model and its assumptions before issuing a tailored proposal.
Match commercial structure to delivery certainty
There is no artificial one-size-fits-all package. Each option makes a different commitment clear: scope, capacity, evidence or ongoing service.
Milestone-based quote
Fixed-scope project
For a defined product, feature, integration or modernisation outcome with agreed deliverables and acceptance criteria.
Monthly capacity
Dedicated delivery team
For an evolving roadmap that benefits from stable product and engineering capacity over a longer delivery period.
Fixed-fee timebox
Discovery & assessment
For turning an uncertain idea, system risk or technology decision into evidence, options and an actionable delivery recommendation.
Recurring retainer
Managed support
For maintaining, supporting and improving live applications within an agreed service boundary and operating rhythm.
Know what is included before work begins
The proposal records the boundaries that matter commercially and operationally. Any estimate or budget range is accompanied by the assumptions that support it.
Review engagement models- Commercial basisScope, capacity, timebox or service coverage.
- Delivery expectationsOutputs, milestones, review and acceptance.
- ResponsibilitiesClient, Juan Infotech and third-party dependencies.
- Change processHow new information affects price and timing.
Clear answers before a proposal
No. Software delivery depends on scope, roles, integrations, risk, timeline and operating expectations. We recommend the commercial model first, then provide a written proposal based on the evidence available.
Yes, when there is enough context to state the assumptions and uncertainty. A range is an early planning aid, not a final commitment.
A proposal normally states the scope or capacity, deliverables, roles, milestones or service period, responsibilities, assumptions, exclusions, payment schedule and change process.
Unless specifically included, third-party licences, cloud consumption, paid APIs, hardware, app-store fees, taxes and client-side resources remain separate and are made visible before approval.