Founder guide

Building an MVP While Employed: Time, Budget and IP Pitfalls

Published October 28, 2026 · By the SquadPrime Team · Keep the job, keep the IP, ship in six weeks

Yes, you can build and launch an MVP while you keep your job, and for most first-time founders that is the right order. The three things that go wrong are predictable: an employment agreement that quietly hands your employer the intellectual property, a budget that is really a credit card, and a plan that assumes free evenings you do not have. This guide handles each with numbers: the clauses to check and what an attorney review costs, a salary-based rule for the budget, the time math of self-build versus paying a team, and a six-week plan in which an outside team builds while you spend three to five hours a week on demos and users.

Read the employment agreement before you spend a dollar

The most expensive MVP mistake an employed founder can make costs nothing up front: building something your employer can later claim. Pull up the agreement you signed on day one, plus any later equity or confidentiality agreement, and find these clauses.

Clause	What to look for	Risk if ignored
Invention assignment	Language assigning "all inventions conceived during employment" to the company, with or without a carve-out for your own time and equipment	Employer owns your code and your idea
Outside activities / moonlighting	A ban on outside business activity, or a requirement for written approval before starting one	Termination for cause, loss of unvested equity
Non-compete and non-solicit	Which products, customers and markets are off limits, and for how long after you leave	Injunction or lawsuit if the MVP overlaps

State law changes the picture. California, Delaware, Illinois, Kansas, Minnesota, Nevada, New Jersey, North Carolina, Utah and Washington have statutes that stop an employer from claiming inventions you made on your own time, with your own equipment, that do not relate to the employer's business. In the other states the contract largely governs, and a broad clause can reach further than you expect.

Do not guess. A one-hour employment agreement review by an attorney costs $300 to $600 in most US cities in 2026, and $600 to $900 in San Francisco or New York. Flat-fee online review services run $250 to $500. Against a $4,000 to $15,000 build, that review is the cheapest insurance you will buy this year.

Nothing in this article is legal advice. The clause names and state list are a reading guide for the conversation with your own attorney, not a substitute for it.

The four separation rules, and the evidence that proves them

Almost every dispute over who owns a side project comes down to four facts. Set them up before the build starts and keep a paper trail, because the burden of showing the project was separate will fall on you.

Rule	What it means in practice	Evidence to keep	Cost
1. Your own hardware	Never open the project on a company laptop or phone, not even in the browser.	Purchase receipt dated before the first commit	$600 to $1,200 for a capable laptop
2. Your own time	Evenings, weekends, vacation days. Not lunch at your desk.	A simple dated time log: date, hours, what you did	$0
3. Your own accounts and network	Personal email domain and cloud accounts, home or mobile internet. Never the company workspace or VPN.	Account creation emails under your personal address	$12 to $20 per year for a domain
4. No overlap with the employer	Different market, different customers, no confidential data, no company code, no coworkers as testers.	A one-page memo on how the product differs from the employer's business, dated and emailed to yourself	$0

Rule four is where honest founders get caught. "I sell software to dentists and my employer sells software to hospitals" is closer than it sounds. If a reasonable person would say your product serves the same customers or an adjacent problem, get the attorney's opinion before you build, because separate hardware does not fix an overlap in subject matter.

The same ownership question applies on the other side of the build. Whoever writes the code must assign it to you or your company in writing, so check the vendor contract for an IP assignment clause before you sign. At SquadPrime 100% of the code is yours on delivery, and the accounts a founder must own before the build are opened in your name from day one.

Budgeting an MVP from a salary

Real 2026 prices for a first version, so you can size the target before you look at your savings:

Landing page and waitlist, built yourself: $0 to $500.
App-builder MVP by a freelancer: $2,000 to $6,000, plus $30 to $150 a month in platform fees.
Custom fixed-price MVP from a studio: $4,000 to $15,000 depending on scope, agreed before the build starts.
Hourly agency build: $20,000 to $60,000, final number unknown until the invoice arrives.

The rule we recommend to employed founders: the build plus six months of running costs should not exceed two months of your net take-home pay. It never comes out of a three to six month emergency fund, and never goes on a credit card, where 2026 purchase rates of 22% to 29% turn a $9,000 build into $11,000 over two years of minimum payments.

