João Mateus Scarpa

AI writes the code.Who decides what it should build?

Today anyone can have software built in days. What AI doesn't do is understand your business, choose the right direction and keep speed from turning into a system that is insecure, hard to grow and expensive to maintain. That's where I come in.

The market has changed: writing code got cheap. Deciding what to write did not. AI executing well in the wrong direction only gets you to the wrong place faster, and the bill arrives later as rework, security holes and a system nobody can change.

When it makes sense

Your process lives in a spreadsheet

The operation grew on Excel and manual steps, and you want to turn that knowledge into software without losing what makes it work.

See a similar case →

Nobody understands your system anymore

A critical system went through several vendors, every change feels risky, and you need to decide whether to evolve or rebuild.

See a similar case →

You're about to invest without a technical voice

You have an idea or a budget and AI promises to build it all, but no one senior to say what to build, what not to build, and what it will really cost.

The AI prototype stopped scaling

It worked great at first. Now every change breaks something else, nobody knows whether the data is safe, and you're not sure whether to keep going or start over.

How I work

  1. 01

    Immersion

    Conversations with the people who run, use and decide. Reading the current system, spreadsheets and processes.

  2. 02

    Problem map

    Actors, flows, business rules, and where the real pain is (and what is only a symptom).

  3. 03

    Scope cut

    What goes into the first version, what waits, and what shouldn't be built at all.

  4. 04

    Architecture

    Solution design, integrations, data model, and the reasoning behind each technical choice.

  5. 05

    Delivery plan

    Shippable slices ordered by value, with effort estimates and risks. Ready for any team to execute.

What you walk away with

Formats

1 week

Diagnosis

One important question answered with a clear recommendation: is it worth turning this spreadsheet into software? Where do we start? Can what we have today keep up as we grow?

from R$ 6,000
2 weeksMost complete

Diagnosis & Architecture

From the idea, the spreadsheet or the current system to a complete plan: what to build first, how, how much it costs and how long it takes.

from R$ 15,000

Fixed price. The final amount depends on the size of the problem and is set in our first conversation.

Let's talk about your problem

A 30-minute conversation to understand the context and see whether I can help. No commitment.