02UA Services CRM
A multi-tenant CRM where business processes run through a visual, no-code flow builder, with AI that scores leads, routes complaints and drafts emails and SMS.
- React
- NestJS
SaaS Development
SaaS product development from the first release to a multi-tenant platform: accounts and roles, separated customer data, subscription billing and the admin tools to run it.
At a glance
- Discipline
- Software & SaaS
- Typical technology
- TypeScript, Next.js, React
- Related work
- UA Services CRM, Smart Dentist
- First reply
- Within one business day
Our view
The decisions that are expensive to change in a SaaS product are made in its first weeks: how each customer’s data is kept apart, how roles and permissions work, and how plans and billing are enforced. We put tenancy in the data model from day one, use managed services for sign-in and payments rather than building our own, and invest early in automated tests and deployment, so adding a customer, a plan or a feature stays routine work.
What we build
What we build.
Usually a 4–6 week foundation phase, then continuous delivery in two-week sprints.
- 01
Multi-tenant platforms
Each customer organization in its own workspace, with its data kept separate in the data model, not only in the interface.
- 02
Accounts, roles and security
Sign-up, invitations, roles per organization and two-factor sign-in, on a managed authentication service.
- 03
Subscription billing
Plans, checkout, usage limits and webhooks through a payment provider such as Stripe.
- 04
Configurable products
Workflows, fields and templates your customers set up themselves, so the product grows without changes to its core code.
- 05
Admin and usage analytics
Internal screens to manage users and organizations, and reporting on how the product is actually used.
How we deliver
How a project runs.
Discovery and scope
User flows, the jobs the first release must do, and clickable designs of the core screens.
Foundations
Repositories, environments, automated builds and deployments, monitoring, sign-in and tenancy.
Core workflows in sprints
Each job built with its screens, business rules, permissions and tests, and demonstrated every week.
Billing, admin and launch
Plans and payments, the admin screens, then a quiet launch with monitoring in place.
Grow the platform
New features, plans and integrations added in two-week sprints on the same foundations.
What you can count on
- Tenancy designed into the data model
- Managed services for sign-in and payments
- Automated tests and CI/CD from week one
- Code, IP and accounts owned by you
Typical technology
- TypeScript
- Next.js
- React
- NestJS
- Node.js
- PostgreSQL
- Stripe
- AWS
Related work
Products we’ve built.
01Smart Dentist
A practice management and revenue growth platform we designed and built for dental clinics: patients, appointments, insurance claims and daily operations in one place, with AI that surfaces the opportunities a busy practice misses.
- Next.js
- NestJS
- TypeScript
- MySQL
- Prisma
SaaS Development · Questions
Questions, answered.
Something else on your mind? An engineer replies within one business day.
Ask an engineerFor most B2B products, yes: one platform, with each customer’s data kept separate. The separation belongs in the data model from the first release, because retrofitting it later touches most of the code that reads or writes data.
Rarely. Managed services for authentication and payments, such as Stripe for subscriptions, are secure, maintained and quicker to integrate than anything built from scratch. The engineering time is better spent on what makes your product different.
It depends on the number of core workflows and integrations, the platforms you need and how accounts and organizations work. Our MVP cost guide gives planning ranges per building block and a worked example of a B2B web product. After a short discovery we give you a written estimate with the team, timeline and assumptions.
Start a project
Planning a SaaS product? Let’s talk it through.
Tell us what you’re building and where you’re stuck. A senior engineer will reply within one business day with honest questions and a suggested first step.
What happens next
- 01We review your briefAn engineer reads every message and replies within one business day.
- 02Discovery callAbout 30–45 minutes on your goals, constraints and what a good outcome looks like.
- 03Written proposalScope, approach, team, timeline and an estimate. No charge and no obligation.