Insurance, United States
End to end development and integrations at a large US insurance carrier. Large system, strict change process, zero tolerance for regression.
Systems architecture and custom software
Whoever designs the architecture writes the code.
Praeda is the software engineering practice of Savio Batista. Fifteen years building systems that have to stay up, with work delivered across 15 countries and 4 continents. You talk to me on the first call, and I am the one who delivers.
Send me the context in two lines. You get back a first technical read of the problem, at no cost and with no sales pitch.
- 15+
- years building and scaling systems in production
- 15
- countries served, across 4 continents
- 70%+
- p95 latency reduction on a production platform
- 1
- point of contact, from the first call to delivery
Based in São Paulo, UTC-3, with daily overlap with North American and European business hours. Fluent English, used to distributed teams. Meetings and technical documentation in English.
Where this work has run
Every contract I sign has a confidentiality clause, so you will not find a client name or logo on this page. What I can tell you is the industry, the problem and the technical decision, which is exactly what you need to assess me. If we work together, your name will not show up here either.
Part of what follows predates Praeda, incorporated in 2022, and comes from my track record as an engineer. The list has a single criterion: it is work I did myself.
Aviation and air traffic control
Decision support software for the operation, a training simulator, and a flight visualiser built from the raw aircraft signal read over radio. A domain where a software error has physical consequences.
Health insurance
AI assistant for a health plan provider: RAG over the plan document base, Next.js and React on the interface, Python and FastAPI on the backend, containerised, with 100% test coverage.
Why this way: in healthcare, a made up answer is not an interface defect, it is regulatory risk. The model only answers from the plan documents, and every answer can be traced back to its source. The 100% coverage follows the same logic: here the cost of being wrong is higher than the cost of testing.
Gym network, multi-site operation
Orchestration layer built from scratch to connect the systems across the network. Serverless on AWS: Lambda, DynamoDB, API Gateway, Cognito, infrastructure as code and continuous delivery from day one.
Why this way: gym network traffic has predictable peaks and long idle hours. Paying per request instead of keeping a server up 24 hours is the right call for that usage profile. And with infrastructure described as code, the whole environment comes back up with one command, without anyone having to remember how it was assembled.
AI-powered advertising
Backend architecture for an AI-driven advertising platform, sized to grow in volume without rewriting the foundation.
Manufacturing and industrial safety
Data pipelines feeding the monitoring portal for equipment used in the field.
Recurring stack: TypeScript, Node.js, Python, FastAPI, PostgreSQL, Next.js, React and AWS (Lambda, DynamoDB, ECS/EKS, API Gateway).
The client name is missing and it will stay missing. What I can do is sign a mutual NDA and walk you through the architecture diagrams and the technical decisions on a call.
When it makes sense to call me
The conversation usually starts one of three ways. The system that carries the operation is slow and nobody can say why. There is an expensive architecture decision on the table and no senior engineer in house to make it. Or the process the company sells runs on a spreadsheet and needs to become software.
Architecture and technical decisions
I survey what already exists, design the target architecture and write the execution plan that fits the budget and the team you actually have. It works both to decide before spending and to unblock what is already stuck.
- Architecture and performance review
- Cloud and legacy modernisation
- Stack selection and second technical opinion
Custom build
From the first prototype to the system in production with people using it. Written for your process, not the other way around.
- Web applications, APIs and integrations
- Data platforms and large volume migrations
- AI features: assistants, RAG and automation
I am not the right choice for a brochure website, for an off the shelf software licence, or for the cheapest quote on the list.
WhatsApp and Instagram
Integrations with Meta's business platform
A specific service line: connecting the systems your company already runs to its own WhatsApp Business and Instagram professional accounts, through the WhatsApp Business Platform and the Instagram Messaging API. Customer service with history, transactional notifications, booking and automation, all inside the system where the data already lives.
What the integration does
- Receives end-customer messages and puts them inside your company's system
- Sends replies, media and approved message templates to people who opted in
- Wires the conversation into the CRM, ERP, calendar or internal system that owns the process
- Monitors delivery, failures and number quality once it is live
Who owns the account
- The business portfolio, the WhatsApp Business account and the phone number stay in your company's name
- I act as the technical provider on its behalf, with access it grants and can revoke
- Conversation data stays in your company's infrastructure, with the retention it defines
- No data selling, no cross-client use, no bulk messaging to purchased lists
How you engage
Three formats, each with duration and deliverable defined before we start.
-
Architecture assessment
One to two weeks, fixed price. You walk away with a document: what exists today, the risks in order of severity, the target architecture and an execution plan with estimates. The document is yours, including if you decide to execute it with someone else.
-
Fixed-scope project
Scope, architecture and price defined in writing before the first line of code, with payment per delivered milestone. Short delivery cycles, with the system live early.
-
Monthly senior seat
Fixed days per week inside your team, for an agreed period. This is the most common format with clients outside Brazil.
I do not sell hours. I sell fixed scope or an agreed period.
One person. And that is the product.
Praeda is a one person company, and that is a choice, not a stage. In fifteen years serving clients in fifteen countries, what delayed projects was never a shortage of people. It was the broken telephone between whoever sells, whoever manages and whoever writes the code.
That chain does not exist here. You explain the problem once, to the person who is going to solve it, and you get the technical answer from that same person. No part of the work is handed down to someone cheaper after the contract is signed.
The trade-off is honest: I take on few projects at a time. If your window does not fit mine, I will say so on the first call instead of accepting and running late.
What if I become unavailable
You should ask this before signing, and the answer is not a promise: it is how I set the project up from day one.
- The code lives in your company's repository. You follow it from the first commit, not at delivery.
- The infrastructure runs in your company's cloud account, under your provider contract and your credentials.
- No manual deployments from my machine. Build and deploy go through a pipeline any engineer can run without me.
- Architecture documentation delivered with the system, not promised for later.
If I disappear tomorrow, your system keeps running and another senior engineer picks up what is live without archaeology. A system only I can maintain is a badly built system.
Savio Batista Staff Software Engineer and architect Full track record, with companies and dates, on LinkedIn
What everyone asks before we start
Can I talk to one of your clients?
No. Every contract I sign has a confidentiality clause, and yours will too. That same rule is what protects your name. Instead of a reference call, I sign a mutual NDA and walk you through the architecture diagrams and technical decisions from projects similar to yours.
How much does a project cost?
There is no price list for custom software. The first deliverable is always scope, architecture and estimates in writing, with a fixed price per milestone. Only after that does a development contract exist.
Do you replace my engineering team?
No. I work alongside the team you already have and leave the system documented so they can run it without me.
How does working across time zones and borders actually work?
Remote by default, and most of my clients are outside Brazil. Based in São Paulo, UTC-3, with daily overlap with North American and European business hours. Meetings and technical documentation in English. The contract is with Praeda Ltda, a registered Brazilian company, invoicing international clients directly.
Tell me the problem
Write two lines about what you need to solve. I reply with a first technical read and a suggestion of where to start, with no commitment and no commercial proposal at that stage. If it is not the kind of work I do well, I will say so and point you to someone else.
It helps to include: the problem in one sentence, the system or process involved, the timeline you have in mind and the budget range you expect.
Praeda Ltda is a registered Brazilian company (CNPJ 48.145.792/0001-19), invoicing international clients directly from São Paulo.