A SaaS vendor’s proposal usually covers features, a timeline and a price. What it often leaves out decides how much the product costs you in the years after launch: whose name the cloud and billing accounts are in, what running it costs each month, how customer data is kept apart, how customers export their data, whether another team can pick up the code, and what the handover looks like. Settle these eight points in writing before you sign, and outsourcing a SaaS build is a sound choice for a small team.
| Question | A good answer | A warning sign |
|---|---|---|
| Whose name are the cloud, billing and app store accounts in? | Yours, from day one; the vendor works inside them | “We host it for you” with no plan to move it |
| Who owns the code and the IP? | You do, in writing | Unclear, or the vendor keeps it without saying so |
| What does it cost to run each month? | A list: hosting, services, billing fees | Only the build price |
| How is each customer’s data kept apart? | A clear answer, and tests that check it | “The framework handles it” |
| How do customers export their data? | A planned export, in a standard format | Not in scope |
| Which stack, and why? | A common stack many developers know | A niche tool only this vendor uses |
| What is in the first release? | One narrow version, live in weeks | Everything at once, live in months |
| What do we get at handover? | Repository, setup notes, a walkthrough | “We’ll support it” with nothing written |
The cloud account, the domain, the payment provider and the app store accounts hold your product and your revenue. If they are in the vendor’s name, you can’t switch vendors without their help. Ask for them to be opened in your company’s name, with the vendor working inside them. IPOPBOOKS, a bookkeeping platform we built, went live 10 weeks after kickoff on the client’s own AWS account, not ours.
The contract should say who owns the code, the designs and the IP. There is a legitimate model where you don’t own it, and you should know which one you’re buying. On our SaaS development page we offer both:
If investors will ask who owns the code, pay for the build and own it. If you do switch teams later, our guide to protecting your IP when you change development teams covers the handover.
The build is a one-time cost. Running a SaaS is a monthly one: hosting, email, error tracking, third-party APIs, and billing fees on every payment. Two examples from the vendors’ own pricing pages, read on 30 October 2026:
Using ready-made services like these is usually cheaper than building billing yourself. Ask the vendor for a monthly running-cost list at your expected number of customers, and again at ten times that.
Most SaaS products keep many customers’ data in one shared system and separate it in software. That is normal and cheap to run, but one missing check can show one customer another’s data. Ask how the separation works and how it is tested. When we audit code from other teams, “who can see whose data” is one of the first things we check.
Customers, especially business customers, will ask how they get their data out. In the EU, the Data Act has applied since 12 September 2025 and sets a framework for customers to switch between cloud and data processing services. If you sell to EU businesses, plan a data export into the first versions and ask a lawyer what the Act means for your product. Even outside the EU, an export button answers a common buyer question.
A common stack means you can hire for it and switch vendors. In the Stack Overflow Developer Survey 2026, PostgreSQL was the most common database: 57.9% of respondents had done extensive work with it in the past year. A niche framework or a tool only one vendor knows makes you depend on that vendor. The Daisy’s Guide client owns plain Flutter code that any Flutter developer can pick up.
A long first release is where budgets go. Across 95 agencies, the median published MVP starting price is $13,234, and the median promised timeline is 6 to 12 weeks (Rocketech MVP Price Index 2026, H2 edition). Ask the vendor what the smallest version that a customer would pay for looks like, and how soon it can go live.
Here is an example run of our estimate’s math with sample inputs for a B2B SaaS web app with teams, roles and subscription billing. The inputs are assumptions. Only the arithmetic is ours.
| Item | Result |
|---|---|
| Work items | 11 items in 7 phases |
| Budget | $6,600 to $13,600 |
| Weeks | 5 |
What happens after launch, and when the build pays back, depends mostly on how long customers stay. Our post on the greatest secret of high-growth SaaS companies runs those numbers.
Ask now what you get if you end the contract: the repository with its full history, notes on how to set up and release the product, and a walkthrough. At the end of the Daisy’s Guide project, we walked the client’s technical advisor through the code and the setup.
You can get a free project estimate for your SaaS in about four minutes. It is a planning range, not a fixed quote.
To compare vendors, our comparison of SaaS development companies lists rates, minimum projects and Clutch ratings, with a source for every figure. We wrote it and we’re included.
Whose name the cloud, billing and app store accounts are in, who owns the code and IP, what the product costs to run each month, how customer data is kept apart, how customers export data, which stack and why, what is in the first release, and what the handover includes.
It depends on the contract. In a classic build you pay for, you should own the code, the designs and the accounts. In a vendor-funded model, the vendor keeps the code and the IP and you pay a subscription, which means you can’t sell the product or raise money on it.
It depends on hosting, outside services and billing fees. For example, Stripe Billing on pay-as-you-go charges 0.7% of billing volume, and RevenueCat is free up to $2,500 in monthly tracked revenue, then 1%. Ask your vendor for a monthly list.
With us, a first release typically takes 2 to 4 weeks and costs $5,000 to $15,000. Across 95 agencies, the median promised MVP timeline is 6 to 12 weeks (Rocketech MVP Price Index 2026).
The Data Act has applied since 12 September 2025 and sets a framework for customers to switch between cloud and data processing services. If you sell to EU customers, ask a lawyer how it applies to your product and plan a data export early.
Before you hire a vendor for a SaaS build, settle who owns the code, the cloud accounts and the release process. Those answers decide how hard it is to switch teams later, which is what the Livetag founder had to do. Explore dedicated development team and the Livetag case study.
Review ownership and handover terms for your SaaS
Start with an AI-assisted project brief covering scope, budget, market assumptions and risks. Review its hypotheses before making a commitment.
Carefully curated content for resourceful Devs, CTOs, and PMs. No spam.