Worked example. On a $95,000 salary in a mid-tax state, net pay lands around $5,800 a month, so the cap is about $11,600. Running costs for a typical MVP are $30 to $150 a month, or $100 to $400 with AI features, so set aside about $900 for six months of services and keep roughly $10,500 for the build. That covers a $4,000 to $10,000 fixed-price build with a 10% to 15% contingency for the one change you will want after launch.

Budget tier	What it buys in 2026	Save per month	Months to fund it
$4,000 to $5,000	One core flow, sign-up, a simple dashboard, payments via a hosted checkout. See what you can build for under $5,000.	$800	5 to 6
$8,000 to $10,000	Two or three connected flows, an admin panel, email notifications, one integration or a basic AI feature.	$1,500	6 to 7
$12,000 to $15,000	A two-sided product or a mobile app with a backend, roles and permissions, reporting, store submission.	$2,000	6 to 8

Those saving months are not wasted. Use them for the validation work that costs nothing: thirty customer conversations, a waitlist, a pre-sale. A founder who arrives with the cash saved and ten people who said "yes, I would pay" is in a different position from one who borrowed the money to find out. For a fuller framework see how to budget for an MVP, and run your feature list through the free MVP cost calculator before you talk to anyone.

Build it yourself at night, or pay a team? The time math

Be honest about the hours. A full-time employee with a commute, a family or both can reliably give a side project six to ten hours a week: two hours on three weeknights plus a half day on the weekend. Everything above that is borrowed from sleep and does not last past month two. Compare what those hours buy.

Route	Founder hours	Calendar time at 8 hrs/week	Cash	What you own at the end
Learn to code, then build	400 to 800 hours	12 to 24 months	$0 to $1,000 in courses and tools	Working code, maybe
App builder, built yourself	100 to 200 hours	3 to 6 months	$360 to $1,800 a year in platform fees	A product locked to one platform
Freelancer, hourly	60 to 100 hours managing	2 to 4 months	$3,000 to $12,000, open-ended	Code of variable quality
Fixed-price senior team	20 to 30 hours total	2 to 6 weeks	$4,000 to $15,000, agreed up front	All the code, accounts in your name, a launch date

The numbers point one way. Your scarce resource is attention, not money, and the only hours that cannot be outsourced are the ones spent with customers. A six-month self-build also carries a risk a two-week build does not: in six months the job gets busier, the idea gets stale, and most side projects quietly die before they reach a user. A fixed price compresses the risk window into weeks and puts a date on the calendar. The exception is a landing page or a spreadsheet-and-email concierge test, which you should always do yourself first because it costs nothing and tells you whether the build is worth funding at all.

The six-week plan with an outside team

This is the schedule that works for employed founders, with your hours per week stated so you can check it against your calendar before you commit. It assumes a fixed-price team that ships a working product in 14 days.

Week	What happens	Your hours	What you decide
Week 0 (before signing)	Attorney reviews your agreement. You form the company, open the accounts, write a one-page spec and pick three to five features.	6 to 8	Go or no-go on the build, and the exact scope
Week 1	Kickoff call, then the team builds. You answer questions within 24 hours. A private preview link you can click arrives by day 5.	3 to 4	Any correction to the core flow, now, while it is cheap
Week 2	Live demos every few days. You test on your own phone against the acceptance criteria. Live on day 14.	4 to 5	Accept, or list the specific gaps
Week 3	First 10 to 20 users, onboarded by hand. You answer every message and watch where people stall.	5 to 6	Which one thing blocks activation
Week 4	Measure: who completed the core action, who came back within seven days, who tried to pay.	3 to 4	Whether the numbers justify the next change
Week 5	One change, not five. Test a price. Ask the people who did not return why.	3 to 4	Pricing and the next feature, or none
Week 6	Decision week: kill, keep part-time, or plan the transition out of the job.	2 to 3	What the next 90 days look like

Two habits make this plan survive a day job. First, put the review slots on your calendar now: Tuesday and Thursday 8 to 9 pm, Saturday 9 to 11 am. A team that waits two days for an answer loses two days of schedule. Second, learn how to review a demo without a technical background: open the preview on your phone, walk the exact path a new user would walk, and write down where you hesitated.

Entity, accounts and the paper trail

