Skip to content

Affonso Xavier

Software Engineer · Full Stack

I'm not just a programmer — I'm a problem solver who happens to use code for it.

I build custom systems, from the first sketch to what runs in production — for teams that have outgrown the spreadsheet. I ship solo and fast, orchestrating AI agents, and I work well on a team too.

  • 3→1devs on the team, and delivery sped up instead of stalling
  • 250+daily users on the product I built myself
  • 5→2 daysto ship a new feature, through automation and tests
  • 10+ yearsbuilding for the web, since 2010
  • Open to a role or contract work
  • Remote
  • Manaus, Brazil (UTC−4 — full-day overlap with US Eastern)
  • Full-time, contract or project
Let's talk → See projects ↓

About

I have been building software for over a decade, and for the last three years I have shipped solo products backed by a delivery system I built: I plan, execute with orchestrated AI agents, validate and ship to production — the process, not the size of the team, is what keeps the pace. As technical owner of a critical system at Obliviate, the team shrank from three developers to one and delivery got faster instead of stalling. I also built Tupã on my own, at tupa.dev, and Inner Circle, the evolution of Baú Arcano into a game. The full cases are below.

What I am looking for: shipping end to end, on my own, with a focus on orchestrating AI agents — and I work well on a team when that is what the team needs. That holds for a full-time role just as much as for hiring this kind of delivery as a service.

Projects

Two cases with measured outcomes. What I built, against which problem, and what changed because of it.

  • Tupã

    Personal product · 2025 – present
    Challenge
    Build a product the size of a real system on my own — from the idea to what runs in production — and keep the delivery pace without a team.
    Solution
    A system that serves anyone who needs a solid foundation to run real applications, from start to launch. I designed how it grows so that new needs — databases, cache or connections — can be added without stalling what already works, and each new piece you add saves repetitive work. Delivery is fully automated, with quality verified before every step forward.
    How the process delivered
    The delivery system is what makes a product this size possible without a team: the automated workflow plans, executes, tests and ships, with human review before every merge and continuous measurement of the cycle. Process, not overtime, holds the quality of a product of this scale maintained by one person.
    Outcome
    ~80% less repetitive work creating applications and delivery cycle down from 5 days to 2, with continuous measurement to prove it — not estimate it.

    Bun · TypeScript · Angular · Node.js

    ↗ tupa.dev

  • Inner Circle

    Personal product · Baú Arcano evolving into a game · in progress
    Challenge
    A tabletop RPG community was growing faster than one person had hours for — and the game, once only played in person, needed to happen at a distance, in real time.
    Solution
    I built solo, end to end, the tools that let this community play and create together: collaborative dice tables in real time, name generation, and a shared space where the group contributes and keeps the game’s universe alive. Those tools succeeded on their own — before any graphical layer — and from them is born today the <strong>Inner Circle</strong>: a browser-based RPG playable online, inside a universe the community itself helps create.
    How the process delivered
    A community growing faster than one person demanded process before more hours: a workflow with orchestrated AI agents keeps the evolution advancing at a steady pace, with automated validation before each step forward.
    Outcome
    Reached 250+ daily users and made the press — a solo product with a real community playing and creating together every day.

    Real-time · Multi-user collaboration · Community · Solo + AI

    ↗ Mapinguá Nerd, Feb 2016 — press coverage (Portuguese)
Want this kind of delivery on your team or as a service? Let’s talk →

How one person delivers what a team delivers

It is not talent — it is a system. When I take on a problem, there is a process that guarantees quality, speed and traceability from the first sketch to what is live.

  1. 1 · You define

    The problem in plain business terms, the definition of done and the order. The human decides what matters; no line is written before that.

  2. 2 · The system executes

    Orchestrated AI agents implement against the plan, with tests and mandatory human review before each step forward.

  3. 3 · Validation verifies

    The delivery passes automated tests, speed is measured, and anything that fails is blocked. Green is the only way forward.

  4. 4 · It goes live

    Automated publishing ships what is ready to production, with monitoring of what matters in the real environment.

Monitoring → feedback → back to step 1. Each round feeds the next: the cycle gets shorter and quality rises over time.

How I work

I work in a delivery cycle, from design to shipping — and it adapts to what you need. The first conversation costs nothing and commits you to nothing.

  1. Plan

    I define what needs to be done, the order, and the definition of done before writing a single line — from the business problem to the system boundaries.

  2. Execute

    A delivery system orchestrates the implementation with AI agents, with mandatory human review before every merge. Team quality at the pace of someone who does not wait.

  3. Validate

    Automated tests verify what matters and the cycle is measured continuously — I do not trust gut feeling, and neither should you.

  4. Deliver

    Automated publishing ships what is ready to production, with monitoring of what matters in the real environment, and feedback from live use loops back to the start — each round is faster than the last.

I do not work with a single package. The starting point is what you need to solve first, within what fits right now: we can begin with a small slice that already delivers value, grow in stages as the return shows up, and keep only a monthly support and evolution plan once it is live. A large project and a small one start from the same conversation.

Formatos de contrato

  • Fixed-scope projectScope, timeline and deliverable agreed before anything starts.
  • Part-time allocationSet days per week inside your team, with the process set up by me.
  • Focused consultingArchitecture of a solution, code review, or standing up automation and monitoring.

Send me a message describing the problem in plain business terms — no technical spec, no fixed budget needed. I reply with my read of it, the format that fits, and a possible path in stages.

What people say

  • When the team dropped to one person, I expected delivery to stall. The opposite happened: we started shipping weekly, and I stopped having to watch the process closely.

    Fabio Porto de CarvalhoCEO, Obliviate

Contact

Got a project or a role in mind? Reach out — I reply fast.

© 2026 Affonso Xavier