01
Agentic AI engineering
Agents running fronts in parallel — code, tests, review, documentation — under my specification and my review. The volume that used to need a team became orchestration.
Donizeti Ferreira · software engineer
One person in place of an
I'm Donizeti Ferreira. For a flat monthly fee I take over your company's engineering: I build what's missing, automate what's manual, keep what already runs from breaking, and own the day-to-day. Not an agency, not project freelancing — one person, under contract, inside your operation.
Talk to me on WhatsAppYou get me,
not an account manager
See what the monthly retainer covers not an account manager
- 1
- person, no middleman
- 24h
- to the first reply
- 30d
- to end it, no penalty
- Who you talk to
- Donizeti Ferreira, directly
- Model
- Monthly retainer, flat fee
- Rating
- 4.81 across 22 reviews · Workana
- Company
- D7BOTS · Reg. 56.659.342/0001-72
How this is possible
How one person does
the work that
used to need a team.
The honest answer isn't that I work like ten people. It's that the part which took ten became machine — and what's left is exactly the part no machine does.
02
Automated pipeline
Automated tests, continuous integration and delivery, a staging environment and rollback ready. Ship several times a week without taking down what was standing.
03
No management layer
There's no product owner, agile master or account manager in the way. What an agency spends on alignment meetings is execution time here.
04
What I don't delegate
Judgement: what to build, what isn't worth it, where the process will break, and when the right answer is not to do it. No machine decides that — which is why there's still a person here.
Software isn't just writing it.
It's staying up afterwards.
Every change goes through the same pipeline before it reaches your customer. That's what makes it safe to ship several times a week without breaking what already worked.
Drag to see the whole pipeline
The bind
Technology is
a monthly demand.
Hiring isn't.
- 01
Hiring a developer is slow, costly and risky
Salary, payroll taxes, benefits and the risk of hiring wrong — for demand that swings from month to month.
- 02
Agencies bill by the hour and by the head
You pay for a product owner, an agile master and an account manager just to reach the developer. And every new request reopens the negotiation.
- 03
The improvement queue never moves
The "when there's time" list grows every month. With nobody accountable for it, it doesn't move — it just ages along with the system.
What stays with me
It isn't only development.
It's everything that needs
someone to own it.
Six fronts, one standard: understand the process as it actually happens, solve it so it runs unattended, and make failure visible when it comes.
01Software developmentA web system, dashboard or internal tool built for your process — not for the market's average process.Details02Process automationTaking off your hands the repetitive work that today depends on someone remembering to do it.Details03Integrations and APIsMaking two systems that were never meant to talk exchange data reliably.Details04Applied AIA language model solving a defined task, with a verifiable result — not a generic chatbot.Details05Maintenance and productionKeeping alive what already runs — including the system I didn't write.Details06Running the day-to-dayNot every demand becomes code. A routine that needs an owner and a technical decision that needs a second opinion are mine too.Details
The monthly retainer
What you get
every month.
A flat monthly fee, one accountable person and a work queue agreed with you. That's what the retainer covers — and what it doesn't.
Included in the flat fee
- Development, automation, integrations, bots and AI agents, in the priority order we agree on
- Maintenance of what already runs: fixes, tests, releases and monitoring — including code I didn't write
- A queue agreed at the start of each month, with visible progress and a review of what shipped at the end
- Running the day-to-day: routines that need an owner, vendors that need chasing, a technical second opinion
- Direct contact with me, no account manager in between
It's neither unlimited demand nor a package of hours: capacity, pace and limits are agreed upfront.
The terms
- How it starts
- A trial month, no penalty and no lock-in. If it doesn't make sense, it ends.
- How it ends
- 30 days' notice, from either side. Nothing is held hostage by a contract.
- What's yours
- All code in your repository and credentials in your vault, from day one.
- A small client list
- I work with a small number of clients at a time. That's what makes fast replies possible.
FeeFlat per month, set from your company's budget.
Tell me what you need each monthReply within 24h, from me
How the price is set
I don't send
A proposal is a document a vendor writes to justify a price they already picked. Here it works the other way around.
01
You tell me the need
On WhatsApp, however it comes out. No finished scope or document required: describing the problem is enough for me to size it.
02
You tell me the budget
What your company can invest per month. Saying the number first doesn't make you pay more: it makes the conversation take a day instead of three weeks.
03
I tell you what fits inside it
Which fronts I cover at that level, at what pace, and what stays out. If nothing worthwhile fits, I say so right away — at no cost.
Tell me what you need
One-off projects with a fixed scope are possible too — but for recurring demand they usually cost more, because you pay to reopen the negotiation on every request. There's a floor for the contract to pay for itself.
Compared with the alternatives
The three ways to solve this.
| Criterion | Hiring in-house | Agency or squad | With me · monthly |
|---|---|---|---|
| Monthly cost | Hiring in-houseSalary + taxes + benefits | Agency or squadHours × heads, with margin on top | With me · monthlyFlat fee, set from your budget |
| Who does the work | Hiring in-houseThe person you interviewed | Agency or squadWhoever is free on the bench | With me · monthlyMe — the same person from the first call |
| Time to start | Hiring in-houseWeeks of hiring process | Agency or squadProposal, approval and kickoff | With me · monthlyThe first week already produces |
| If demand drops | Hiring in-houseYou pay the same, with idle time | Agency or squadYou don't call and the system ages | With me · monthlyThe month turns into maintenance and improvement |
| Maintenance after | Hiring in-houseCovered, while the person stays | Agency or squadA separate support contract | With me · monthlyInside the contract, always |
| If it goes wrong | Hiring in-houseTermination, cost and rehiring | Agency or squadA project delivered half-done | With me · monthly30 days' notice and the code is yours |
An honest comparison: hiring in-house makes sense when the demand fills someone's week, every week. An agency makes sense when the volume needs several people in parallel. Between those two is where I'm the cheaper answer.
Tell me what you needAnswer within 24h, and it's me answering
A typical month
What happens between one invoice and the next.
No week is only meetings, and none is only code. Keeping what already exists alive is inside the contract — the part one-off projects leave orphaned. The front that carries most of this is maintenance and production — it's what separates a continuous contract from a one-off project.
BuildingKeeping alive
- Week 1
Priority set
- Agreeing what goes into the month
- First front already in development
- Week 2
Building
- Development of the main front
- Adjustments the operation asked for along the way
- Week 3
In production
- What's ready goes live
- Watching the first days closely
- Week 4
Maintenance and review
- Reviewing the month's alerts and failures
- What didn't fit opens the next month
Proof
My code
running without me.
In a continuous contract the question isn't whether I deliver — it's whether what I deliver stays up on its own. No client is named here, because none agreed to be a showcase. What's below is what anyone can verify without taking my word for it.
Client reviews, on the platformHERO4.81across 22 client reviews- Projects delivered
- 20
- Violations
- 0
- Clients who came back
- 42026-10-04
- IT rank in Brazil
- #196
Work you can check yourself
Case 01 · open source
forecast-calibration-kit
A TypeScript library that scores the quality of probabilistic forecasts, published as open source and as an npm package, with 98% test coverage declared in the repository.
- What you can check
- Code, documentation, input validation, tests and usage examples, including the command line for JSON data.
- On a retainer
- It's how I treat an automation on a retainer: well-defined inputs, verifiable behavior and maintenance.
What it doesn't prove. My own product. It isn't a client deployment, nor proof of savings at a company.
Case 02 · published product
Praxis Index Trend
A software product for MetaTrader 5, with its own presentation page and a public listing on the MQL5 Market.
- What you can check
- Description, requirements, parameters and usage limits, plus the Strategy Tester demo the platform provides.
- On a retainer
- Publishing a product means explaining how it works, how to test it and under which conditions it runs. That's the discipline I bring to automations and integrations.
What it doesn't prove. Engineering of my own product. No financial results or investment advice offered.
Case 03 · software portfolio
D7 EA Portfolio
My own portfolio of EAs for MetaTrader 5, combined in a single Expert Advisor.
- What you can check
- Portfolio composition, installation requirements and usage limits in the public presentation.
- On a retainer
- Integrating components means taking care of compatibility, configuration and operation. It's the same care I bring to a company's integrations.
What it doesn't prove. Engineering of my own product. No financial results or investment advice offered.
github.com/donizetiferr
Consistency
271 of 365 dayswith code shipped, over the last 12 months
Measured on 2026-10-04
Kinds of work in production today
- IntegrationsMarketplaces and management systems exchanging data without typing.
- DashboardsData from separate sources on a single screen.
- DocumentsAutomated reading with human review where mistakes are expensive.
- Web platformsFrom zero to production, delivered in usable stages.
- MigrationsLegacy systems moved to new infrastructure without stopping the operation.
- OperationsActive alerting and a maintenance routine on what's already live.
Before working for myself
- Linx (Stone Co)Director of Operations & Software Engineer2020 — 2023
- NeemoCOO & Full Stack Developer2016 — 2020
Worth calling me if
- Your company has technology demand every month, not once a year
- You want someone accountable for what already runs, not only for the new
- You prefer predictable cost over a quote for every request
- You want to talk directly to whoever does the work
Not worth it if
- You need one thing, well defined, and never again
- The demand fills someone's week — then hiring is the better answer
- The volume needs several people in parallel from month one
- The deciding factor is the lowest price on the market
How it starts
From first contact
to the first month.
No step here is a meeting to schedule a meeting. If at any point it's clear it isn't worth it, I'll say so — and the conversation ends at no cost.
- Same week
Conversation
You tell me what the company needs. No sales deck, no slides.
- A few days
Assessment
I look at what already exists and tell you what can be solved, in what order.
- No commitment
Agreement
We set the monthly fee from your budget, and what it covers.
- No lock-in
First month
It starts. If it doesn't make sense, it ends with no penalty.
Before you decide
The questions
that always come.
Can one person really do a team's work?
A small team's work, yes — and that's exactly why I limit how many contracts I take. What changed is the proportion: today most of the effort in a project is deciding, specifying and reviewing, and that part was always one person's job. If your demand needs several people in parallel from the start, I'll say so in the first conversation.
Who writes the code: you or the AI?
Both, and I answer for the result. I use agents to produce volume, but nothing reaches production without passing automated tests and my review. If it breaks, the problem is mine — not the tool's.
Why don't you send proposals?
Because a proposal is a document that exists to justify a price already chosen, and it costs two weeks for both of us. I'd rather know your budget and tell you straight away what fits inside it. You save time and I don't spend mine assembling a PDF.
Is there a minimum?
There is a level from which the contract sustains itself, because I absorb the infrastructure and AI tooling costs behind that pace. I'll tell you the figure in the first message, before you invest any time — and if your budget is below it, I'd rather say so than deliver badly.
Is it a block of hours?
No. Counting hours makes you think twice before calling me, which is the opposite of what a continuous contract should produce. What we agree on is the month's priority; whatever doesn't fit opens the next month.
What if I need very little in a given month?
The month turns into maintenance, improvements and the "when there's time" queue that never moves. A continuous contract rarely has an empty month — it has months where the work is less visible.
My company already has an IT team. Does this make sense?
Usually more, not less. In-house teams spend their days firefighting and the project queue doesn't move. I come in as extra capacity on specific fronts, without competing for space with whoever is already there.
Do I own the code?
You do, from day one: your repository, credentials in your vault, operational documentation included. If the contract ends, nothing stops working and nobody is held hostage.
Tell me what your company
In the first conversation I'll tell you whether a monthly contract pays for itself in your case — and when it doesn't, I'll say that too. No proposal, no sales deck, no runaround.
Donizeti FerreiraThe one who answers and writes the code