Skip to content
Sun Software logo with the tagline Engineering Beyond Code

11 November 2026 · 2 min read

By Sun Software engineering team

Add us as a preferred source on Google

How do you decide what goes into your first release?

MVP feature prioritization starts here: pick one user, one job and one measure of success. Then add the foundations you can’t easily add later.

Cover image for the guide: How do you decide what goes into your first release?

The short answer

Choose one user, one job they need done and one way to tell whether it worked. Build the shortest complete path for that, on foundations you can’t easily add later. Everything else goes on a list for after launch.

Start with one user and one journey

Name the person your first release is for, and the job they will use it to do. Then write out the journey, from sign-up to the moment the job is done.

That journey is your product. If a feature isn’t on it, you don’t need it on day one.

Sort every idea into three lists

  • Must work on day one: the journey itself, signing in, and payment if you charge.
  • Needed soon: what your first customers will ask for within weeks.
  • Later: everything else, including the ideas you are most attached to.

Moving an item down a list doesn’t mean you’ve rejected it. It means it is waiting for evidence.

What should you never cut?

The foundations. Some things are cheap to include at the start and expensive to add later:

  • Sign-in and permissions.
  • A data model, which is how your information is organized, that keeps each customer’s data separate.
  • The billing integration, if you plan to charge.
  • Backups and error logging.
  • A few analytics events, so you can see what people actually do.

Buy before you build

Sign-in, payments, email and file storage are solved problems. Use an established service for each one, and spend your budget on the part that is yours alone.

How will you know it worked?

Write down your measure of success before the build starts. For example: ten customers complete the journey without help.

A release without a measure can’t tell you what to do next.

When does this advice change?

Regulated industries and large enterprise buyers can make extra features compulsory from day one. Two examples are single sign-on, where staff use their company login, and audit logs, a record of who did what.

If your first customer has a security questionnaire, read it before you set the scope.

How can Sun Software help with this?

We plan your first release around one journey and build it on foundations that last. Tell us what you are dealing with. We reply within one business day with our questions and a suggested next step.

FAQs

Questions people ask next

How many features should an MVP have?

There’s no set number. Include what is on the journey from sign-up to the moment the job is done, plus the foundations. If a feature isn’t on that journey, you don’t need it on day one.

What if my first customers ask for a feature I left out?

That’s the evidence you were waiting for. Moving an idea down a list doesn’t mean you rejected it. If your first customers ask for it, move it up.

Do I need to build my own login and payment system?

No. Sign-in, payments, email and file storage are solved problems. Use an established service for each one, and spend your budget on the part that is yours alone.

What if I’m selling to a large company or a regulated industry?

Then your first release may need more. These buyers can make features such as single sign-on and audit logs compulsory from day one. If your first customer has a security questionnaire, read it before you set the scope.

Can Sun Software help me plan my first release?

Yes. We plan your first release around one journey and build it on foundations that last. Tell us who the product is for and what job it does.

Want us to look at your case?

We plan your first release around one journey and build it on foundations that last. Tell us your situation, and we reply within one business day.

  • The first conversation is free
  • NDA before you share anything
  • A reply within one business day