We build SaaS apps with customer accounts, access roles, payments and monitoring. React, Node and Postgres or Next.js with your existing CMS; the code goes into your repository.
Four things always included in a Balance IT SaaS package.
Problem brief + personas + scope → quote within 24h with an MVP plan / sprint scope.
Repository on your GitHub from the first commit. No vendor lock-in, no licences. You can switch providers.
We agree on fixes, further development and monitoring in the proposal.
React + Node + Postgres + legacy CMS / Stripe / Sentry. No closed-source vendor lock-in.
Multi-tenancy, RBAC, billing, monitoring, audit log — all need to be built in from the start. Adding them a year later means a full-stack refactor.
Discovery + technology selection (stack + DB schema + auth + billing)
Development in 1-week sprints (a demo each sprint)
Options for monitoring and ongoing development
Or Next.js + legacy CMS. Selected for your use case during discovery.
legacy CMS Auth / NextAuth / Clerk. Multi-tenancy + Row Level Security.
Stripe Billing + Customer Portal + webhooks. Multi-currency support.
Errors + performance + custom events. Slack alerts when a spike occurs.
Choose the pace and scope — with pricing based on the agreed scope. Prices exclude VAT. The amounts shown cover the package scope; additional work requires an agreed scope and a confirmed quote.
Implementation: 6-8 weeks
Delivery: 10-14 weeks
Delivery: tailored to the project
Every project uses a proven open-source stack. No experiments, no vendor lock-in, no closed-source platforms that block scaling.
End-to-end TypeScript. Next.js + tRPC for full-stack, or React + Node + Postgres for a custom backend.
legacy CMS or dedicated Postgres. Row Level Security for multi-tenancy. Versioned migrations (Prisma / Drizzle).
legacy CMS Auth / NextAuth / Clerk. RBAC with a role hierarchy. Optional SSO (Google / Microsoft / Okta).
Stripe Billing + Customer Portal + webhooks + Stripe Tax. Multi-currency, prorated changes and dunning built in.
Realtime updates (notifications, collaborative editing, presence). Subscribed channels per tenant.
Errors + performance traces + custom events. Slack / email alerts when a spike occurs. Database-level audit log.
We review these questions with you before we confirm the scope and deliverables.
Scope and handover
What should a user be able to complete in the first release?
Who is responsible for data, access and integrations?
What acceptance criteria must the working release meet?
How will we hand over code, documentation and agreed support?
The Balance IT standard
A dedicated PM and fast Slack/Teams support.
The agreement sets the price, which revisions are included and how we price additional work.
A bespoke UI component library.
GitHub repo + Postgres dump + environment configuration. You can switch providers at any time.
Each stage has a dedicated team and success metrics. That is how we make SaaS projects as polished as our homepage.
Each stage ends with a demo and approval. Only then do we invoice and move on.
Weeks 1-2 · stack + DB schema + scope
Weeks 3-5 · scaffolding + core
Weeks 6-8 · full scope
Week 9+ · go-live
Loading projects...
Answers to frequently asked questions about Web Apps