Questions I get asked.
Straight answers. If yours is not here, ask me directly.
General
- Who owns the code?
You do, from the first commit. Repository, credentials, and decisions live in your accounts, not mine. The Latellu website and my own products stay mine.
- What does it cost?
Fixed from $15,000. Typical slice: 6 to 10 weeks. You see the number in writing before any deposit. If we estimated wrong, that cost is ours.
- Who does the work?
Ilham Tenriajeng leads Latellu. You talk to him. Each incoming project is staffed with a development team. He signs the quote.
- Do you take small projects?
I take work where judgment matters and the slice fits a 6 to 10 week window. If it is a good fit, size is not the blocker. If I cannot start this month, I will say so.
- How do you handle security?
Least-privilege access, secrets in your accounts, and a boring SDLC. I do not advertise SOC 2, a DPO, or hospital-grade compliance I cannot carry.
- Can you work with our team?
Yes. I embed alongside in-house engineers as a partner, in your repository. I leave documentation your team can run without me.
- Do you have work I can see?
No client work yet. What is live: Atlas CMS runs this site (sample sites in the Atlas docs are demos, not clients). Tumbuhku tracks child growth against WHO and IDAI standards at app.tumbuhku.id. Pulse is an editorial experiment; I do not treat its archive as proof.
- Are you a company?
No. Latellu is a software studio. Ilham Tenriajeng signs. Not a PT or CV. No NIB. Engagements are with Ilham Tenriajeng, personally. Indonesian corporate PO that requires a PT will have to wait, or go through me as perorangan. I will not pretend otherwise to close a deposit.
Custom Software
- How long does a build take?
6 to 10 weeks for a typical slice. The first working build is in your hands in the first weeks, and the fixed number covers the fixed scope.
- Can you take over an existing codebase?
Yes. I start with the same audit I would run on my own code, then build from wherever it stands.
- What happens after handover?
Your team ships. I 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 I 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?
Write to us and we will answer it within one business day.