SaaS (Software as a Service) is a model in which you offer software as a service: the customer pays a subscription and uses it in the browser, with no installation. That is how Slack, Notion and Figma work, but you do not have to aim at the global market. A narrow niche and a problem you know from your own company or from customers are enough.
In Poland there are many such niches: systems for clinics, travel expense settlement, fleet management, schedules for installation crews. What matters is that the problem is recurring and painful enough that someone will pay every month to solve it.
In short
- Start with one problem and one core feature, not a "platform for everything".
- A SaaS MVP has 5 elements: login, a panel with the core feature, roles, billing, a landing page with pricing.
- The subscription model is simple maths: number of customers times price minus running costs.
- The first version will not survive contact with users unchanged, so plan for iterations.
Where to start: the problem and the niche
The best SaaS ideas do not come from brainstorming but from recurring frustration: an Excel spreadsheet that has grown out of hand, manually copying data between systems, yet another email asking “what is the status of the order”. Before you build anything, check three things:
- whether at least a dozen other companies in your industry have the same problem,
- whether they solve it today by hand or with an expensive, bloated system,
- whether they would pay for the solution every month rather than once (ask three such customers directly).
If the idea grows out of a tool that already works in your company, you have an advantage: you know the process and you have your first user. We describe this path in the article from a business card website to SaaS.
What a SaaS MVP must have
An MVP is not a “stripped-down” version but the smallest product someone will pay for. The technical minimum looks like this:
Registration and login
Email and password, optionally login with Google or Microsoft.
A panel with the core feature
One thing the product does better than a spreadsheet.
A role system
Administrator, user, read-only - so that a customer can invite their team.
Billing
Even a single plan with card payment and automatic renewal.
Landing page
A description of the problem, pricing and a start button. Without it nobody will pay.
The rest (reports, integrations, a mobile app, advanced permissions) can wait until the first customers show you what is really missing. We apply similar logic in web applications for businesses.
Stack and multi-tenant architecture
In SaaS projects at Mikamait we usually use a proven set: React with TypeScript on the front end, a Node.js back end (Express, Prisma), a PostgreSQL database, Redis for cache and sessions, and Tailwind CSS for the interface. We handle recurring payments through a payment provider, for example Stripe or Revolut.
The key architectural decision is multi-tenancy: one system serves many customers, and each customer’s data is isolated at the database level. This way you maintain a single version of the application, and a new customer is a new record, not a new installation.
The data isolation rule
The customer identifier should be in every table and every query from day one. Retrofitting isolation into a running system is one of the most expensive fixes in the history of SaaS products.
Got a product idea?
Describe the problem and we will tell you what the smallest MVP looks like
A preliminary estimate of the first version's scope within 24 hours, with no obligation.
Describe your idea+48 731 377 999How long it takes and what it costs
At a traditional agency an MVP usually takes several months. With us the first working version is ready within a few weeks, because we generate the project scaffolding (structure, login, roles, the panel skeleton) with AI tools and spend our time on business logic and testing. We describe the technique in detail in the text on vibecoding.
The cost depends on complexity. We start pricing custom web applications from PLN 8,000 (about EUR 1,900; the current scope is in the price list), and we fix the price before work starts. It is an investment in a product that can earn month after month.
The calculation above is an example, not a forecast. Subtract hosting, payment costs, support and your own time from the revenue, and only then assess how many customers you need to break even.
After launch: first customers and iterations
No idea survives contact with users unchanged. That is why, after launch:
- schedule conversations with the first 5-10 users and watch what they actually do in the panel,
- track three numbers: sign-ups, activation (who performed the core action) and churn,
- fix what blocks payment first, and only then add features.
Do not build too much at the start
The most common mistake is half a year of work on features nobody ordered. It is better to release a simple version and collect feedback than to polish the product in a vacuum.
Financing the deployment
Building a digital product can sometimes be co-financed from public funds. The rules, deadlines and limits change, so check the current call rules before you buy. You will find an overview of programmes in the article on grants for IT and company digitalisation in the region. If you are wondering whether an internal tool or a product for the market is the better choice, also take a look at the page on systems for businesses.
Need help?
Create your own digital product or SaaS
We design and program cloud applications with recurring payments, a customer panel and a database. We reply within 24 hours.
Write to us (reply within 24 h)Call: +48 731 377 999