Skip to content

Web application and MVP development

We build custom web applications in India for businesses that have outgrown spreadsheets and off-the-shelf software: customer-facing apps, dashboards, portals with logins and roles, and the first working version of a product, an MVP.

The work is split into milestones. Each one ends with something you can use and test, and you approve it before the next begins. A named person on our team reviews every output, and at handover you receive the code, the documentation and the accounts.

Web applications and MVPs
Illustration of web applications and mvps work, with sample content

For example: a customer portal where your customers sign in to check order status and download their invoices.

An illustration of the kind of work we do, not a client project.

How customers check today

Before

Customer: Has my order shipped? Can you resend the invoice?

Order statusLooked up in a spreadsheet
InvoiceFound and emailed by hand

Customer portal

After

Signed in as

Customer

Latest orderShipped
InvoiceDownload

Each customer sees only their own orders.

What web application development includes

  • Scoping before any build

    A written scope: what will be built, what is not included, the risks and what done looks like.

  • UI and UX design

    Screens designed around the people who will use them every day, agreed before they are built.

  • Sign-in, roles and permissions

    Each person sees and does only what their role allows: customers, staff and administrators.

  • Database and APIs

    A data model that fits how your business works, and APIs other systems can use later.

  • Testing at every milestone

    Automated tests and checks with your real data before each milestone is handed over.

  • Deployment and handover

    Deployed to your hosting, with the code, documentation and a runbook in your accounts.

Want this for your business?

Tell us what you need. A founder reads every enquiry and replies with questions or a proposed scope.

Start a project

Not sure yet? Start with a free 30-minute call

Talk it through with a founder first. No obligation.

Free 30-min call

Who it’s for

  • Founders who need a first working version

    An MVP with the few features that prove the idea, built so it can grow if the idea works.

  • Businesses giving customers a portal

    Customers or partners sign in to check orders, download documents or raise requests themselves.

  • Teams that have outgrown off-the-shelf software

    Software built around how your team actually works, instead of working around a tool.

What you get at handover

Everything is handed over in your name, so you can run it, change it or move it to another team.

Handover record Checked by a reviewer
  • The application, deployed to hosting in your name
  • The source code in your own repository
  • Architecture notes: the components and how data moves between them
  • A runbook: how to deploy, roll back and fix common problems
  • Admin accounts and the credential-transfer record
Illustration of a handover record

What we need from you

A project moves fastest when these are ready. We help you put together anything you do not have yet.

  1. 1A clear description of the problem and the people who will use the application
  2. 2Examples of the data it will hold: spreadsheets, forms or exports
  3. 3Access to any system it must connect to
  4. 4One decision-maker who approves each milestone
  5. 5Time from your team to test each milestone

How an engagement runs

  1. Scope document

    Scope: customer portal

    What we deliver

    • Customer sign-in, with roles
    • Order status page
    • Invoice downloads
    Not includedMobile appDone whenTested with your real orders

    Agreed by you before the build starts

  2. This week’s build

    This week’s increment

    Order status page

    Ready to view

    feat: order status page

    test: status for each order type

    docs: how statuses are calculated

    Next increment: invoice downloads

  3. Review checkpoint
    Our reviewer
    • Checked against the scope
    • Tests read and run
    • Ready for you

    Your approval

    Approve milestoneRequest changes
  4. Handover pack

    Code repository

    In your account

    Credentials record

    Transferred to you

    Documentation

    What was built and how

    Runbook

    Deploy, roll back, fix common problems

    Maintenance available on a monthly plan

What affects the cost

We quote after a scoping conversation, so there is no fixed price on the site. These are the factors that move the cost of this work up or down; the proposal states the scope, what is not included and the price.

Technologies we commonly use

  • React and TypeScript
  • Python
  • Document and relational databases
  • REST APIs
  • Cloud hosting in your own account
  • UPI, M-Pesa and regional payment gateways
Number of user roles and screens
A portal with two roles and ten screens is a smaller build than one with five roles.
Integrations with other systems
Payments, CRM, ERP or WhatsApp connections each add work and testing.
Data migration
Moving existing records in from spreadsheets or an old system.
Reports and dashboards
How many reports there are, and how often the data behind them changes.
How soon you need it
A tighter deadline needs more people working in parallel.

Questions

You do, from handover, unless your contract says otherwise. You receive the code, the credentials and the documentation needed to run it.

Tell us what you want to build.

Describe the work. We will scope it with you, or tell you plainly if it is not work we should take on.