Retain and repair
I favor repair when the core workflow can be reproduced, source and accounts are accessible, and the changes can be bounded by testable acceptance criteria. I keep working parts and test affected behavior.
Software project rescue
A stalled build should not decide your next milestone.
I help funded founders resume products with real users or a committed pilot after an agency engagement or a DIY build. I start with the blocked business outcome and what can be retained.
A conversation about context, impact and fit. This is not a free technical audit or penetration test.
I’m Henrique Pett, a Product Engineer. You work directly with the person who scopes and implements the delivery. Read my background.
Start with the milestone your product cannot reach
For pre-seed and seed founders in the US or Europe without a CTO: onboarding cannot finish, a paid workflow breaks, or a pilot is waiting on an unresolved integration. An agency, internal build or AI tool is the project’s origin, not a verdict on its quality.
What I need to understand
- Which user workflow is blocked, and what does that mean for your pilot or business?
- Who owns the repository and infrastructure accounts, and can authorize access?
- What is the last usable release, and which tests, handover notes and dependencies exist?
- Who can decide priorities and sign off on acceptance with pilot users?
Repair or rebuild?
Rescope before execution
I recommend replanning when essential rules are missing, the structure cannot support the required change, or repair risk cannot be bounded. A partial or full rebuild needs its own scope and budget; it is not automatically included in Production-Ready.
What makes delivery verifiable
This is the acceptance structure I adapt to your project.
- Blocker map
- Recorded expected and actual behavior, affected workflow, dependencies and priorities.
- Bounded changes
- Changes in your repository with agreed scenario tests and regression coverage for the core workflow.
- Release evidence
- A staging demonstration, owner acceptance, and a documented release and rollback plan.
- Continuity
- Operating instructions, client-controlled accounts and a record of known limitations.
Pricing follows scope, not the tool or vendor
You have users or a concrete pilot, an identifiable business impact, a decision-maker and budget for the applicable offer. You can arrange authorized access to source and environments. If the inherited system is poorly understood, I start with a Product Sprint to define scope.
Production-Ready
US$ 7,000
For a usable prototype and compatible scope: 2–3 weeks. I confirm eligibility before contracting. 50% at start and 50% on delivery.
Product Sprint
US$ 3,000
For an uncertain inherited system or undefined scope. Two weeks to define the problem, priorities and execution plan; 100% upfront. This is not a comprehensive technical audit.
If a new MVP is needed, MVP Core is from US$ 15,000, with a separate scope and contract. The Sprint is fully credited toward an MVP signed within 30 days; its deliverables are yours.
See all offers and termsWhat is excluded
- A full rewrite, new features or broad migration within the Production-Ready price.
- 24/7 incident response, emergency support or a promise to rescue every system.
- Penetration testing, certification or regulated compliance without separately engaged specialists.
- Contract disputes with a previous vendor or unauthorized access to their code.
Let’s define the next step.
Bring the blocked workflow, business impact, users or pilot, deadline, decision-maker and budget range for the offer. Confirm whether you can authorize source access. Do not send passwords, keys or customer data; any access will be arranged through invitations and appropriate permissions.
A conversation about context, impact and fit. This is not a free technical audit or penetration test.
Starting from a Lovable app?Before we talk
Do I have to throw away the agency’s work?
No. I assess what can be retained and what must change for the agreed outcome. The project’s origin is not a technical diagnosis.
Does a product I built myself qualify?
Yes, if it serves real users or a concrete pilot and you have authorized access, a decision-maker and a compatible budget. The tool used does not decide eligibility.
Does the free diagnostic include a repository audit?
No. The 45-minute conversation covers impact, context and fit. Technical investigation and deeper scoping require a paid engagement; a Sprint is not a comprehensive technical audit either.