Web application development
SaaS, dashboards, internal tools, B2B portals. Modern frontend, robust backend, fast iteration.
Updated
A web application for a specific business job: SaaS, internal tool, customer portal or B2B platform — from prototype to launch and support. Timeline: 14 days. Priced after a short brief.
What's included
- SPA or SSR (Next.js / Nuxt / Astro)
- Node.js or PHP 8 backend
- PostgreSQL + Redis
- Auth, roles, permissions
- Realtime via WebSocket or SSE
- PWA mode: install on iOS/Android
- CI/CD, monitoring, backups
A web application is a product people work in every day: a SaaS, a dashboard, an internal tool or a B2B portal. What matters here isn't the shop window but the logic, the data, the permissions and how the thing behaves under load. We design these applications from the data model to the interface and launch them so the product can grow in iterations instead of being rewritten six months later.
Who it's for
- SaaS founders who need a first version with multi-tenancy, billing and self-service signup.
- Companies running on spreadsheets and email that need an internal tool on their own infrastructure.
- Businesses with partners or B2B customers who need a portal for orders, documents and statuses.
- Teams that need a dashboard showing live data from several sources in one place.
How we work
- Brief and analysis. We go through the task, user roles, key scenarios and data requirements, and decide what belongs in the first version.
- Architecture and data model. We design the data model, API and access rules. This is the foundation everything else rests on.
- Prototype and design system. Key screens and a UI kit, so later sections are built quickly and look consistent.
- Development. Frontend and backend, authentication, roles, integrations and background jobs, in short iterations with a demo at the end of each.
- Testing and monitoring. We check scenarios, load and permissions, and connect logs, metrics and alerts.
- Launch and growth. We deploy through CI/CD, watch how it runs and plan the next iterations.
What you get
- An application built around your process, not a pile of compromises from a ready-made service.
- A well-thought-out data model and API that make adding features straightforward.
- Authentication with passwords, OAuth, 2FA or SSO, plus roles and permissions: each user sees only what they should.
- A fast interface your team actually works in rather than puts up with.
- Realtime updates where they matter: notifications, statuses, live dashboards.
- A documented REST or GraphQL API, if partners or other systems need to connect.
- CI/CD, monitoring, logs and backups, so releases are predictable and failures are visible immediately.
- A PWA mode for installing on a phone, if the product is needed on mobile too.
Technology
Usually Next.js, Nuxt or Astro on the frontend, Node.js or PHP 8 on the backend, PostgreSQL and Redis. But we choose the stack for the task, your team and your hosting, not the other way round. An internal tool can be deployed on your own servers if your security policy requires it.
Timeline and cost
The first working version with the main scenario usually goes live in about 14 days, and the product then develops in iterations. The timeline depends on the complexity of the logic, the number of roles and integrations, load requirements and how clearly the scenarios are described. A clear idea of what goes into version one, and a willingness to cut the secondary stuff, speed things up. Vague requirements and trying to do everything at once slow them down. We start with an MVP on purpose: it delivers value sooner and shows where to take the product next.
Cost is estimated after a short brief. It depends on the complexity of the logic, roles, integrations and load requirements. Along with the estimate we suggest what to put in the first version and what can safely wait.
Example
For example, for a company that tracks its work in spreadsheets and email threads, we would build an internal tool: one database with roles, input forms, task statuses and a dashboard with current figures. The most needed scenario goes live first, say, processing incoming requests, and reports and extra modules follow in later iterations. Data stops getting lost across scattered files, and the manager sees the state of things in one window.
What we need from you
- An understanding of the task and the users. A formal specification isn't required; we structure the requirements together at the brief.
- A product owner on your side who can make decisions about scope.
- Access to the systems we'll integrate with, and sample data if you have it.
If the application is mostly about sales and clients, custom CRM development may be the more precise fit. An application lives longer than its development: load grows, integration APIs change, dependencies get updated. That's what web application and SaaS support is for. On picking the right realtime approach: Realtime: WebSocket vs SSE vs polling.