Custom software,without the black box
Leave the building to us, so you can run the business instead of the project. The price is agreed before each stage starts, working software arrives every week, and the code and every account are in your name from day one.
- Web and mobile applications
- Technical consulting
- Automation and AI
- Product design
Selected work
Agreed, delivered, and handed over in full — the code, the accounts, and every password in your name. Some clients take it from there. Others keep us running it.
Lenggah
What we commit to
- Agreed before we start
- What you get and what it costs are put in writing before each stage begins. No renegotiating halfway through.
- Everything ends up yours
- The code, the servers, the domain, and every account are in your name from the first day — not ours.
- Talk to the people building it
- You deal directly with the people writing the software. Nobody relays messages on our behalf.
Selected workMata Screen Print
Selected workSerenity Cove Resort
Start small.
The first job does not have to be the whole product. Pick the smallest thing that is genuinely costing you — one process, one connection between systems, one screen people fight with. We agree what it takes, build it, and hand it over. If that went well, we do the next one.
Start smallHow we work
Four stages, each agreed before it starts — so the only thing you ever have to decide is whether to keep going.
- 01
Discovery
We work out the real problem, who uses it, and what limits us — before anyone writes code. You end up with a written plan and a fixed price, and it is yours to keep whether you continue with us or not.
Typical duration · 1–2 weeks
- 02
Design
We decide how it looks and how it is built, together. You review real screens in your browser, not slides.
Typical duration · 2–3 weeks
- 03
Build
Delivered in pieces you can actually use. A working demo every week, and a private link you can open any time — you don’t have to watch it being built, you just always can.
Typical duration · from 6 weeks
- 04
Handover
The code, the documentation, and every password and account are confirmed as yours. From here some clients run it themselves and others keep us on to do it. You are choosing which, and that is the whole point of doing the first three stages this way.
Typical duration · 1 week
What we build
Web and mobile applications
Things people use every day — customer portals, booking systems, internal systems, online shops. Built on proven, widely used technology, so the next person to work on it can pick it up quickly.
- Websites and web apps
- iOS and Android apps
- Internal systems and integrations
Technical consulting
A review, a second opinion, or a plan. Useful when you already have a team and need to know whether what you have will hold up, or what to build next.
Automation and AI
Taking the manual work out — handling documents, sorting requests, summarising, internal assistants. If a spreadsheet would do the job, we will say so.
Product design
How it looks and how it flows, for things that actually get built. Delivered as real working screens, not a PDF.
Running it after launch
Hosting, monitoring, fixes, and the small changes that come up once real people are using it. For teams who would rather not take that on. Priced monthly, cancel whenever, and the accounts stay in your name throughout.
Why us
Seven years inside product teams
Before this studio we spent seven years building and shipping product at established technology companies. That is where the process on this page comes from.
We stay if you want us to
Plenty of clients would rather not run it themselves, and we are happy to — hosting, support, and whatever comes next, agreed the same way as everything else. The difference is that you are choosing it, not stuck with it.
We say no
If an off-the-shelf tool solves your problem, we will tell you and point you at it. Custom software is expensive and it should be the right call.
Built to be handed to someone else
Proven tools, conventional structure, and the reasoning recorded alongside the code. Whether the next person is your team, another studio, or us in a year, nothing depends on what is only in someone's head.
Small on purpose.
You get the people who did the pitch. Nobody is swapped out after signing and nothing is subcontracted — so it is one conversation, not a chain of them.
“95% of new products miss the mark — not because of the idea, but because of poor execution”
Software rarely fails on the idea. It fails on execution. Execution is a process problem, and process is the part we are strict about.
Who we are
A small studio in Indonesia building custom software for businesses that have outgrown their spreadsheets and off-the-shelf tools.
We keep the team small deliberately. It is the only way the person who planned your project is still the person building it three months later.
How we think
Openly, and in writing. The reasoning behind a decision is worth more a year later than the decision itself.
We would rather tell you something is a bad idea early than build it politely and watch it fail.
Agreeing each stage up front means you can stop after any of them without an argument.
What we believe
- Proven technology
- Widely used, well-supported tools. The interesting part should be your product, not the technology we picked.
- Reasons written down
- If we cannot explain why we did something, we have not finished the work.
- Small and senior
- No layer between you and the person writing the code.
- Honest estimates
- We quote what the work costs, not what wins the deal.
Writing
What we have learned about build-versus-buy, the real cost of ownership, and what actually goes wrong in software projects.
Guides
Tell us what you're building.
A few sentences is enough to start. The first step is a call to work out what you need — no charge, no sales deck — and you can stop there with the plan in hand.