FAQ
The questions your board, your lawyer and your CTO will ask.
Straight answers to the things people want to know before they sign.
Ownership and data
Who owns the code?
You do. All product code, infrastructure, credentials and intellectual property transfer to you at launch. We build on standard, open technology, so there is nothing to keep licensing from us.
Where do our code and data go?
Into your repositories, your cloud accounts and your environments, in your name from day one. We work inside your perimeter where your security policy requires it, and we sign your data processing agreement.
Do AI tools see our code?
Yes, in the same way a code editor does. We will walk your security team through what goes where before we start, and if a part of your system must never touch an AI tool, we work on it without one.
How AI is used
Who reviews AI-written code?
A senior engineer reviews every line that ships, without exception. AI does the mechanical work. People make the decisions and carry the responsibility.
Who is liable if there is a defect?
We are. There is no AI carve-out in our contracts. If we ship a defect, we fix it at our cost.
Will our product feel like it was built by AI?
No. Design, architecture and every product decision are made by people. AI changes how fast we build, not what gets built.
The engagement
What if scope changes mid-build?
We price the change before we do the work. You see the cost and the effect on the timeline, and you decide. We never change the budget on our own.
What if you finish early or late?
If early, you get it early. If late, the price does not change and the cost is ours. Payments are tied to milestones, not to time.
Who will actually do the work?
The people you meet in the first step are the people on the build. We do not pitch with seniors and staff with juniors. If someone has to change, we tell you in writing before it happens.
Can our team be involved?
Yes, and we recommend it. Pair one of your developers with the team and the knowledge transfers during the build rather than in a handover document.
After launch
Can our team maintain what you build?
That is the design goal. Standard stacks, documented architecture, every decision recorded in the repository, and a walkthrough at handover. Then 30 days of support for questions.
What happens after the 30 days?
Whatever you choose. Run it yourself, come back for a further fixed-price phase, or move to monthly ongoing support. There is no lock-in.
Practical
Where are you based?
Engineering in Sofia, Bulgaria. Offices in San Jose and Dallas. We schedule calls in your time zone.
Which entity do we contract with?
Our Bulgarian company. We invoice in US dollars and work with US and UK clients on this basis routinely.
How small can we start?
The $2,500 production readiness audit or the $3,500 discovery sprint. Both are useful on their own, and both can lead to more.
Something we have not answered? Book a free 30-minute call and ask.