How we work
See the shape of the system first, then decide
We start from the process you want to sort out, show you the shape of the system, then build it in stages. At every stage you know what is being done and what comes out of it.
- 01
Tell us what you need
Over WhatsApp or a short brief: the process you want to sort out, who uses it, and the systems already in place.
- What we do
- We read your brief or chat, then ask the follow-up questions that need answers before we talk.
- What we need from you
- Tell us about the process you want to sort out: how it runs now, who is involved, and where it most often goes wrong.
- The outcome
- An initial picture of your needs and a time to talk.
- 02
Flow demo or discovery
For websites and simple systems, we show you a flow demo. Complex systems start with a discovery session.
- What we do
- For websites and simple systems, we prepare a clickable draft of the flow with sample data. For complex systems, we show a similar existing system and run a discovery session.
- What we need from you
- Examples of the documents, screenshots, or spreadsheets you use now, and time for one discussion session.
- The outcome
- A written scope: modules, users, and stages.
- 03
Built in stages
Written scope and estimate, staged payments, and progress you can check and test at every stage.
- What we do
- We build in stages as set out in the proposal, with staged payments. You can check and test every stage.
- What we need from you
- Feedback at each stage and people who can try the system.
- The outcome
- A system that becomes more complete at each stage.
- 04
Go-live & support
Team training, documentation, and a support period as agreed in the proposal once the system is in use.
- What we do
- We install the system, train your team, and hand over documentation. The support period and bug handling follow the proposal.
- What we need from you
- Time for team training and the initial data you will use.
- The outcome
- A system your team uses, documentation, and source code that becomes yours once the project is paid in full.
Demo limits
A demo helps you see the shape of the system before you decide.
- Websites and simple systems: a clickable draft of the flow, with sample data.
- Complex systems: a demo of a similar system we have built (sample data), plus a discovery session to map your needs.
A demo shows the main flow only. Real integrations, your actual data, and repeated revisions before an agreement are not included, because they are part of building the system.
How we put together an estimate
We prepare an estimate after discussing your needs, based on the scope, the number of modules, and the build stages. The written proposal covers scope, timeline, and staged payments. We do not use a price list because every system is different.
Staged payments
Payment is split into stages as set out in the proposal. You can check and test each stage before the next one starts.
Source code ownership
The source code belongs to the client once the project is paid in full.
Support after go-live
The support period and how bugs are handled are agreed in the proposal.
Questions about the process
How much does a system cost?
We prepare an estimate once the needs and scope have been discussed, because every system differs in modules and users. The written proposal covers scope, timeline, and staged payments.
Can I see an example or a demo first?
Yes. For websites and simple systems, we prepare a clickable draft of the flow with sample data. For complex systems, we show a similar existing system and start with a discovery session. A demo does not include real integrations, your actual data, or repeated revisions before an agreement.
Who owns the source code once the project is finished?
The source code belongs to the client once the project is paid in full.
Can you continue an existing system?
Yes. We first assess the running system in a discovery session, then agree on which parts to continue, integrate, or rebuild.
Do you work with clients outside Bandung?
Yes. We work remotely with clients in other cities in Indonesia, using WhatsApp for quick questions and scheduled discussion sessions for important decisions.
How does support work after go-live?
The support period and how bugs are handled are agreed in the proposal, based on what your system needs.