The questions we hear most.
Straight answers. If yours is not here, ask us directly.
General
- Who owns the code?
You do, from the first commit. Repository, credentials, and decisions live in your accounts, not ours.
- What does it cost?
A fixed number you see before we start. If we estimated wrong, that is our cost, not yours.
- Who does the work?
The engineer you talk to writes the code and answers the questions. The team grows only when a project needs it to.
- Do you take small projects?
We take work where judgment matters. If it is a good fit, size is not the blocker.
- How do you handle security?
Least-privilege access, encrypted secrets, and a secure SDLC by default, not as an add-on.
- Can you work with our team?
Yes. We embed alongside in-house engineers as technical partners, and we leave the team stronger than we found it.
- Do you have work I can see?
No client work yet. What is live: Atlas CMS runs this site, Tumbuhku tracks child growth against WHO and IDAI standards at app.tumbuhku.id, and Pulse has been publishing in English, Indonesian, and Japanese since March 2026.
Custom Software
- How long does a build take?
Scope decides. The first working slice is in your hands within the first weeks, and the fixed number covers the fixed scope, however long it takes us.
- Can you take over an existing codebase?
Yes. We start with the same audit we would run on our own code, then build from wherever it stands.
- What happens after handover?
Your team ships. We stay reachable, and any continued work is its own fixed scope.
MVP & Product
- Will we have to rebuild it later?
No. Minimum cuts the surface, not the quality: the schema, the auth, and the deploys are production-grade from week one.
- What if the idea changes mid-build?
It usually does. Weekly working software exists so a change costs a conversation, not a contract renegotiation.
- Can you keep going after launch?
Yes. The MVP continues as a product build on the same terms, or your own team takes over. The code is ready for either.
IT Consulting
- Is this a rewrite pitch?
No. The roadmap starts from the smallest reversible change, and a rewrite has to argue its way in against that list.
- How do you work with our engineers?
Alongside them, in your repository and your reviews. The goal is that they own the roadmap when we leave.
- What does the audit actually produce?
A written diagnosis with the evidence attached: what slows delivery, where it lives, and the sequenced steps that remove it.
Still have a question?
Email us and we will answer it within one business day.