Custom software, web systems and integrations: what I do at AFS IT Services

After twenty-plus years building systems for other people, I decided to build my own. This site is live, and this post opens the blog.

The idea is simple: write about the problems I solve every day — systems that don't talk to each other, spreadsheets that became bottlenecks, technology decisions that keep a business stuck — in language a business owner actually understands. No tech jargon. When a post gets truly technical, I'll say so upfront.

But a first post calls for an introduction. So here it goes.

Where I come from

I started in this field in the early 2000s and, in 2008, co-founded Personalware — a software house I ran for eight years alongside my business partner. We built a vehicle tracking platform, a sales-force solution, custom ERPs. And since the company was ours, I did the whole cycle: proposal, development, rollout, support, the client calling at the end of the day. That's where I learned to look at software with a business owner's eye, not just a programmer's.

In 2016 I joined Spring Mobile Solutions to customize and roll out a sales-force app that field teams from brands like TIM, Unilever, Vigor and Premier Pet used on the street, every single day. That's where the lesson I still carry comes from: good software isn't what looks great in a demo — it's what works in the user's hand, under the sun, on a bad connection, in the middle of a shift.

Then came BNP Paribas, maintaining systems that generated mandatory reports for Brazil's Central Bank, facial biometrics apps for banks and pension funds, and, from 2023 to 2026, Mercado Libre — backend work on a profitability team, in an environment where a system going down means money stops moving across several countries at once. The quality bar you pick up in a place like that doesn't go away.

Now that bar serves companies that don't have (and don't need) an engineering team of their own.

What I deliver

In practice, my work splits into five fronts:

Custom software — management systems and automation for operations still running on spreadsheets and manual controls.
Web systems and platforms — from admin panels to full SaaS products.
Mobile apps — Android and iOS, from concept to the app store.
Integrations — getting your ERP, e-commerce, spreadsheets and apps to exchange data without retyping.
Architecture and consulting — a senior eye for teams that need to decide with confidence.

Across all of them, I handle the full cycle: understand the problem, design the solution, build it, ship it, and stay close after launch. If you've ever bought software and got orphaned at the first maintenance request, you know why that last part matters.

Where AI comes in

Let's be honest here, because the market is full of hype.

I use AI every day, and it genuinely changed my pace: what used to take weeks of coding now takes days. But AI speeds up people who already know the way — it doesn't pick the way for you. The difference between a system that's born fast and solid and a fragile prototype that collapses in its first month isn't the tool. It's the judgment of the person using it.

That's why I insist on the order: first, the methodology I learned at large companies — understand the business, design before building, test for real, measure the result. AI works as an accelerator inside that process, not as a replacement for it. You feel the effect on timeline and budget; the engineering behind it is the same kind that keeps banks and marketplaces running.

What to expect from this blog

I'll write about practical cases: how to tell when a spreadsheet has become a risk, what to ask before commissioning a system, when integrating beats replacing, and what AI can (and still can't) do for your business.

If you run a company where someone consolidates a spreadsheet every Friday, retypes the same order into two systems, or keeps postponing a technology decision for lack of someone to talk it through with — this blog exists exactly for you.

The site is live. The conversation starts now.