How to choose a tech partner for your MVP
Every agency says it builds great MVPs. Here is a short, vendor-neutral process to find out which one actually will, including when we are the wrong choice.
Updated October 24, 2026: Re-checked every source on October 24, 2026; no facts changed.

To choose a tech partner for your MVP, run a short, paid selection process instead of comparing pitch decks, ending by paying your favorite for one small, real piece of work before you sign anything bigger. The partner who ships that piece well, tells you what not to build, and leaves everything in your name is usually the right one.
Before that paid piece, write down what the first version must prove. Shortlist two or three teams and ask each the same questions. Check who will own the code and the accounts. As of October 24, 2026, the legal and platform facts below come from the primary sources listed at the end.
Who should build or finish your first product: an agency, a freelancer, a studio or a subscription team? That partner might be an agency, a freelancer, a studio or a subscription team, and the product might have started in Lovable, Bolt or a similar AI builder; the process below works for all of them. It is a process, not a ranking. If you want the routes compared on cost and fit, read agency vs freelancer vs in-house first.
What should you decide before talking to anyone?
Decide three things first: the one assumption the MVP must prove, what is already built, and what you can spend over the first twelve months, not just the first release. Also name who on your side makes product decisions. Without these, every proposal looks reasonable and none can be compared.
- The one assumption the first version tests. For example, "small gyms will pay monthly for class booking". Everything that does not test it can wait.
- What exists today: a Figma file, a Lovable prototype, a spreadsheet, or nothing. A working prototype changes the job from building to engineering. Our guide explains what production-ready means for a Lovable app.
- Your budget for twelve months, not for the first release. Hosting, fixes and the second version all cost money too.
- Who on your side makes product decisions, and how many hours a week they have for it.
If you are not sure what belongs in a first version, read what an MVP is. Then write the answers on one page. You will send that page to every candidate, so their answers are comparable.
What kinds of tech partner are there?
Most options fall into five groups: a freelancer, an agency on a fixed project, a development subscription, a fractional CTO or a technical co-founder. Each fits a different stage, and the wrong one is expensive mainly because switching later costs time.
| Partner | Fits best when | Watch for |
|---|---|---|
| Freelancer | The scope is small and clear, and you can review the work | One person is a single point of failure |
| Agency (fixed project) | The scope is stable and a fixed price matters more than flexibility | Change requests repriced mid-project; a handover at the end |
| Development subscription | You expect to keep changing the product after launch | What one plan includes per week or month |
| Fractional CTO | You need technical judgment and hiring help more than hands | Advice without anyone to build it |
| Technical co-founder | Technology is the core of the company for years | Equity and a long search; not a quick fix |
A fractional CTO and a technical co-founder are roles, not vendors, so they are defined separately in our glossary. For how a subscription differs from an agency on price and process, see development subscription vs agency.
What questions should you ask a development agency?
Ask every agency, freelancer or team on the shortlist the same questions, in writing: who will do the work, what they would cut, how they release and test, what happens when scope changes and after launch, who owns the code and accounts, and whether you can speak to a recent client. The answers matter less than how specific they are.
- 01Who will actually do the work?Ask who is accountable for your product day to day, and how you reach them; meet that person before you sign. Sales and delivery are often different people.
- 02What would you cut from my first version?A good partner pushes back on scope. A team that agrees to everything is easy to hire and costly to learn from.
- 03How do changes reach users?Ask how often they release, whether there is a staging copy for testing, and how a release is rolled back if it breaks.
- 04How do you test?Ask which tests run automatically on every change, and who reviews code before it ships. Ask to see a test report from a current project.
- 05What happens when scope changes?Ask how a new request is estimated, how fast, and what it does to the price and the date.
- 06Who owns the code, data and accounts?Ask in whose name the repository, database, hosting, domain and app store accounts will be created. The right answer is yours.
- 07What happens after launch?Ask who fixes bugs, applies security updates and watches errors once real users arrive, and what that costs.
- 08Can I speak to a recent client?Ask for one from the last twelve months, and ask that client what went wrong and how the team handled it.
Who owns the code a partner writes for you?
Not automatically you. Under US copyright law, as of October 24, 2026, copyright belongs first to the author (17 U.S.C. 201). Work an employee does as part of the job belongs to the employer. An outside contractor's work is "made for hire" only in nine listed categories, and only with a signed written agreement saying so (17 U.S.C. 101).
Software is not named on that list.
So the usual route is an assignment: a written transfer of the rights, signed by the owner. The law requires that for a transfer of copyright ownership (17 U.S.C. 204). Make sure your contract contains one and that it covers code written by subcontractors too. Check when the rights pass to you: as each invoice is paid is safer than only when the whole project ends. This is general information, not legal advice; have a lawyer read the contract.
Ownership of the accounts matters as much as ownership of the rights. Ask for the code repository, the database and the hosting to be created in your own organization from day one, with the partner invited as members. Moving them later is possible but has conditions. GitHub's documentation says a repository transfer needs admin access to the repository, and that its issues, pull requests and wiki move with it. Supabase's documentation says only the owner of the source organization can transfer a project. An active GitHub integration or log drains must be removed first.
What are the red flags?
Red flags include a fixed price before anyone has seen your prototype, your repository in the partner's accounts, no staging or automated tests, nobody accountable for delivery, a yes to everything, no plan for after launch, and a rewrite from scratch without a reason. Most bad partnerships show warning signs before the contract is signed. Watch for these:
- A fixed price and date given before anyone has seen your prototype or asked what the MVP must prove.
- The repository, database or hosting will live in the partner's accounts "for now".
- No staging environment, no automated tests, or "we test manually before launch".
- Nobody is accountable for delivery: you only ever talk to sales.
- Every question gets a yes, and nothing in your scope is challenged.
- No answer to what happens after launch, or support that is priced only once you ask.
- A plan to rewrite your working Lovable prototype from scratch, without a reason tied to what it must prove.
One red flag is not always a dealbreaker. Two or more on the same candidate usually is.
Why pay for a first change before you commit?
Because a small, real piece of work tells you more than any proposal. Pick a change that matters but is small: a sign-up flow, one integration, a set of access rules. Pay the shortlisted favorite to deliver it, in your repository, through their normal process.
Then judge what you got, not what you were promised:
- Did it arrive when they said, and did they tell you early about any delay?
- Is it live, or on a staging copy you can click through, rather than in screenshots?
- Did it come with tests, and do they run on their own?
- Can you read the pull request and understand what changed and why?
- Did they ask good questions, or did they guess?
A first change costs a fraction of the project and protects the rest of it. If the work is good, you continue with evidence. If it is not, you have lost a week, not a quarter. If you built your prototype in Lovable, our guide to hiring a Lovable developer adds what to look for in that case.
How do you compare the finalists?
Score each finalist from 1 to 5 on the same five lines: evidence, ownership, release process, fit, and cost over twelve months. Weigh the first two most heavily: evidence from the paid first change, test reports and a recent reference, and ownership of the code, data and accounts. Here is what each line covers:
- Evidence: the paid first change, test reports and a recent reference.
- Ownership: code, data and accounts in your name, with an assignment in the contract.
- Release process: staging, automated tests, review by a second engineer, rollback.
- Fit: they understood what the MVP must prove and cut scope to match it.
- Cost over twelve months, including the work after launch.
Price comes last on purpose. The cheapest quote is often the most expensive project once rework and a second partner are counted. To sanity-check a quote, compare it with what the build should cost on each route.
When is Plutonapps the wrong choice?
Plutonapps is the wrong choice for a one-off fixed-scope build, a founder seeking a technical co-founder or mainly advice, or a budget below any team's cost. We are a development subscription for founders who design in Lovable and need engineers to turn each version into a live product. That is a specific fit; these cases are better served elsewhere:
- You need a one-off build with a fixed scope and no changes after launch. A fixed-price agency or a strong freelancer fits better.
- Technology is the company's core for years, and you want someone with equity. Look for a technical co-founder.
- You mainly need advice, hiring help or a board-level view. A fractional CTO fits better.
- Your budget for the year is below the cost of any team. Keep building in your AI tool and validate first.
Starter is $2,999 a month paid annually, $3,999 a month billed quarterly, or $4,999 month to month; Growth is custom. A month-to-month Starter plan can be canceled at any time and stops at the end of the current billing month. See pricing. To see where your app stands first, take the free production-readiness check: 22–35 questions, a score out of 100 and your three biggest risks. If you already have an AI-built MVP that is misbehaving, our vibe coding rescue starts with an architecture review of what exists and builds around what works.
Sources
Each legal and platform fact above comes from one of these pages, checked on October 24, 2026. We review this page every 30 days.
- US Code, 17 U.S.C. 201: Ownership of copyright (law.cornell.edu/uscode/text/17/201).
- US Code, 17 U.S.C. 101: Definitions, "work made for hire" (law.cornell.edu/uscode/text/17/101).
- US Code, 17 U.S.C. 204: Execution of transfers of copyright ownership (law.cornell.edu/uscode/text/17/204).
- GitHub documentation: Transferring a repository (docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository).
- Supabase documentation: Project transfers (supabase.com/docs/guides/platform/project-transfer).
- Lovable documentation: GitHub integration (docs.lovable.dev/integrations/github).
- Plutonapps: our pricing page, plan terms and Ripply case study, as published on this site (plutonapps.com/pricing; plutonapps.com/legal/refunds; plutonapps.com/work/ripply).
Common questions
How long should choosing a tech partner take?
Two to four weeks is usually enough for an MVP. Spend one week on your one-page brief and shortlist, one on questions and references, and one or two on a paid first change from your favorite.
Should I pay for a trial project?
Yes. A small paid change, delivered in your own repository through the partner's normal process, shows how they plan, test, communicate and release. Unpaid trials tend to get less care and tell you less.
Do I own the code a contractor writes for me?
Not automatically under US law. Custom software by an outside contractor usually needs a written, signed assignment of the rights. Check that your contract has one, that it covers subcontractors, and ask a lawyer to review it.
Is a fixed price safer than paying monthly?
Only if the scope will not change. MVPs usually change once users arrive, and a fixed price then turns into repriced change requests. If you expect to keep changing the product, an ongoing arrangement is easier to plan.
Can a partner keep working on my Lovable prototype?
Yes. Lovable's GitHub integration syncs code both ways, and the repository lives in your own GitHub account or organization, so engineers can work on the same code. Ask any candidate how they keep your Lovable edits and their changes in step.
More on this: Product strategy & scoping · How to hire a Lovable developer or Lovable expert (and what it costs)
Built something in Lovable you want people to rely on?
We are the engineers who take it the rest of the way — secured, tested, released and supported.


