// questions
Frequently asked questions
If yours is not here, message us and we will answer it straight.
Money and timelines
How can a small team deliver this scope?
Because an AI-native workflow removes most of the repetitive engineering work — scaffolding, boilerplate, fixtures, migrations. Senior engineers spend their time on architecture, security and review, which is where projects actually succeed or fail. The team is smaller because the repetitive part is smaller, not because anything is cut.
How is the price calculated?
After a short call we write down the scope: what is in and what is out. The price and the deadline are calculated from that, and both go into the contract. New requests later get their own estimate rather than quietly inflating the invoice.
What if the project runs past the deadline?
The deadline is fixed, and overrunning it is our risk, not your invoice. If we got the estimate wrong, we finish the work within the agreed figure.
How does payment work?
Usually 50% at the start and 50% on handover. Larger projects are split into stages. Contract, invoice and closing documents always.
Code and quality
Is AI-written code safe to put in production?
Not on its own — which is exactly why an engineer reviews it. AI is good at volume and bad at boundaries: authentication, permissions, payment handling and edge cases. Those are the parts we check by hand and cover with tests.
Who owns the code?
You do, from day one. The repository, the infrastructure and every account are in your name. We do not hold the keys and we do not build dependency on ourselves.
What happens if we want to move to another team?
You take the repository, the access and the documentation — which is written as the project goes, not on the last day. That is part of delivery, not a paid extra.
We already built a prototype with no-code or AI tools. Will you take it over?
Yes. An audit comes first: what can stay, what has to be rewritten, and where the security holes are. Then an honest answer — which is sometimes "rebuilding is cheaper".
Working together
How much of our time will this take?
About an hour a week: the demo and decisions on anything ambiguous. The rest is on us. But one person on your side has to be able to make decisions, or the project stalls.
Do you do design?
Yes. If there are no mockups we build the interface directly in code and iterate in the browser — faster than drawing screens in Figma and then rebuilding them.
What about support after launch?
30 days of fixes on anything that is our fault, free. Ongoing development and support is a separate agreement, monthly or hourly.
Still have questions?
Email us or fill in the questionnaire and we will get specific about your case.