Marcus Biel.

SaaS and MVP development

Build and grow your SaaS product

A first release should let a customer finish one worthwhile task. I can help you choose that task, build the product around it and plan what comes next once people start using it.

I’m Marcus Biel. I lead the project and write code. As the founder and developer of Maildroppa, I also know what it takes to keep a SaaS product running as customers and requirements change.

What running Maildroppa brings to your project

I built Maildroppa so small businesses could manage subscribers, send campaigns, and automate email follow-ups in one place.

At launch I have to decide which features people need and how they fit together. In production I see which integrations matter, then work out how to add new features without disrupting existing customers.

I bring those questions to your product from the first design session onward.

The case study looks at those decisions in the context of a live product.

View Maildroppa in detail
Maildroppa / Automation editor A rule in Maildroppa’s automation editor chooses between two follow-up emails in a welcome sequence.
In the automation editor, users determine which email a new contact will receive next.

Where are you starting from?

You have a product idea

You know the problem you want to solve. You still need to decide what to build first.

I start by asking who the product is for and what they should be able to do with it on day one. You get a design that sets out the key features, integrations, and work needed for a first release.

You want to develop an MVP

You want early users to try a working product and show you which parts are worth building out.

I define the scope and build what the first group of users needs. Depending on the product, this includes accounts, data storage, permissions and integrations.

You already have a prototype

A clickable design, a technical prototype or an AI-built first version gives me a starting point for a review. I look at the structure, data model, permissions and integrations, then show you which parts are ready to reuse and what still needs work.

How I review a prototype

You want to extend an existing SaaS product

Customers already use your product. You need new features, system integrations or technical changes.

I review the current product and proposed changes with your team. Together we choose a release that fits your roadmap and the way your developers work.

Discuss the next release

What belongs in the first usable version?

The first step is to identify who needs to use the product and which task they should be able to complete.

That workflow determines what belongs in the first release. I keep track of other ideas and prioritize them for future phases.

Need someone to own the product backlog?

I can join as your product owner. You set the goal and budget, and we agree on the decisions I can make. I prioritize the backlog, work with users to define what each feature needs to do, and decide what ships in the next release.

One decision I faced at Maildroppa was what should happen to subscribers already in an email sequence when someone edits it.

A first release for document approvals

Imagine a product that lets a company get a document signed off.

  1. A company creates a workspace and selects the people involved.
  2. A user submits a document for review.
  3. The assigned reviewers give feedback.
  4. An authorized person approves the document.
  5. Everyone involved can see the current status and the decision.

User accounts, documents, roles and review states need to work together for this workflow.

More detailed reports, other approval processes or further integrations can follow in later releases.

The same approach works for your MVP. Once you’ve picked the customer task that matters most, I can estimate the work and test the release against that task.

What your SaaS product needs

Even a small first release may need accounts, permissions, and a way to manage customers. I identify which pieces your product needs from day one.

  • Users and organizations. How are accounts created? Will several people at one company use the product together?
  • Roles and permissions. Who is allowed to see what information and perform what actions?
  • Onboarding. What does someone need to do between signing up and getting their first result?
  • Subscriptions and billing. How do customers choose a plan, subscribe, and get billed?
  • Administration. What tools will you need to manage accounts and support customers?
  • Integrations. Which external services or existing systems need to be integrated?
  • Deployment and operations. Where will the application run and who will handle the agreed operational tasks?

We’ll decide which of these belong in the first release and which can wait.

Do you already have a prototype?

A design, clickable mock-up or technical prototype can help us work through features and user journeys.

If there’s already code, I assess which parts can be developed further. I look at structure, data models, access and integrations.

An AI-built prototype can be a useful starting point, too. I’ll show you what’s worth keeping and what needs work before customers can rely on it.

From a first release to a running product

  1. 1. Define the product goal and first release

    Who is the first customer, what problem do they have, and how will they use the product to solve it?

    We prioritize features against real workflows and address open questions. Then we agree on the first phase, responsibilities and budget.

    If that’s already clear, I can start building.

  2. 2. Build and review together

    I develop the agreed features and regularly show you the latest working version.

    Try the workflows yourself and tell me what should change. We’ll discuss how each change affects the schedule and what to build next.

    I lead the technical work and write code alongside your developers. I can bring in specialists when the project calls for them.

  3. 3. Prepare for launch

    For the first rollout we agree how to deploy the product, give people access and migrate any existing data.

    I test the agreed features. Before launch, I work with you to line up support, day-to-day operations, and a way for early users to give feedback.

  4. 4. Plan the next release

    After launch, I review customer feedback with you and look for the changes that would make the biggest difference.

    We prioritize features, improvements and technical changes and use them to define the next release.

Discuss your SaaS project

Frequently asked questions about SaaS development

How far along does our idea need to be?

For a first conversation, tell me who the product is for, what problem it solves, and how someone might use it.

If the idea is still taking shape, I can start with a product design. It outlines the main workflows, the features to prioritize, and what to build first.

How much does it cost to develop a SaaS product?

The main factors are the workflows, account types, data, and integrations the product needs. Billing, admin tools, and the infrastructure required to run it also affect the estimate.

Once the scope is clear, you can commission a specific deliverable or a development phase with an agreed budget. The estimate includes the infrastructure, third-party services and support the product will need.

I also estimate the ongoing cost of infrastructure, external services, and any support you need.

Who decides which features to build?

You set the product goals and business priorities. I help define features, identify dependencies and explain what each option would mean.

You can keep those decisions with your team or ask me to take on the product owner role.

Can you work with our existing team?

Yes. I can join your developers and take responsibility for a specific part of the product.

We agree on who owns product decisions, who builds each feature, and who approves a release. I work remotely.

Can you help run and develop the product after launch?

I can continue development and take on agreed operating tasks, or hand the product over to your team or operations partner.

Before launch, we agree on who handles support, operations, and new development.

More about working with me

What’s the next milestone for your product?

Tell me who your product is for, what it does today, and the next thing you’d like a customer to be able to do.

We can work out what belongs in that release and what it would take to build.

Prefer to talk first? Call +49 171 1151013 or message me on LinkedIn.

Discuss your SaaS project