The problem
Customer records and enquiries were scattered across a notebook, a spreadsheet and WhatsApp threads. Floor staff could not see what management had agreed, and customer data circulated with no rule about who was allowed to see what.
Independent developer
When the spreadsheet stops holding up,
I'm Ricardo. I work solo and build custom management systems, mobile apps and websites — from the first sketch to a live server, with maintenance after delivery.
01 Starting point
You're probably here for one of these reasons
None of them start out as technology problems. They are work problems that turned into technology problems.
-
My team runs everything on spreadsheets and information keeps going missing.
Everyone keeps their own copy, nobody knows which version is current, and the history disappears along the way. A proper system fixes that with role-based access and a record of who changed what.
-
I want an app, but the quote I got was out of touch with reality.
A large share of an app budget goes to app stores and paperwork. It can be delivered as an app installed straight from a link, opening like a native app on the phone — with an Android APK when that makes sense.
-
My website is slow, awkward on mobile and invisible on Google.
A company website does not need a heavy platform. Built as static pages, it loads fast, behaves properly on a phone and is ready to be indexed.
-
Someone built my system and then vanished.
This is exactly why I run my own servers. Once delivered, the system still has an owner: backups, certificates, updates, and someone to answer when it breaks.
-
Every week I redo the same task by hand.
Checking a spreadsheet, sending a reminder, generating a report, chasing whoever forgot. These are routines that can run on their own, on schedule, with nobody having to remember.
02 Services
What I build
Always custom. I do not resell off-the-shelf software or charge a monthly fee per user.
01 Custom management systems Lightweight CRM and ERP, for when spreadsheets and WhatsApp no longer hold up.
Customer records, a pipeline for handling enquiries, role-based access, reports, and personal data handled under Brazilian data protection law. Built around the process your business already has, not the other way round.
02 Mobile apps Installed from a link, no app store — plus an Android APK when you need one.
The app installs straight from the browser and becomes an icon on the phone. It works on Android and iPhone, updates itself, and never waits on store approval to ship a change.
03 Company websites Fast, static, with an SSL certificate and ready for search engines.
Static pages served directly by the server: fewer moving parts, faster loading and better performance scores. HTTPS, sharing metadata and sitemap configured from the start.
04 Automation and integrations Routines that run themselves: alerts, reports, bots and system-to-system links.
Automatic alerts by message or email, reports generated on schedule, systems exchanging data with each other, and repetitive work taken off someone’s desk.
05 Hosting and maintenance I run the servers. The system still has an owner after delivery.
Daily automatic backups, a security certificate that renews itself, monitoring, and fixes when something breaks. This is the part that usually goes missing once a project ends.
03 Case study
A CRM for a restaurant
The name was changed at the client’s request. The project is real and live — it is the identification that cannot be published.
What was built
A web system with three access levels, each one seeing only what belongs to its role. Records were designed around data protection rules from day one: consent recorded, personal data kept apart from the rest, and deletion possible on the subject’s request.
Where it stands today
Live, on a server I operate, with daily automatic backups and a certificate that renews itself. When something needs adjusting, the client talks to me directly.
- FastAPI
- SQLite
- Nginx
- Daily backups
- Data protection
04 Other projects
What else has come out of here
Most of my clients work with sensitive information, so names stay out of it. What I can tell you is what was built.
B2B prospecting CRM
For a public speaker
A system to organise the search for companies, log every contact and track where each negotiation stands.
- FastAPI
- SQLite
Patient records and management
For a clinic
Patient records, treatment history and scheduling, with strict access control because it handles health data.
- Web
- Role-based access
AgencyOS
My own product
A management platform for agencies, with an inbox that brings every channel into one place and an AI assistant that triages first contact.
- Next.js
- PostgreSQL
05 How it works
From first contact to a running system
Five stages. You always know which one we are in.
-
First conversation
You tell me how the work happens today and where it jams. No commitment, no charge. If I think I am not the right person for the problem, I say so.
-
Proposal
I write down what will be built, what is out of scope and what it costs. Pricing is per project, set after that conversation — every system is different and a guess helps nobody.
-
Build
You see the system working as it is built, not only at the end. That way changes happen early, while they are still cheap.
-
Launch
I put it live on its own address, with a security certificate and backups configured. A user manual comes with it.
-
Maintenance
The system stays looked after: backups running, certificates renewing, fixes when something breaks, and adjustments as the business changes.
07 Contact
Tell me what the problem is
You do not need a finished project in mind. Describe how the work happens today and where it gets stuck — we design the rest together.
The fastest way to reach me.
Start a chatIf you would rather write at length, or send a document along.
Send an email
I work solo, so the person replying is me.