Service
Custom systems, CRM and SaaS
I build CRMs, customer portals, internal systems and SaaS, from the database to the screen. When the product serves several companies, each one has its data isolated in the database itself, with row-level security in Postgres. I built a CRM like that on my own, and analyzing each lead became 70% faster over the first 60 days.
Who it is for
Companies whose operation has outgrown what spreadsheets and off-the-shelf tools can handle, and founders who need a web product with login, permissions and billing. It also fits anyone with a half-built system who needs someone to take it to production safely.
Problems it solves
- An off-the-shelf tool that does not fit the process, so the team works around it with spreadsheets.
- A product that serves several companies and cannot let one company's data show up for another.
- An empty screen with no error at all, because the database access rule blocked the query silently.
- A system that passes every test and breaks on the first real payment or the first real customer.
- Login and sessions built in a hurry, with no protection against stolen tokens or too many attempts.
What I deliver
- A complete web system: interface, business rules and a Postgres database.
- Login, role-based permissions and secure sessions, with protection against token reuse and too many attempts.
- Isolation of each company's data with row-level security, when the system serves several companies.
- Billing and subscriptions, when the product charges users, tested with a real payment before it goes live.
- Integration with WhatsApp, email, ERP and the tools the operation already uses.
- Dashboards for the team to follow the operation and the numbers.
How it works
Diagnosis
One conversation to map the process, who uses the system and what hurts today. No cost, no commitment.
A written proposal, in parts, each with a deliverable and acceptance criteria agreed before we start.
Building in weekly deliveries, with the system live early so your team can use it and correct course.
Going live and follow-up
First with a few users, then with everyone, checking what real use shows.
Typical timeline
The proposal gives the timeline for each part, and deliveries are weekly. A complete system is split into phases, agreed after the diagnosis.
Related case
Frequently asked questions
What is a multi-tenant system?
It is a single system that serves several companies, each seeing only its own data. In Postgres, this is enforced in the database itself with row-level security: the access rule lives in the base, not just on the screen. That way, an interface mistake cannot leak one company's data to another.
Have you built a system like this before?
Yes. I was the only developer at a startup and built the company CRM from the database to the screen: multi-tenant, with login, a Kanban pipeline, a WhatsApp inbox and dashboards, in production with active customers. Lead analysis took 70% less time over the first 60 days. The case is right below.
Do I need to replace the system I already use?
Not always. If your current tool does the job, I integrate with it. Replacing it or building a new system only pays off when what exists blocks what the operation needs. I say so plainly in the diagnosis.
How much does it cost and how long does it take?
It depends on the scope. After the diagnosis, which is free, I send a written proposal with the timeline and price of each part, and deliveries are weekly. The code and the database are yours, and I hand everything over at the end.
Let's talk?
The diagnosis is a conversation, free and with no commitment. You leave with the list of processes that eat the most hours of your team.
Talk on WhatsAppOther services
Want this running in your operation?
Tell me in one sentence. I reply with what can be done, how long it takes and what it costs.
Tell me the problem