QUICK SOLUTIONS AI

How we work

A method that is written down, measured and open.

From the first conversation to every monthly delivery, everything follows a process you can follow: AI-led requirements gathering, a monthly cycle, hours measured from Git with a public ruler, and code that stays with you.

Getting started

The first steps cost nothing.

FreeNo commitment up to here
  1. 1

    Conversation

    One meeting for you to see the method and for us to understand the operation.

  2. 2

    You pick the pain

    Together we choose the problem most worth solving first.

  3. 3

    Requirements gathering

    With Ideia Estruturada, the AI interviews you across seven layers and produces a technical scope, before any quote.

    Ideia Estruturada
  4. 4

    Proposal

    Scope, success metric and cost, end to end.

Who's behind it

Quick Solutions AI is led by Marcelo Oliveira: over 35 years in technology, a degree in Computer Science and a specialisation in Data Science. The person you talk to is the person who builds.

Meet the team

How we work

One cycle a month, with you at the table.

AI proposes. People decide.

1 cycleper month01020304

What we learn goes back into the queue.

  1. 1

    Prioritise

    You pick the next pain point from the backlog. We tell you what it costs and how we'll measure it.

  2. 2

    Build

    Short deliveries, live early, on the same secure foundation.

  3. 3

    Measure

    Against the yardstick agreed upfront: time, cost, errors or conversion.

  4. 4

    Show

    At the monthly meeting: what changed, what it cost and what comes next.

How we measure hours

Every hour points to a commit.

Hours don't come from a spreadsheet or from memory. The Hours Radar reads the Git history (date, author and the description of each change) and applies a ruler that is written down, public and agreed before any billing. Any hour can be checked in the repository, line by line.

Excluded: merges, commits duplicated by rebase and commits from outside the team. And only product work is billed: documentation and the measurement itself are measured, shown in the report and left out of the bill.

How we count hours

Imagine we write in a notebook every time we finish a small piece of work. By counting the time between notes, we find out how many hours we worked. No guessing and no spreadsheet.

The note in the notebook

Each time the programmer finishes a step, they press "save". The day, the time, who did it and what changed are recorded. That record is called a commit. Nothing is erased.

Counting time between notes

A robot reads the notebook and looks at the time of each note. If one was at 9:00 and the next at 9:25, that is 25 minutes of work.

The five rules, like a game

  1. 1Notes close together · up to 40 minIf two notes are 25 minutes apart, we count 25. If they are far apart, like over lunch, we count only 40 minutes. You never pay for the coffee break.
  2. 2Setting up the desk · 45 minBefore we start drawing, we set up the desk: read what changed, open the system, test things. We count 45 minutes a day for that.
  3. 3The first note · 15 minThe day's first note has no earlier one to compare with. It gets a fixed 15 minutes.
  4. 4A little extra · +10%Talking with you and checking a colleague's work is also work, but it does not become a note. So we add 10%.
  5. 5Never more than 12 hours · 12 hNobody works more than 12 hours in a day. That is the most we count.

One day, in practice

Six notes through the day. Notice lunch: we went 2h45 without writing anything, and only 40 minutes count.

  • 09:00 → 09:2525 min
  • 09:25 → 09:5530 min
  • 09:55 → 12:40 (lunch: only 40 count)40 min
  • 12:40 → 13:1535 min
  • 13:15 → 13:3520 min
  • Setting up the desk45 min
  • First note of the day15 min
  • A little extra (10%)21 min
Hours for the day3h51

What we do not bill

Repeated copies and notes from people outside the team do not count. The paperwork (documentation) and the measuring itself are not billed either.

How you check it

Every hour has a note that proves it. The notebook is yours and you can open it whenever you like. And the monthly fee never goes beyond the agreed hours.

The ruler, in five lines

  1. up to 40 minTime between commitsEach gap between two commits by the same person counts at its real length, up to 40 minutes. A long break never turns into billing.
  2. 45 minDaily warm-upOnce per working day, per person: reading the context, setting up, running the tests before changing anything.
  3. 15 minFirst-commit floorThe day's first commit closes no gap, so it gets a fixed floor.
  4. +10%AllowanceOn top of the total, for reviews and conversations that don't become commits.
  5. 12 hDaily capNo one logs more than 12 hours in a day, allowance included.

One day, by the rule

  • Time between commits
  • Daily warm-up
  • First-commit floor
  • Long break: only 40 min count

150 min

between commits

+

45 min

warm-up

+

15 min

floor

+

21 min

10% buffer

=

3h51

that day

Illustrative example of one person's working day.

On a recent project

88h10

