Web App and MVP Development for Business

You need a web app where a website stops being enough: roles, data, calculations, statuses and several people working on one record. An MVP solves a different problem. It tests demand for an idea before a large budget is spent. We start with one main scenario and release a version people can actually use.

When you need it

  • Orders, stock and approvals live in a dozen spreadsheets, and the numbers do not match.
  • Customers ask for their order status in a messenger every day, and managers answer by hand.
  • You have an idea for a service and need to find out whether people will use it and pay for it.
  • A manager assembles a report from several systems and gets the numbers late.
  • An off-the-shelf product covers half of your process, and the team does the rest manually.

What is included

  • Hypothesis

    We write down who the user is, which problem we solve and which metric will confirm the idea. For an internal tool it may be time per operation. For a product it is the share of users who return and pay.

  • Scenarios and release scope

    We sort features into must-haves for the first release and deferred ones. Deferred items go to a backlog that you can see and change after the first data comes in.

  • Interface

    A prototype of the main screens, error states, empty states and the mobile view. Roles and permissions are designed from the start: a director, a manager and a customer see different things.

  • Development

    Back end, database, API and authentication. We pick a stack that another contractor can maintain without rewriting.

  • Integrations

    HubSpot, Pipedrive or Zoho, Stripe and other payment services, email, WhatsApp and Telegram, exports to Google Sheets or Airtable. We read each system's documentation before estimating, because this is where extra time most often hides.

  • PWA and dashboards

    A PWA installs on a phone like an app and updates without app stores. A dashboard shows a manager the numbers that matter on one screen, with data pulled straight from the sources.

  • Launch and reliability

    A staging environment, backups and an error log. Data is hosted in the region your customers and regulations call for, and forms follow GDPR practice where it applies.

Web apps and MVPs, AI automation

Manager's control panel app

An app for a business owner: see where an answer is needed, what waits for approval and whose move is next.

Web apps and MVPs, AI automation

Web app for working with AI

An interface for tasks and chats: search, work states and commands available from the browser.

Web apps and MVPs

Zerno: grain elevator dashboard

A working screen for a grain elevator: grain stocks, storage load and incoming batches side by side.

Web apps and MVPs

Polka: product economics calculator

A calculator for a seller: break down costs and compare price scenarios.

Web apps and MVPs

Reys: dispatch desk for a service team

An internal service for assigning technician visits and seeing the status of every request.

How we work

  1. Process review

    We ask you to show how the work runs today: spreadsheets, chats, screenshots. We find the step where the most time or money is lost.

  2. Spec and prototype

    A short description of the first version and a clickable prototype. Logic errors show up here, long before any code.

  3. Development in short stages

    We show working parts on a test address. You try them on your own data and give feedback as we go.

  4. First users

    We launch to a small group, watch the logs and behavior, and fix whatever stops people from finishing the scenario.

  5. Decision on next steps

    With the data collected, we decide together whether to develop, change or stop. Every one of those outcomes saves money.

What we need from you

  • A description of the process or idea in your own words, even a voice message.
  • Examples of current documents, spreadsheets and reports.
  • Access or documentation for the systems we need to integrate with.
  • A couple of real users willing to try the first version.
  • A person who decides on the feature set.

What you get

  • A working application on your server or cloud account.
  • Source code, database and access, all owned by you.
  • An architecture description and deployment guide for the next developer.
  • A backlog of next features with estimates, plus the first users' data.

Price and timeline

The price covers the whole first version and is fixed before development starts, after we have scoped the task. You pay for the agreed result, and we do not bill by the hour. The more precisely the first release is defined, the lower the estimate: extra roles and integrations are easier to add as a next stage with its own price. We give the timeline together with the cost. Hosting and third-party services are paid by you directly.

Questions

How is an MVP different from a prototype?

A prototype shows how the interface will look and behave, and holds no real data. An MVP already works with real data and real users, it just does only the main thing. A prototype answers whether people understand it. An MVP answers whether they actually need it.

Can we test the idea without development first?

Often yes, and we recommend it. A landing page with a sign-up form, a spreadsheet plus a bot, or manual handling of the first orders can show demand for a small part of the budget. We write code once there are real users behind the idea.

Who owns the code?

We hand over the code and data, and the server and domain are registered to your company. If you change contractors, the new team gets the repository and the documentation.

What have you built in this area?

For ourselves we built a working owner's dashboard: project summary, tasks and approvals on one screen, with reminders. Our portfolio includes a grain elevator dashboard, a product economics calculator and a dispatch tool for a service team.

Discuss a project

Describe the task in the form or email us.