The real numbers nobody shows you upfront
Most SaaS cost calculators give you fairy tales. They quote "€15K to MVP" then you're six months in, €64K deep, still pre-launch. Here's what building a functioning SaaS actually costs in 2026, measured in cash-out-the-door, not fantasy budgets.
We're comparing three paths to the same finish line: a SaaS with user auth, payments, a functional core feature, basic dashboard, and enough polish that strangers will pay for it. Not enterprise-grade, not handling 50K users yet, but real enough to charge €29-79/month and not embarrass yourself.
The finish line is twelve months from start. That's the timeframe where comparison makes sense—shorter and you're still building, longer and you're into completely different growth problems.
Path 1: Hire a founding engineering team (€220K first year)
You hire two mid-level engineers at European market rates. One full-stack generalist, one with deeper backend/infrastructure experience. You're paying €65K-75K base each, plus taxes, laptop, software licenses, office contribution if they're not fully remote.
Month-by-month breakdown:
- Months 0-1: Recruiting, interviewing, negotiating. You're not paying salary yet but you've probably engaged a recruiter (€8K-12K per hire if you can't source yourself) or you're spending 30 hours/week on it.
- Months 2-4: Onboarding, architecture decisions, first code. €18K/month burn. Progress feels slow because good engineers want to build it right.
- Months 5-8: Core build phase. €18K/month continues. You hit decision paralysis twice, rebuild the data model once, realize the payment provider you picked doesn't do EU VAT properly.
- Months 9-12: Polish, beta testing, first customers. €18K/month. One engineer spends 40% of their time on bugs you didn't predict.
Total cash cost year one: €216K in salary/taxes/equipment, plus €16-24K in recruitment if you used agencies. Round to €220K+ at the low end.
The hidden costs: Your own time managing engineers (20 hrs/week), the three features you cut because they'd take another two months, the technical debt you're already carrying at month twelve because you optimized for speed. Also, you now have two people on payroll before you have revenue. Runway pressure is real.
Upside: You own the codebase completely. Engineers can pivot fast when you discover your first idea was wrong. If this works, you have the team to scale it. Custom everything, no platform limitations.
Downside: Highest cash risk. If you shut down at month eight, you've spent €144K and have a GitHub repo. Recruiting took two months you didn't plan for. The technical choices your engineers made lock you into patterns you'll regret by year two.
Path 2: AI builder + your own labor (€76K including founder salary)
You use Marcus or a comparable AI-assisted builder. You're technical enough to write clear specs and handle basic customization, but you're not a professional developer. You pay yourself a minimal founder salary (€3K/month, €36K/year) because you need to eat and this is full-time work.
Month-by-month breakdown:
- Months 0-1: Learning the platform, building first version of core feature. Marcus Studio plan at €290/month. 60-hour weeks because you're doing everything.
- Months 2-4: Payment integration, user management, first beta users. €290/month platform + €3K/month founder salary. You hire a designer for €2.5K (one-time) to make it not look like a builder template.
- Months 5-8: Iteration based on feedback, adding two secondary features users actually wanted. €290/month + €3K salary. You bring in a part-time developer (€4K total across four months) to build one custom integration Marcus can't handle.
- Months 9-12: Scaling to first 50 customers, support, polish. €290/month + €3K salary. You spend €6K on a proper copywriter and landing page optimization because your conversion rate was embarrassing.
Total cash cost year one: €3,480 platform fees, €36K founder salary, €2.5K design, €4K contract dev, €6K marketing/copy. Total: €51,980. But you should budget €76K to account for the unexpected expenses that always appear (legal for ToS, accountant for first VAT quarter, that API you had to pay for).
The hidden costs: Your sanity. You're learning platform constraints while building a business. Some things take three hours that would take a hired engineer thirty minutes. Other things take you thirty minutes that would take an engineer three days. You don't always know which is which until you're in it.
Upside: You can start today. Lowest cash risk—if you pivot at month six, you've spent €28K, not €108K. You learn every part of your SaaS intimately because you built it. Monthly costs stay low even as you scale to first hundred customers.
Downside: Platform constraints are real. When you need something truly custom, you're either hiring contract help or reconsidering the feature. You're the bottleneck for technical changes. If this succeeds big, you'll rebuild parts of it eventually.
Path 3: Pure offshore freelance team (€20-40K but read the fine print)
You hire developers from markets where €15-25/hour is standard. You find them on Upwork, specify everything carefully, and manage the project yourself. This is the "scrappy bootstrap" path.
Month-by-month breakdown:
- Months 0-2: Writing detailed specs (you must be precise or this falls apart), hiring, first build sprint. €3K-5K. The first developer ghosts after three weeks. You hire a replacement.
- Months 3-5: Core build with second team. €4K-6K. They build what you specified, which turns out to be 60% of what you actually needed. You didn't know to specify the other 40%.
- Months 6-8: Rebuilding the parts that don't work, adding what's missing. €4K-6K. You hire a different developer because the first team is unresponsive. Code handoff is messy.
- Months 9-12: Bug fixes, polish, desperate attempts to make it production-ready. €4K-8K. You bring in a European developer for €6K to audit the codebase. They find security issues and code that will break at scale.
Total cash cost year one: €15K-25K in offshore development, €6K-12K fixing what they built, €3K in platform costs (hosting, services). Budget €24K-40K depending on how lucky you get.
The hidden costs: Your time is the killer. You spend 25 hours/week managing contractors, reviewing code you half-understand, writing specs, debugging miscommunications. Timezone differences mean half your day is async waiting. And the technical debt is invisible until month nine when everything starts breaking.
Upside: Lowest direct cash outlay. If you're extremely detailed in specs and get lucky with contractors, you can get a working product for €20K. You own the code. Works well if you're technical enough to review PRs and catch problems early.
Downside: Quality is a lottery. You'll hire three teams before you find one that's competent. The code you get often works but isn't maintainable. When your first developer disappears, the next one will want to rebuild rather than touch the existing code. Time-to-market is unpredictable—budget twelve months but it might take eighteen.
The costs every path shares (add €8-15K)
Whichever path you pick, budget for these:
- Domain, hosting, services: €1,200-2,400/year (domains, SSL, email hosting, CDN, database hosting, error tracking, analytics)
- Legal and compliance: €2,000-4,000 (ToS/Privacy Policy templates or lawyer review, GDPR compliance audit, business registration depending on country)
- Payment processing: You'll pay 1.4-2.9% + €0.25 per transaction. Stripe is €2K-3K in fees if you process €100K revenue in year one.
- Tools you forgot: €1,500-3,000 (customer support tool, email sending service, the three SaaS products you subscribe to because they save you ten hours/week)
- Accountant: €1,200-2,400 (quarterly VAT filings, year-end accounts, someone who understands SaaS revenue recognition)
These add €8K-15K depending on your entity structure and how much you DIY. They apply regardless of which build path you choose.
Which path fits your situation
Choose hired team if: You've raised funding (€300K+), you're building in a regulated space where custom security matters, or you have deep domain expertise but zero technical ability. Also choose this if your SaaS idea requires real algorithmic innovation—AI builders and offshore teams are bad at novel technical problems.
Choose AI builder if: You're self-funding, technical enough to learn a platform, and building something where 80% of features are standard SaaS patterns (user management, billing, dashboards, forms, workflows). This path makes sense when speed to market and capital efficiency matter more than custom everything. It's the right call for most B2B SaaS that isn't trying to reinvent infrastructure.
Choose offshore freelance if: You're extremely capital-constrained (under €30K total budget), you have strong technical skills to review code and catch issues, and you have time to manage contractors as a half-time job. Only pick this path if you can write specs a junior developer could implement and you're comfortable debugging their work.
The time-versus-money calculation everyone gets wrong
First-time founders optimize for cash cost. That's why offshore freelance looks attractive at €25K. But you're not accounting for opportunity cost.
If the hired team ships at month eight and the offshore path ships at month sixteen, the hired team got eight extra months of revenue and learning. If your SaaS can reach €8K MRR by month twelve with the faster path, you've made back the cost difference. The expensive path was cheaper.
The AI builder path typically ships at month four to six for first sellable version. That's faster than hired team because you're not recruiting, onboarding, or debating architecture. It's much faster than offshore because there's no miscommunication overhead.
Time-to-revenue matters more than build cost when you're pre-product-market-fit. Every month you're not in market is a month you're not learning whether anyone wants this.
What changes in year two
Year one costs are predictable. Year two depends entirely on whether you found product-market-fit.
If you didn't find fit and you're pivoting, the AI builder path wins—you spent €76K total, you can rebuild the new version in six weeks. The hired team path means you spent €220K and now you're paying €18K/month to pivot. Offshore is somewhere in between but the technical debt makes pivoting slower.
If you found fit and you're scaling, costs converge. You'll hire engineers eventually on any path. The question is whether you're hiring to scale something that's working (good problem) or hiring to fix something that's broken (expensive problem).
Marcus customers growing past €15K MRR typically add a part-time developer at month eighteen to twenty-four (€2K-3K/month contract) to handle custom integrations and performance optimization. They stay on Marcus for the core platform because rebuilding working systems is rarely worth it. Total year-two cost: €40K-50K including platform and contract help.
Hired team cost in year two is €220K+ again, plus you're probably hiring a third person. Offshore path usually means you're rebuilding with a European team because the original code wasn't maintainable. Budget €40K-80K to do it properly.
The real decision point
The choice isn't actually about money. It's about what kills your startup if you guess wrong.
Hiring a team when you're pre-revenue means runway pressure kills you before you find fit. You're out of cash at month fourteen, product is 80% done, no customers yet because you spent all your time building instead of selling.
Going offshore when you're non-technical means quality issues kill you. You launch something broken, first customers churn, you spend six months fixing instead of growing.
Using an AI builder when you need deep custom technology means platform limits kill you. You hit a constraint at month eight that requires a full rebuild, losing your speed advantage.
Match the path to your biggest risk. If risk is running out of money, optimize for capital efficiency (AI builder, €76K). If risk is shipping something that doesn't work, optimize for quality control (hired team, €220K). If risk is spending anything at all, accept the management overhead (offshore, €30K plus your sanity).
Most first-time SaaS founders should optimize for capital efficiency and speed. You don't know if this idea works yet. Spending €220K to build the wrong thing beautifully is worse than spending €76K to build the right thing adequately.