I connect systems and remove manual work before adding new software. The shortest path is not always a new system.
Companies that hired my work
The cause is often the process or the missing integration, not more software.
When someone reaches out, the first question is not "which system do you want?" It is "what is happening in your operation?" The answer is usually one of these steps, and almost never the last.
Develop what is missing
Almost neverDo nothing for now
There is another answer: when the return does not justify the change, I say so. It is cheaper to hear that from me than to discover it six months later.
When the systems work, but the work between them is still done by someone copying data from one place to another.
When a predictable routine consumes time every day, creates repeated work and should not depend on someone remembering to run it.
When what exists leaves a real gap and there is a reason to build or extend it instead of working around it.
Data, dashboards, AI, APIs and WhatsApp fit inside these paths when they make sense. None of them is the starting point.
Companies in SaaS, retail, financial services, real estate, the public sector and e-commerce hired me to build, integrate and evolve systems their operations depended on.
Financial product tied to the card flow of a retail operation with more than 5,000 branches.
I was responsible for the backend, APIs, data modelling, authentication and authorization, integrations and background processing.
existing system → new product + integration
Platform for CRM, real estate management, finance and digital channels, with a base of more than 96,000 registered users, in daily use.
I was responsible for backend evolution, APIs, integrations, asynchronous processing, lead workflows and AI features.
existing system → evolution + integration + automation
Small business operation with repetitive administrative activities and scattered data.
I was responsible for automating manual administrative tasks, with internal tools, APIs and integrations that centralized the data.
Client and sector withheld under a confidentiality agreement.
manual routine → automation
You tell me how the process works today and where it hurts. No sales presentation and no proposal yet.
I identify where the real bottleneck is, what can change and what cannot.
It may make sense to integrate, automate, evolve, develop or do nothing for now. The recommendation comes with the reason.
When there is a project, it is divided into deliveries you can verify along the way, not only at the end.
What happens after delivery is agreed before we start.
Talk about a processThe person who understands the problem writes the code. There is no customer-service layer between the conversation and the execution, and nothing gets lost on the way back.
There is an honest limit to that: this is a small operation. When a project needs more capacity than I have, I say so before we start, not halfway through.
Since 2020, I have worked with companies in SaaS, retail, financial services, real estate, the public sector and e-commerce, building, integrating and evolving the systems their operations relied on.
Based in Maranhão, Brazil. I work remotely.
I write about the decisions that come before the purchase, the ones that become expensive when they are made in a rush.
A set of tools for tasks accounting firms do by hand every week. Free, with no sign-up, processed on your own computer.
See all toolsMissing a weekly check? Tell me which one.
Suggest a toolCommon questions about how I work.
Replacing the ERP is not my starting point. First I evaluate whether the problem can be solved by adjusting the process, configuring what already exists or integrating the current tools. When the problem is between systems, integration avoids the cost and risk of replacing a tool that already works.
Not necessarily. A spreadsheet solves many things well. The problem starts when it becomes a critical part of the operation and nobody dares to touch it, or when the same data exists in three different versions.
That is what I recommend. A small scope shows whether the approach works before you commit a large budget. If it does not, you find out cheaply.
Development is the last step, not the first. Before that come adjusting the process, configuring what already exists, integrating and automating. When one of those solves the problem, it is cheaper and faster.
After understanding the problem, never before. A quote given without a diagnosis is a guess, and guesses fail both sides.
It is agreed before we start: what is included, for how long and what to do when something new appears. Without that, the word "support" becomes an argument.
That risk is real and needs to be handled at the beginning, not the end. Before we start, we define where the code is maintained, what is delivered, what belongs to each party and what another person would need to continue the work.
Minimum necessary access, and no real data leaves your company's environment unless that has been agreed.
I say so. If the expected gain does not justify the change, the recommendation is to leave things as they are for now. Losing a small project is cheaper than delivering something that should not exist.
You do not need to have the problem formulated or know what the solution should be. Describing how it works today is enough for the first conversation.
I usually reply on WhatsApp the same day.
Prefer to write first? Use the contact form. Or Answer five questions and I will say what will probably solve it.
