§ 02 / Apps

Building web applications — SPA, CRM, customer portals.

We build apps people actually use every day. Complex forms, tables with thousands of rows, real-time collaboration, dashboards with live data. Code is written so any developer can open it six months later and immediately see what's going on.

§ 02.1 What we build

→ SPA

Single-Page Applications

Fast, interactive apps: editors, builders, kanban boards, chats. State management without pain, routing, optional offline support.

→ Admin panel

Internal systems

Admin panels, customer accounts, CRM, ERP — the internal tools that should stop wasting your team's time. Roles, permissions, audit logs.

→ Dashboard

Analytics dashboards

Real data in real time: charts, filters, exports. Connections to ClickHouse, BigQuery, Postgres or event streams.

→ SaaS

SaaS products

Multi-tenant apps: billing, subscriptions, organizations, invites, integration APIs, webhooks. From MVP through scale-up.

→ Customer portal

Customer account portals

B2C / B2B portals: orders, documents, payments, support, notifications. Integrates with 1C, AmoCRM, Bitrix24 or your own backend.

→ Portal

Education and HR portals

LMS, onboarding systems, internal knowledge bases. Search, notifications, progress tracking, certificates, roles.

§ 02.2 How the process works

We start from key user journeys — what people do most often and where it currently slows them down.
API and data model are designed first, before the first screen is drawn.
1–2 week sprints. Every sprint ends with a live build in a prod-like environment.
Integration tests on the critical path — so a DB migration doesn't kill Friday afternoon payments.
Error and performance monitoring — Sentry, logs, an incident dashboard.
API documentation and admin runbooks.

§ 02.3 Stack

Frontend: TypeScript, React 19 or Svelte 5. TanStack Query, tRPC, Zustand / Nanostores. CSS Modules or Tailwind — team's choice.

Backend: Node.js (Fastify, Hono), Go, Python — depending on the task and your maintenance team. Postgres, Redis, sometimes ClickHouse.

Auth: Auth.js, WorkOS, Clerk, or in-house — depending on enterprise SSO / LDAP requirements.

Payments and billing: Stripe, YooKassa, CloudPayments, Paddle, Lago for subscription models.

What we avoid: jQuery, Angular 1.x, over-engineered microservice architectures where a modular monolith would do.

§ 02.4 Timeline

Small admin panel

2–3 weeks

CRUD, roles, auth, reports. Internal tool for a team of up to 20 people.

CRM / ERP / portal

4–6 weeks

Multi-role system with integrations, notifications, business logic. Mid-size system for mid-size companies.

SaaS / platform

6+ weeks

MVP of a multi-tenant platform with billing, API and infrastructure. After that — phased growth.

Pricing is always custom — it depends on business-logic complexity, role count and integrations. We'll quote after a short discovery call.

§ 02.5 FAQ

We already have a React app. Can you join our existing team?

Yes — we take on one-off tasks: rewrite a broken module, ship a new flow, pay down technical debt. We work through your git, with PR review. But "permanently sitting inside your team" isn't our model.

Can we skip design?

Yes. For internal tools a component library (Radix, shadcn/ui) plus solid UX is often enough. For customer-facing products — design is worth the investment.

What about tests?

Integration tests on the critical path — mandatory. Unit tests on complex business logic. E2E with Playwright when it's justified. "100% coverage" — no, that's burning budget.

Will it scale under load?

The architecture is built with headroom from day one: stateless servers, queues, caching, horizontal scaling. We run load tests before release if traffic is expected to be significant.

§ — Write to us

Tell us
what we're building.

hi@weiss.help ↗

or via Telegram · phone

First 20-minute call — free. Quote within 24 hours.