About
A studio. The code is yours from day one.
I am Ilham Tenriajeng. Latellu is my software studio in Makassar. I lead it. Every project that comes in is staffed with a development team. No PT, no CV, no NIB. If you need a badan hukum to issue a PO, say so before any deposit.
Every engagement ends with you holding the codebase, the tests, and the deployment pipeline. You have owned them since the first commit, because the repository lived in your accounts from day one.
The engagement
One person, from kickoff to handover.
01
A fixed price before work starts
Scope is written down and priced before the first commit. Fixed from $15,000. Typical slice: 6 to 10 weeks. The number you see is the number you pay; if the estimate was wrong, that cost is ours. Nothing is billed by the hour.
02
Working software every week
Every week ends with something you can click through in your own repository. If it is wrong, saying so costs you one week, not one quarter.
03
Handover from day one
Repository, credentials, and infrastructure live in your accounts from day one. The last day of the engagement changes nothing, because there is nothing left to hand over.
04
After, on your terms
Continued work is its own fixed scope. Or you take the codebase to your own team, which was the plan from the start.
Ilham Tenriajeng
Makassar, Indonesia
Founder. A development team on every project.
I am the person behind Latellu. I answer the email and sign the quote. The build is done with a development team staffed for that project. I also work as a fullstack engineer at SIPS Edutech Indonesia in Makassar. The products you can check: Atlas runs this site, Tumbuhku is live at app.tumbuhku.id, and Pulse is an editorial experiment, not a client case study.
Latellu is a software studio. Ilham Tenriajeng signs. Not a PT or CV. No NIB. Engagements are with Ilham Tenriajeng, personally.
How the work actually runs.
You talk to the person behind the studio.
The person in the kickoff call is Ilham. He leads Latellu, signs the quote, and stays on the work. Each incoming project is staffed with a development team. That is not a hidden bench. It is how the studio runs.
That also means bad news arrives fast. If something is slipping or an approach is not working, you hear it the week it happens, from the person who knows why.
Decisions are written down.
Every non-obvious choice gets a short note in the repository: what was decided, what was rejected, and why. Commit messages say why, not just what.
This is what makes the handover real. The next engineer inherits the reasoning, not just the code, and never has to schedule a call with me to understand their own system.
Boring choices, deliberately.
The stack below is proven, documented, and hireable. Every tool in it is picked so that the next engineer already knows it, the failure modes are on record, and nothing needs me around to keep running.
When a project genuinely needs something unusual, it gets it, written down with the reason. Novelty has to be argued for; the boring option is the default.
Built with
- TypeScript
- React
- Next.js
- Go
- Laravel
- Node.js
- PostgreSQL
- Tailwind CSS
- Docker
- AWS
- GitHub Actions
Think this is a fit?
Tell us what you are building. We will come back on whether we can take it, roughly how long it would take, and how the work would run.