Focused delivery
$1,500–$5,000
For a bounded problem with a clear outcome in an existing product or workflow.
- Technical audits and delivery plans
- Third-party integrations
- Production fixes and improvements
- One focused feature or workflow
Pricing
Every product is different. These ranges show the usual scale of work before I review your goals, codebase, dependencies, and delivery constraints.
Focused delivery
For a bounded problem with a clear outcome in an existing product or workflow.
Product milestone
For a substantial product area that can be planned and delivered as one milestone.
Full product delivery
For an end-to-end release spanning several parts of the product and its delivery.
These are typical project ranges, not rigid packages. The exact estimate follows a review of scope, access, dependencies, and delivery risk.
Describe your projectFAQ
The useful answer usually depends on the product, but these are the terms I clarify before proposing the work.
Most project work is scoped as a fixed milestone with agreed deliverables, timing, and price. When the codebase or requirements contain important unknowns, I propose a short paid discovery before fixing the delivery estimate.
Send the outcome you need, what already exists, the main constraints, and any relevant product, repository, design, or documentation links. A deadline and decision-maker context also help me produce a useful estimate.
Yes. A focused engagement can start with the current application, infrastructure, and delivery process. I first review the relevant code and constraints, then define the smallest responsible scope for the requested outcome.
The proposal lists the agreed implementation, appropriate testing, delivery work, and handover. Hosting, paid third-party services, content production, and other external costs are identified separately when they apply.
If a new request changes the agreed outcome or delivery effort, I explain the impact and estimate it before continuing. Small clarifications stay inside the milestone; material additions become a separate scope or follow-up phase.
Yes. Discovery is useful when the product, codebase, integrations, or requirements need investigation first. It ends with documented findings, delivery risks, a recommended scope, and a more reliable estimate.