Rates & terms
All of this is true before we talk, so neither of us spends a week finding out it is not a fit.
Currency and payment methods
I invoice in USD or BRL. Bank transfer, Wise or PayPal; Pix for clients in Brazil.
Robux is not accepted
Not at any exchange rate, not through DevEx, not as part payment, not as a bonus on top of cash. If Robux is the only budget available, we are not a fit — and I would rather you know that now than after a week of scoping.
How payment is structured
- Payment in milestones, each one tied to something you can run and test before you release it.
- Never the full amount upfront. A small task can be a single milestone paid on delivery.
- Price is quoted per task when the scope is fixed, or hourly for ongoing work.
Ways to work together
One-off tasks, ongoing maintenance, part-time and full-time. There is no minimum project size — a two-hour fix is welcome work, and quoting it honestly costs me nothing.
Unpaid technical tests, on one condition
I'll build for free if the code gets to become public portfolio afterward — that's how the eight open-source projects under MIT on this page came to exist. If the scope requires staying locked behind an NDA with no way out, it's paid work.
Quotes
Within 24 hours of having enough detail to be accurate. If a scope is too vague to quote, I say so and ask the specific questions that would fix it.
What to send in the first message
The four things that let me answer usefully instead of asking four rounds of questions:
- What the system has to do, in your own words.
- Your budget and the currency it is in.
- The deadline, if there is one.
- The engine and framework — Roblox / FiveM (ESX, QBCore, standalone) / Minecraft (Spigot, Paper), or something custom.
Working hours
Monday to Saturday, roughly 09:00–19:00 UTC-3 (Brazil). Flexible around your team’s timezone for calls and releases.