Category · 35 guides
SaaS & MVPs
For founders and product teams: scoping an MVP, choosing a stack, pricing a SaaS product, GDPR for B2B software and the decisions that come when the first version starts to strain.
Build an internal tool or buy a SaaS subscription?
Subscriptions are cheap in year one and expensive in year five; custom is the reverse. Here is how to compare them honestly and the signs that custom is worth it.
Choosing a SaaS tech stack without regret
Pick boring, well-supported technology by who you can hire, where you can host and what your team already knows. The stacks we would avoid for an MVP, and why.
What does it cost to scale an existing app?
Scaling is rarely one big rebuild. Separate the cloud bill from engineering time, take the cheap wins first and only pay for architecture changes your data says you need.
How to cut your MVP feature list in half
Every feature list doubles between the idea and the brief. Here is a two-hour exercise that halves it again without a fight, by anchoring every decision to one core job.
Enterprise readiness: SSO, audit logs and SLAs
Bigger customers bring bigger checklists. Which enterprise features and documents to build first, based on what actually blocks deals.
EU data residency for SaaS
Swedish public and enterprise buyers will ask where your data lives and who can reach it. Here is how to answer in one document instead of a week of emails.
Funding an MVP in Sweden: Almi, Vinnova and more
A first version costs real money before it earns any. Here is the map of where Swedish founders get it, from customer prepayments to innovation loans and angels, and what each funder expects.
GDPR for SaaS founders
The first enterprise customer will send a security questionnaire before they send a purchase order. Here is what to have ready: the DPA, the sub-processor list, and the logs and deletion routines behind them.
How long does it take to build an MVP?
Weeks, not months, if the scope is held. Here is the phase-by-phase shape of an MVP project, what each phase needs from you, and the five decisions that most often double the timeline.
Is a paid discovery phase worth the money?
A discovery phase sounds like paying for a meeting. Done right, it is paying for the decisions that make the build cheaper and the quote reliable.
Multi-tenant SaaS architecture in plain terms
Every SaaS product has to decide how customers' data lives next to each other. The choice is invisible to users and decisive for security, running cost and the enterprise deals you can sign.
What an MVP costs to build
MVP quotes vary by a factor of ten because scope does. Here are the features that multiply cost, the ones that are nearly free, and how to keep the number under control.
What to prepare before an MVP kickoff
Most MVP delays happen before the first line of code: a missing decision maker, an unowned domain, a store account under review. This is the list that lets the build start on day one.
MVP launch checklist: staging to first users
Before real users arrive: backups, terms, error tracking, a support channel and an invite plan. The checklist for launching an MVP without chaos.
No-code or custom code for your MVP?
No-code is the right first build more often than developers admit, and the wrong one more often than founders hope. A decision checklist built on what you need to learn and what happens after it works.
R&D tax relief for Swedish software startups
Swedish companies with employees doing research and development can reduce their employer contributions. Here is how the deduction works for software teams.
Rebuild or refactor when the MVP stops scaling?
Developers like starting over; businesses rarely survive it. Here is how to decide from where the pain actually is, and the staged route that gets most of a rebuild's benefit at a fraction of its risk.
SaaS pricing models for a first product
Early pricing is a hypothesis you want to be able to change. Pick the model that is simplest to explain, charge in the currency your buyers think in, and get VAT right from day one.
Subscription billing for SaaS with Stripe
Stripe makes the first subscription easy and the hundredth complicated. Here is how to model plans, trials, dunning, VAT and self-service so billing does not become your second product.
SaaS security checklist before the first paying customer
You do not need a security team before your first invoice. You need eleven controls that take days, not months, and one restore test you have actually run.
Owning your code: IP clauses in development contracts
Paying for software does not automatically make it yours. Under Swedish copyright law the developer owns the code unless the contract says otherwise. Here are the clauses that decide it.
Taking over a codebase from a previous developer
When a developer or agency leaves, the risk is not the code itself but the accounts, secrets and knowledge that leave with them. Here is the handover order that keeps you safe.
Technical co-founder, freelancer or agency?
Three ways to get your first version built, each with a different price, a different risk and a different answer to the question of who owns the code and knows how it works.
Two-sided marketplace MVP
Most marketplace MVPs fail on liquidity, not code. Start narrow, do the matching by hand and let a licensed provider handle the money.
Not sure which package fits?
Book a free 15-minute call and we will match your needs to the right package — or tell you honestly if none of them fit.
Free · ~15 minutes · No obligation