The spreadsheet three people email back and forth — replaced properly.

Nothing, until you approve it. The scope we agree before kickoff is fixed, and the price with it. When you ask for something outside that scope — and most projects do — we quote it in writing before we build it, as a separate line you can accept or decline. We don't absorb changes quietly and hand you a larger invoice at the end. That is the single most common way software projects in Indonesia go wrong, and it's the specific thing we organise our process to prevent.

You do. On final payment, all source code, designs, and content are yours outright, along with the repository and the server credentials — held in your name, not ours. We keep no licence over your system and nothing is locked to us. If you want to move to another team later, you can, and we'll hand over cleanly. We'd rather be kept because the work is good than because leaving is difficult.

A fair question, and the honest answer is that we plan for it rather than pretend it can't happen. Every project is documented and every repository is accessible to the whole team, so no system depends on one person's memory. At least two of us know each codebase. You own the code and the credentials from day one, so you are never locked out of your own system. And if we ever couldn't continue, you'd get a written handover — not silence.

Usually, yes. A good share of our work is integration rather than greenfield — connecting to accounting, payment, or logistics systems you already run, or taking over an application someone else built. If we look at an existing codebase and think the honest answer is to rebuild rather than patch, we'll say so and show you the reasoning, including the cost of both paths.