A custom web platform has no list price. The cost comes from the number of screens, the user roles, the integrations and the platforms it runs on. At Bitnoda the budget ranges run from “under €3,000” to “over €25,000”, and the staged estimate comes after the discovery stage, not before it.

In short, how much does a custom web platform cost?

Our contact form offers five ranges: under €3,000, €3,000–5,000, €5,000–10,000, €10,000–25,000 or over €25,000. They are budget ranges, not project prices. They show roughly where you stand, not what your exact idea costs.

The exact price comes after discovery, the first stage of the work, when the idea turns into a list of features, priorities and costs. We do not quote a figure before we understand the project.

As for time, a presentation website can be ready in a few weeks and a complex platform in a few months.

What pushes the price up: screens, roles, integrations, platforms?

Four things, almost every time:

  • Screens. Every screen is designed, built and tested. Smart Spin, the platform of a table tennis league, has stage sign-up, a ranking, player profiles and an ELO rating that updates with every score entered.
  • Roles. A visitor, a signed-in user and an administrator see different things and are allowed to do different things. On e-voluntar.md, tasks move through a kanban board everyone involved can see.
  • Integrations. Payments, file storage, search, email, AI. Each one brings its own rules and its own errors.
  • Platforms. Web only, or web plus a mobile or desktop app. Every extra platform is one more interface to build and maintain.

What does a marketplace have that a website does not?

A website shows information. A marketplace brings two kinds of people to the same place: those who offer and those who are looking. DriverHub, a car-rental marketplace for Romania, has accounts, listings and search, all in a single Nuxt app.

Photos and files go to separate storage (MinIO), the data sits on Firebase/Firestore and Supabase, and everything runs in Docker containers behind Traefik, on the owner’s own infrastructure. A presentation site has none of these parts. Each one is built, tested and maintained. See also the web platforms page.

How much do online payments and an admin panel add?

Payments are more than a “Pay” button. They are also the declined payment and the refund. At FisherWay, a digital-products shop in Laravel, card payments run through maib. Before launch we test the successful, declined and refunded payment paths.

The admin panel is the part budgets forget most easily. Someone has to add products and see the orders. At FisherWay we built it with Filament, which comes with a panel’s structure ready-made. We wrote about choosing between a custom store and Shopify here.

What changes when the app becomes several services?

Some products stop being one app and become several services talking to each other. Every service is built, deployed and monitored on its own, and that means more work.

A stack of that kind: async APIs in FastAPI, a Nuxt 4 frontend, services linked through NATS, search through MCP and Gemini, all on Kubernetes with ArgoCD. It is the stack of an HR platform with AI search that Ion Rusu, Bitnoda’s founder, worked on for a client under NDA. About that project we name only the stack and the role: development.

When a project needs more people, we work as a development team, with collaborating developers coordinated by the founder.

Fixed budget or iterative work?

Both work. For a well-defined project we set a budget per stage. For a product that changes along the way we work iteratively and revisit priorities regularly. Either way, you follow progress on a staging environment and always know what comes next.

What do you pay after launch?

Three things: hosting, maintenance and new features. Hosting can be on your server, a VPS or in the cloud. Maintenance means monitoring, security updates and backups, at a pace we agree on together.

If you would rather your own team carries on, we hand the project over with all its context. Either way, at the end you get the live product, the source code, the technical documentation and access to the infrastructure.

How do you cut the cost without hurting the product?

Launch a small version first. Pick the features the product makes no sense without, build them well and watch how people use them. The rest comes later, on an architecture designed to grow.

e-voluntar.md started that way: its first version was a bachelor’s thesis, and today it is a public platform.

What is not worth cutting: payment testing and backups. They are cheap at the start and expensive when missing.

What should a quote contain so you can compare it with another?

Two quotes can be compared only if they describe the same thing. Ask every company for the five items below. The other questions to ask before you sign are in our article on how to choose a software development company.

  • The list of features, written in plain language.
  • The estimate split by stage, not a single sum.
  • What is not included: hosting, maintenance, content.
  • Who owns the code, the data and the infrastructure accounts.
  • How you follow progress: a staging environment you can open.

We work the same way with companies in Romania and in Moldova. You will find more answers in the FAQ.