Questions
The things people ask before they write to us. If yours is not here, ask it — we answer either way.
- How do you charge?
- A fixed price for a defined piece of work, with a delivery date. We do not sell hours, because selling hours pays us for being slow and gives you a number that only becomes real at the end.
- What does it cost to start?
- A discovery is one to two weeks at a fixed price, quoted after the first conversation once we know the size of the problem. You will have that number before you commit to anything, and the plan it produces is yours whoever ends up building it.
- What if the scope changes halfway through?
- We re-quote in writing and wait for your answer before building anything. The alternative — absorbing it quietly and raising it at the end — is how fixed-price projects get a reputation they deserve.
- Who owns the code?
- You do, from the first commit. Code, infrastructure and accounts live in your organisation rather than ours, so there is never a moment where leaving us is expensive.
- What do you build with?
- Mostly TypeScript and Node, Python where it fits, React and Next.js on the front end, Postgres and MongoDB, deployed in containers. We pick what suits the problem and what you can hire for afterwards — a stack nobody else in your city knows is a maintenance problem wearing a technical disguise.
- Do you work outside Bahia?
- Yes. The work is remote and we take projects anywhere in Brazil. We can meet in person in Bahia when it is worth the trip, and most of the time it is not.
- Will you sign an NDA?
- Yes, before the first conversation if you would rather. Send yours and we will sign it, or ask and we will send one.
- How long does a project take?
- The discovery tells you, and that is most of what a discovery is for. Anyone who gives you a delivery date before understanding the data model is guessing, and you will find out which way they guessed in month five.
- Do you take small projects?
- Yes. A discovery is the smallest thing we sell and often the most useful — sometimes the finding is that the thing should not be built, and that is a cheap answer to buy.
- Who will actually work on my project?
- The engineer who scopes it with you in the first conversation. We have no account manager running interference, and we do not sell with a senior and deliver with a junior. You talk directly to whoever writes the code.
- What does the tax reform change in a system that issues notas fiscais?
- 2026 is a transition year. Anyone already issuing fiscal documents has to show IBS and CBS on the nota, for information only - a test rate of 1%, made up of 0.9% CBS and 0.1% IBS, with no effect on what is charged. The software deadlines differ: for NF-e the fields are required from 3 August 2026, and for NFS-e between October and December 2026. Companies in Simples Nacional are unaffected in 2026 and start in 2027, and there is a 60-day window to correct a mistake before any fine. We are not tax advisers and hold no certification. But changing a system that issues notas, adding fields and reworking calculation logic is exactly the kind of work we do.
- Do you use AI to write the code?
- Yes, all the time. It is excellent at the repetitive work and at creating code skeletons, which is what lets senior engineers deliver what used to need a padded team. But it is useless at understanding what your business actually needs, and dangerous if nobody reviews the output - which is why every line that reaches your repository has been read, tested and owned by us.
- Does my code go to a third-party AI?
- That is your call, and it is written into the contract before any work starts. We may use external services to speed development up, but if your company has compliance or LGPD rules that prevent it, the answer is no. If you say no, no line of code and no client data leaves your infrastructure.
- What happens to us if you disappear?
- Nothing that stops you. The repository, the infrastructure, the documentation and the runbook are already in your accounts, and they are written for somebody who has never met us. That is the same reason the code survives us leaving as it is that it survives your own engineer leaving.