Form the company before you sign the build contract, so the contract, the IP assignment and every account are in the company's name. In 2026 a single-member LLC costs $50 to $500 in state filing fees: Wyoming is $100 to file and $60 a year, Delaware is $110 to file plus a $300 annual franchise tax, and most other states fall between. A registered agent adds $50 to $150 a year. Allow two to three weeks for the filing, an EIN from the IRS and a business bank account.

Then open the accounts you must control: domain, hosting, app store developer accounts if you are going mobile, the payment processor, email sending and analytics. Every one under your personal or company email, never an employer address, with you as owner and the build team as an invited collaborator. Start the dated folder at the same time: attorney's notes, time log, hardware receipt, the signed vendor contract with its IP clause, and the memo on how the product differs from your employer's business. If a question is ever raised, that folder is your answer.

When to tell your employer, and when to quit

If the agreement or the employee handbook requires disclosure or written consent for outside work, ask. The answer is usually yes when the product is clearly unrelated, and a written approval with a carve-out ("the company claims no interest in Project X as described") is stronger protection than any amount of careful separation. Ask by email, describe the product in one paragraph, and keep the reply. If nothing requires disclosure, you are not obliged to volunteer it.

Do not resign to build the MVP. The MVP is the experiment that tells you whether the idea deserves your full attention, and running it on a salary removes the pressure to declare victory early. A reasonable trigger to leave is three consecutive months of revenue covering at least half of your net pay, or a signed funding round, plus six to twelve months of personal runway. Most founders stay employed for six to twelve months after the first version ships. When you do leave, give proper notice, return every piece of company property and do not touch company files in your last weeks, because a clean exit protects the IP you spent a year keeping separate.

Our recommendation

Keep the job. Spend $300 to $600 on an attorney before anything else. Set up the four separations with a paper trail. Validate with conversations and a waitlist while you save the budget over four to eight months, capped at two months of net pay. Then hand a tight spec to a fixed-price senior team, hold three to five hours a week for reviews and users, and make the real decision in week six with data instead of hope. At SquadPrime we build that version at one fixed price from $4,000, agreed before the build starts, live in 14 days, with all the code yours on delivery, which is the shape of risk an employed founder can afford.

Have a spec? Get one fixed price for it.

Bring your spec to a free 30-minute call. We will pressure-test the scope, flag anything that will inflate the build, and quote one fixed price (from $4,000). Live in 14 days or you don't pay, and you own all the code.

Get My Launch Date & Fixed Price

FAQ

Can my employer claim ownership of an MVP I build on my own time?

It depends on your employment agreement and your state. If you signed a broad invention assignment clause and built the MVP with company equipment, during work hours, or in your employer's line of business, the employer may have a claim. Several US states limit those clauses to inventions that relate to the employer's business or use its resources. The safe path is to build only on your own hardware, on your own time, in an unrelated field, and to have an employment attorney read your agreement before you spend money.

Do I have to tell my employer that I am building a startup?

Only if your agreement or company policy requires disclosure or written approval of outside activities, which many do. If it does, ask in writing and keep the answer, because a written carve-out is the strongest protection you can get. If nothing requires disclosure, you are not obliged to tell anyone, but you must still follow the rules on equipment, time, and confidential information.

How much of my salary should I spend on an MVP?

A workable rule is that the build plus six months of running costs should not exceed two months of your net take-home pay, and should never come out of a three to six month emergency fund or a credit card. On a $95,000 salary that is roughly $11,000, which comfortably covers a fixed-price custom MVP in the $4,000 to $10,000 range. Save it over four to eight months before you sign anything.

How many hours a week does an MVP build take from the founder?

With an outside team doing the building, plan on three to five hours a week for six weeks: answering questions within a day, reviewing a demo every few days, testing on your own phone, and talking to your first users. Building it yourself at night takes 100 to 200 hours with an app builder and 400 to 800 hours if you learn to code first, which means months or years at a typical eight hours a week.

Should I quit my job before building the MVP?

No. The MVP exists to find out whether the idea deserves your full time, so build it while the salary is still paying the bills. A reasonable trigger to leave is three consecutive months of revenue covering at least half of your net pay, or a funding round, plus six to twelve months of personal runway. Most founders stay employed for six to twelve months after the MVP ships.

All third-party names and trademarks belong to their respective owners and are used for identification only. Any market figures reflect our experience building MVPs and typical ranges as of October 28, 2026, and may change at any time. Spotted something outdated or inaccurate? Email talk@squadprime.com and we'll correct it promptly.