Solutions

Build a SaaS without coding

For founders and domain experts who want to sell software as a subscription without writing code. You describe your product in your own words. Melta builds it, puts it online and operates it: accounts, teams, subscriptions, emails and analytics included.

What a SaaS product from Melta includes

SaaS means your customers use your software in the browser and pay for it monthly or annually. These building blocks are part of every SaaS you build with Melta:

Accounts and sign-up

Users sign up with email and password, confirm their address and reset a forgotten password themselves. Every account has its own data.

Teams and organisations

An account invites colleagues. The data belongs to the team, not to one person.

Roles and permissions

Owner, admin, member, guest: you decide who can see, change and pay for what. New roles come later with a chat message.

Subscriptions with trial

Monthly or annual plans, several tiers, a free trial of 14 days for example. The payment provider charges, your product unlocks the account and locks it again when the subscription ends.

Admin area

You see your customers, their subscriptions and their activity, suspend or extend accounts and follow up on questions yourself.

Emails and analytics

Welcome email, payment confirmation and a reminder before the trial ends are sent from your product. Cookieless analytics show what is used.

How you build a SaaS without coding: the steps

Describe - You explain in your own words who uses your product, which problem it solves and what a subscription should cost. No specification document.
Read the concept - Melta writes a concept in plain language: pages, roles, plan tiers, trial. You change it until it fits.
Confirm - When you confirm, the build starts, paid from the credits of your plan. Melta builds the product; a full build can take up to about a day.
Check the preview - With test accounts and demo data you sign up as a customer, start a trial, take out a test subscription and look at the admin area.
Go live - You decide when your SaaS goes online. Preview and live are separate environments.
Keep improving - From then on every change is a chat message: a new plan tier, a longer trial, an extra feature. Change runs are included in every plan.

What belongs in a first version, and what does not

The most common mistake when starting a SaaS is not too little, but too much. A first version has one question to answer: does anyone pay for this product? Everything else can wait and is added later as a chat message.

Belongs in the first version:

One core feature that solves a concrete problem and can be explained in one sentence.
Sign-up, login and password reset.
A subscription with a trial and a clear price. Two tiers at most.
An admin area where you see who uses your product and who pays.
The emails a customer expects: welcome, payment confirmation, end of trial.
Legal pages that fit your country.

Can wait:

Connections to other tools. Only once paying customers ask for them.
A mobile app on top of the web app. The web product works on the phone.
Many roles with fine-grained permissions. Two roles are almost always enough at the start.
Coupons, discount campaigns, an affiliate programme.
Reports for customers before there is enough data for them.

Unsure what belongs in? The concept is the place to settle it.

Example products: TeamTakt and WabenMeister

TeamTakt is a task tool for teams of 2 to 10 people: tasks with a due date and a responsible person, comments right on the task, a weekly overview at its heart. The classic SaaS pattern: a team creates an account, invites colleagues, everyone works on the same data. TeamTakt runs in preview. See the example product TeamTakt

WabenMeister is an app for hobby beekeepers with 1 to 30 colonies: a digital hive record, reminders for biological deadlines, traceable honey harvests. A specialist application for a clearly defined audience. WabenMeister runs live and shows that a SaaS does not have to be built for everyone to be worth it. See the example product WabenMeister

Both show what it means to build a SaaS without coding. If your product fits one industry rather than a broad market, read on under industry tools.

Operated for you: what Melta takes care of

Building a SaaS without coding is one half. The other half is running it, and at Melta that comes with it:

Hosting - on a melta.ai subdomain or your own domain, bought through Melta or connected.
Payments - one-time payments, subscriptions and checkout are connected. The revenue goes to you.
Email - confirmations, reminders and password links are sent from your product.
Legal pages - imprint, privacy policy and terms are generated from your operator data, ready for Switzerland, Germany and Austria. General information, not legal advice.
Support inbox - requests from your customers are sorted by topic automatically.
Analytics and monitoring - visitor numbers without cookies; errors are monitored and reported to you.

You own what runs.

What it costs

A concept uses only a few credits; afterwards your product runs on a plan per organisation with credits every month. All numbers and how the price is made up are on the pricing page.

Frequently asked questions

Can I build a SaaS without being able to code?

Yes. You describe in your own words who uses your product, which problem it solves and what a subscription costs. Melta turns that into a concept in plain language. After you confirm it, Melta builds the product. You never write code, not even later.

How do subscriptions and the trial work in my SaaS?

Your customers pick a plan, start with a free trial if you offer one and add their card in the checkout. The payment provider charges monthly or annually, your product unlocks the account and locks it again when the subscription ends. Card processing is deducted from each payment and never invoiced separately.

Do I own the product, the customers and the revenue?

Yes. Your SaaS runs under your name, on a melta.ai subdomain or on your own domain. Your customers subscribe with you, the revenue goes to you. You own what runs.

What happens when my SaaS grows?

You write new features, plans or roles as a chat message; change runs are included in every plan. The plan depends on the number of your products and team members.

Describe your SaaS - Melta does the rest.

A concept uses only a few credits. Your product is built, put online and operated once you approve it.

Get early access