Skip to main content
GullySystem
A practical guide

Software Development for Startups: What to Build First

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 4 min read

In this guide 7 sections
The short answer

Build one paying customer journey. For most startups that means one customer type, one core action, a way to pay and a plain admin screen for the founders, built well enough to use daily. Write the scope down before coding starts.

One paid customer journey

A first release is the shortest path from a customer’s problem to the moment they get something worth paying for, built well enough to use every day. It is not a shrunken product.

Write that journey as steps. A parent searches for a maths tutor at ten at night, books a trial class for Saturday, pays by card, and gets a WhatsApp reminder on Friday evening.

A feature serving none of those four steps stays out of version one, so the tutor dashboard is a plain booking list until a real tutor asks for more. That is the whole product for now.

What to leave out of version one

Everything below is reasonable later, but in a first release each item adds cost and delays the question that matters most, which is whether people will pay.

Cut each item today, keep the idea on a written later list, and bring it back only when paying customers ask for it more than once. Later is not never.

  • Separate Android and iOS apps
  • Chat, social feeds and referral schemes
  • Detailed admin reports beyond a CSV export
  • Languages the first customers will not use
  • Automation of steps WhatsApp can handle

What to get right even in a small build

A few choices cost little on day one and become painful to change once real customers are inside, so do them properly however small the build is.

Skipping them looks thrifty at first. The bill arrives when a payment is double-counted, an account cannot be recovered or a departing developer takes the only copy of the code.

  • Accounts and login, with OTP if expected
  • Payments confirmed by signed gateway webhook
  • Basic roles for adding staff later
  • Error logs and daily backups
  • Code and cloud accounts in company name

What makes a first release cost more

Cost follows the number of journeys and screens, the kinds of account, and integrations such as payments, maps and SMS, so count them before asking anyone for quotes. Three platforms at launch add real cost.

Published market ranges for an MVP are very wide, because a simple booking flow and a two-sided marketplace both get called an MVP, which makes any single figure misleading. Our MVP cost guide gives sourced figures, each labelled as illustrative market ranges rather than a quote for your build, and none of them replaces a written scope.

Prices are not published here. The first release is written down with you, with what is in and what is out, and the cost follows from that scope.

When not to build yet

Talk to buyers first. Software will not answer whether strangers will pay, and building is an expensive way to avoid asking that question face to face.

A form, a spreadsheet and a payment link can test a surprising number of ideas, and if people use the clumsy version the case for building is made. If nobody bites, you saved the build.

No-code tools suit a first test too, and custom code makes sense once workarounds cost customers or an investor needs to see something you own.

Put the advice to work.

Use a test copy or fictional example to turn the discussion into something your team can check.

What to get right even in a small build

Can the same receipt be allocated without counting the money twice?

Take an unallocated amount in “What to get right even in a small build” and apply it to the intended balance. Review the remaining amount and the original receipt reference together.

Background reading: ERPNext: payment allocation

First-release scope canvas

A one-page canvas with the core customer journey written as steps beside a column of features marked now or later, plus the early foundations and needed integrations. Use it to brief any team.

Open a blank worksheet to print

Questions owners ask

Should a startup build a mobile app or a web app first?

Usually a mobile-friendly web app. One build runs on every phone and updates instantly, so go native first only when the core feature needs the camera, background location or offline use. Start on the web.

Who should own the code if an agency builds our MVP?

Your company, from the first commit. Keep the repository, domain and cloud accounts in the company’s name and add the agency as members, so a handover or a second vendor stays possible later.

Can you help us decide what to cut from version one?

Send a short brief: idea, first customers. The written proposal then separates the first journey from everything that can wait, and lists what is in and what is out for your build.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Discuss Your Requirement