I am a custom web app developer. I build SaaS products, custom CRMs, client portals and internal tools with React, Vite, Node.js, Supabase and PostgreSQL. I design the data and the security model first, enforce permissions in the database, and write automated tests as I go, so the app holds up when real users arrive.
Who this is for
- Founders building a SaaS product who need a SaaS developer to take it from spec to working software.
- Businesses outgrowing spreadsheets or off-the-shelf tools that no longer fit how they work.
- Agencies and service firms that need custom CRM development: leads, pipeline, projects, client portal.
- Teams with an existing app that needs new features, better security or a proper test suite.
- Companies looking for a full-stack developer for hire who can own the whole build, not just one layer.
What you get
- Database design. A PostgreSQL data model built for the workflows you described, with migrations under version control.
- Security in the database. Row-level security so each user and each tenant only sees what they are allowed to see, even if front-end code has a bug.
- Roles and permissions. Defined and enforced centrally, not scattered through the interface.
- A React front end. Built with Vite, focused on the screens your users need daily.
- Back-end services. Node.js services and API integrations with the tools you already use.
- Tests. Automated tests for features and, critically, for access control.
- Deployment. Netlify and GitHub, so every change is tracked and deployable.
How I work
I start with the data and the permissions. Who are the users? What can each role see and do? Where does data come from? Getting this right early is far cheaper than retrofitting it.
Then I build in small, working releases. You can log in and use real features early, and we adjust based on what you see. Tests are written alongside features, not left for the end. For multi-tenant apps I write probes that try to read across tenants, and any probe that succeeds is treated as a bug to fix before release.
Everything lives in your GitHub repository: code, migrations and documentation.
Why use a React and Supabase developer for a SaaS build?
Supabase gives you a full PostgreSQL database with authentication and row-level security, and React gives you a fast, maintainable interface. As a React and Supabase developer I can put access rules into the database, where they cannot be bypassed by a front-end bug. You also avoid lock-in: your data sits in standard PostgreSQL. I explain the security approach in Supabase RLS for multi-tenant SaaS.
Why hire me
- I have built a serious multi-tenant system. The RENXW multi-tenant CRM has 86 tables, 32 migrations, 15 system roles, 88 permissions enforced in the database, 834 automated tests, 425 tenant-isolation probes and 16 screens. Features include leads, calls, pipeline, onboarding, projects, website-build tracking, a client portal, reporting, an encrypted credential vault and automation hooks.
- I work on production full-stack code now. At Tech Goes Global (US) I work on a Shopify store with a Node.js backend and a React dashboard.
- I build AI features too. I am lead developer of ALI, an AI assistant using embeddings and retrieval. See AI automation and agents.
What should a first version include?
Most app projects go wrong by trying to build everything at once. A good first version does one core job well for one type of user. For a CRM, for example, that might be leads, follow-ups and a pipeline view, with reporting and a client portal coming later. I help you decide what belongs in version one, build it properly with tests and permissions, and plan the next releases so they fit without rework.
Pricing and timelines
I quote per project after a scoping conversation. What drives cost and time:
- Number of user roles and permissions. More roles mean more rules to design and test.
- Multi-tenancy. Isolating customers properly adds design and testing work, and is not optional for SaaS.
- Integrations. Each outside system adds its own API and edge cases.
- Number of screens and workflows. The core loop first, extras later.
- Test coverage expected. Regulated or sensitive data needs deeper testing.
Bring your idea or your spec. I will help you cut it to a first version worth building, then quote it. Start here.
