Web platform, customer portal and SaaS development

Web platform and SaaS development covers customer portals, marketplaces, learning, fintech and SaaS products, from spec and architecture to launch, with automated tests, documentation and CI/CD. It is for companies and founders who need their own product, not a brochure site. Prices start at €5,000 and timelines at 60 days, with estimates and payments split into phases.

Who needs a web platform

• You have a product idea but no technical team, and need to know what an MVP will cost and what goes into it.
• Your business has outgrown spreadsheets and off-the-shelf tools: processes are spread across systems that barely integrate. See systems can’t keep up with growth.
• Your customers need a portal: order status, documents, payments and history.
• A previous vendor left code nobody can maintain, or disappeared with the access (see developer dependency).
• The MVP must ship fast, without a rewrite from scratch later.

What we build

• Portals for customers, partners and investors.
• Learning platforms: courses, schedules, tests, internships, support.
• Fintech platforms with calculations, reporting and stricter security requirements.
• Marketplaces and B2B services with roles, moderation and payments.
• Internal systems: admin panels, document workflows, ticketing, reports.
• AI features inside the product: assistants, draft generation, document search.

Process and timeline

An MVP takes from 60 days. Every phase has its own plan, acceptance criteria and deploy, so you see working software rather than progress reports.

1. Discovery. We review the spec or idea, users and roles, integrations and security requirements. The output is a technical solution and a phased estimate.
2. Architecture and prototype. Data model, API and key screens. We agree the MVP scope: what is needed for launch and what moves to later phases.
3. MVP development in short iterations with demos: front end, back end, admin panel, roles and permissions.
4. Integrations: payments, external APIs, e-mail and notifications, AI features.
5. Testing and launch. Automated tests for critical logic, CI/CD, monitoring, backups and TLS.
6. Documentation and growth. Technical docs, a production runbook and the next phases by priority.

How much platform development costs

The price is driven by the number of roles and scenarios, the complexity of business logic and calculations, integrations, security and load requirements, and the number of interfaces (public site, portal, admin, mobile layout). We split the spec into phases with clear acceptance criteria and estimate each one, so you pay for a delivered phase rather than open-ended hours.

How we run the project

We work in iterations with versioned plans and meeting notes. Each phase has its own plan, acceptance criteria and a deploy to a staging environment where you check the result before it reaches production. Database changes go through migrations only, so production updates need no manual fixes. If priorities change, we re-plan the next phase without throwing away finished work.

Stack and infrastructure

Front end: React/Next.js and TypeScript. Back end: Node.js/NestJS, Laravel or Python, depending on the job and who you plan to hire next. Database: PostgreSQL, with schema changes through migrations only. Deployment: Docker, CI/CD, monitoring and backups. For products with several apps we use a monorepo with shared packages so logic is not duplicated between front end and back end.

Examples from our work

• Crypto asset trust management platform: a TypeScript monorepo with a Next.js landing page and investor dashboard, a NestJS back end and a VPN-only admin. One shared fee engine serves both front end and back end, so the website calculator and the server always agree.
• Digital AI university: a React and TypeScript learning platform with courses, schedules, tests, internships, support tickets, an AI assistant and an “Applicants” module; PostgreSQL with migrations, Docker, CI/CD and a runbook.
• Parcel Lead: our own Next.js and PostgreSQL product for finding and qualifying B2B leads.

What to check before choosing a development partner

• A phased estimate with acceptance criteria, not one large figure for a year of work.
• Code and infrastructure in your name: repository, servers, domains and service accounts.
• Automated tests and CI/CD for critical logic such as calculations, payments and permissions.
• Documentation another team could pick up and continue from.
• Security from day one: tenant data isolation, encryption, restricted admin access.
• An honest MVP scope. If everything goes into the “MVP”, launch slips by months.

What you get

• A working product on your server or cloud, with the repository and accounts in your name.
• Automated tests for critical logic, CI/CD and monitoring.
• Technical documentation and a production runbook.
• A phased roadmap with estimates for what comes next.

Getting started

If a previous vendor has vanished and left the project without access, regain control of the domain, servers and code first; the steps are in your web developer disappeared: how to take back your domain, hosting, access and code.

Send us your spec, a description of the idea or access to the current code. We will review it and propose an architecture and a phased estimate. If you inherited the project from another team, we start with a technical audit. Discuss your web platform.