measured across 487 commits, in two weeks

Real time between commits
66h09 · 75%
Daily warm-up
10h30 · 12%
10% allowance
8h01 · 9%
First-commit floor
3h30 · 4%

Of these, 25h16 of documentation and measurement were measured and not billed.

The monthly fee

You buy hours. You never pay beyond them.

We agree on a number of hours per month, for example 40 h. That is the base of the monthly fee, and every hour can be audited in Git. It does not mean we will only work 40 hours: it depends on demand and need. Anything beyond the agreed amount becomes a running account, paid over the following months, no problem.

  1. 1

    You pick the hours

    For example, 40 hours a month. That number is the base of the monthly fee.

  2. 2

    We guarantee the effort

    We commit to dedicating that many hours to your project, every month.

  3. 3

    We measure it in Git

    Every hour is measured by the public ruler and can be checked in the repository.

  4. 4

    You pay for what was done, up to the cap

    If we did less than contracted, you pay only for what was done. If we did more, the excess waits in the queue for the following months.

Two examples with 40 hours contracted

A low-demand month

We did less than contracted: you pay only for the hours done.

  • Hours worked
  • Hours paid in the month

You pay: 25h + 30h + 20h · total 75h

A high-demand month

We did 90 hours at once. You pay 40 in the first month, 40 in the second and 10 in the third, never going over the cap.

  • Hours worked
  • Hours paid in the month

You pay: 40h + 40h + 10h · total 90h

You know what you will spend, month by month

Because billing never goes beyond the contracted number of hours, each month's maximum is known before it starts. No surprises on the invoice.

The contracted hours are our commitment

Contracted 20 hours? That is the effort we guarantee. If the company wants more features, they take longer to be ready, or the contracted hours go up.

No lock-in

You can leave whenever you want. And take everything.

Lock-in is when the client is stuck with the vendor: the code is not theirs, cancelling is expensive and switching companies means starting over. Here it is the opposite.

What is yours from day one

  • Source codeLives in your company's repository
  • InfrastructureThe system's servers and database
  • DocumentationManuals, rules and recorded decisions

What if you decide to leave?

  1. 1

    You tell us

    No penalty and no minimum contract term.

  2. 2

    We hand it all over

    Code, infrastructure and documentation are already yours.

  3. 3

    Settle the queue, if any

    Only what was already done and not yet paid, as agreed in the document.

  4. 4

    Done

    You carry on with whoever you like, without starting over.

Lock-in vs. how we work

With lock-in (what we do not do)

  • The code stays with the vendor
  • Penalty to cancel
  • Minimum contract term
  • Switching companies means starting over

No lock-in (how we work)

  • The code is yours from day 1
  • No penalty
  • No minimum term
  • You take everything and carry on with whoever you like
A cap that holds
The month's billing never goes beyond the contracted hours.
Fewer hours, you pay less
If we did less than contracted, you pay only for what was done.
Excess in the queue, in writing
Whatever goes over the cap is paid in the following months, always within the same cap. The company takes on that queue in a document, committing to pay until it is settled.

What comes with it

Each project starts further ahead than the last.

Each new agent inherits what was already solved in the previous ones. You don't pay twice for security, logging and integration.

Effort per project

  1. A

    Project A

    Starts from scratch and builds the base

  2. B

    Project B

    Inherits the base, born with security, logging and WhatsApp

  3. C

    Project C

    yours

    Inherits the base and what A and B learned

  • Inherited from the foundation
  • New work for the project

Quick foundation: what the next product inherits

  • Personal data pseudonymised before it reaches the AI
  • Every AI call logged: what went in, what came out and what it cost
  • Agents with approved versions; nothing changes without you knowing
  • Data hosted in Brazil
  • WhatsApp integrated from day one

Learning that compounds

Every product gives back to the foundation what it learned: benchmarks, rules and already-calibrated agents. The next one does not start from scratch; it starts from what the others already learned.

Commercial model

A monthly fee, not one project at a time.

Fixed monthly fee
Predictable for your budget, with no new proposal for every idea.
Auditable hours
Every hour tied to a commit and a delivery. You see what you paid for.
Excess waits in the queue
Whatever goes beyond the contracted hours is paid in the following months, always within the cap.
No lock-in
Code, infrastructure and documentation are yours. If you leave, you take everything.

Prefer to pay for results?

We work that way too: no upfront payment during the build, and you pay once the agreed KPI is validated.

Which process in your company would you like to stop doing by hand?

Tell us in one message. We'll reply with a scheduled conversation, not a generic deck.

Book a callMessage us on WhatsApp