Users and access
- Registration, sign-in and account recovery
- User types, roles and permissions
- Account and organisation administration
Digital product and MVP
SaaS development, from idea to product.
We define a useful MVP, its users, data, payments and integrations before overbuilding.
Authorship and reviewJavier Nache
BasisScope criteria and phased development
Last reviewed
How I prepare and review contentWhat SaaS is, without the jargon.
SaaS means software as a service. It is a program usually accessed through a browser and maintained centrally, rather than installing a separate copy for each client.
People sign in to their account, use a set of functions and work with data stored in the product. It may be charged by subscription, by usage or as part of another service. Subscriptions are common, but do not define SaaS on their own.
- Informational website Explains a company, service or content and makes contact easier.
- Web application Lets people complete tasks and manage information in a browser.
- SaaS Offers that application as a service that can be maintained and developed for its users.
When it makes sense to create SaaS.
Technology comes after the problem. A product makes sense when there is a repeated task, an identifiable user and an improvement that can be verified.
Process
A task repeats and consumes time
The product can structure steps, reduce manual work or make the status of each case visible.
Users
Several people need to work with the same information
Accounts, roles and permissions let each person access what they need.
Data
Information must be connected and up to date
A sound data model avoids dependence on isolated files and duplicated tasks.
Service
The tool must grow with clients or teams
SaaS can evolve centrally and provide improvements without reinstalling the product for every user.
Sometimes a website or prototype is enough.
If you only need to explain a service, generate enquiries or test whether interest exists, it is better to start with a smaller solution before taking on the complexity of SaaS.
An MVP is not half a product.
It is the smallest version that lets a real user complete the core task and provides useful information for deciding what to build next.
What defines the scope of SaaS.
Two products with the same number of screens can have very different complexity. Rules, data and connections matter as much as the interface.
Data and rules
- Information stored by the product and how it relates
- Validations, states and permitted actions
- Search, filters, import or export if required
Payments
- Plans, subscriptions or usage-based charging where appropriate
- Trials, plan changes and cancellations
- Billing and payment-provider events
Integrations
- Email, analytics and notifications
- Required APIs or external tools
- Automation and information synchronisation
Operations
- Internal panels for managing the service
- Testing, environments and publication
- Maintenance and evolution after launch
From the problem to a usable first version.
The process aims to reduce uncertainty before adding technical complexity.
Clarify
We define the problem, the user and the core task it must solve.
Prioritise
We separate the MVP from valuable functions that can come later.
Design and build
We turn rules and flows into a coherent interface and technical foundation.
Test and launch
We review primary cases, errors, permissions and behaviour before publication.
Direct collaboration for local or remote products.
I work with you to turn business decisions into a scope that can be designed, quoted and reviewed. If the project is in Vallès Occidental or Barcelona, proximity can make initial sessions easier. Development can also be organised remotely.
Available in Sabadell, Terrassa, Sant Cugat del Vallès, Rubí, Cerdanyola del Vallès and Barcelona, as well as for remote projects. View digital services in Vallès Occidental
Questions about SaaS development.
Is SaaS the same as a website?
No. A website usually presents information and makes contact easier. SaaS lets people sign in, perform tasks, store data and use a service that continues to evolve.
Do I need to define every function first?
No. It is more important to understand the problem, user and main flow. From there, the MVP is prioritised and pending decisions are made clear.
Can the MVP include payments and integrations?
Yes, if they are needed to test the core value. If not, they can be left for a later iteration and the initial scope reduced.
How much does SaaS development cost?
There is no useful figure without defining scope. Users, permissions, data, rules, payments, integrations and maintenance directly change the work required.
Check whether you need a product or a presence.
A well-framed early decision avoids building functions the business does not yet need.
Let's start with the problem, not the features.
Tell me who will use the product and which task it must solve. From there, we can define a realistic MVP and budget.