HiBank
The public face of an Indonesian bank, maintained by its own team.
What we delivered
- Web
- CMS
- 01
The bank’s own team writes an announcement, rate or disclosure
- 02
The content system structures it around banking disclosure rules
- 03
It is live on the public site
The version of this process we replaced had a developer as step two. Removing them is the point: a rate change should not need a deployment.
Solid outline: built and run by us. Dashed: an external system the flow depends on.
The business
HiBank is an Indonesian bank in the BNI group. Its public site is where customers find products and current rates, and where the bank meets its obligation to publish announcements and governance disclosures.
The challenge
HiBank, part of the BNI group, needed a public site its own people could keep current — announcements, product information, daily rates, governance disclosures, complaint intake — without a developer in the loop for every change.
- 01
A bank publishes constantly, and a developer cannot be in that loop
Rates move. Announcements are time-sensitive. Disclosures have deadlines. Any process where publishing requires a deployment fails on the first urgent day — and for a bank, the first urgent day is the one that matters.
- 02
The structure is set by regulation, not by taste
A bank has to disclose particular things, in particular places, on a schedule. The content model had to be built around those obligations rather than around a conventional marketing site.
- 03
A complaint is a routing problem, not a contact form
Intake has to reach the desk that can actually act on it, and there has to be evidence that it did.
- 04
This site is read more closely than most
What is published here is read by customers, by regulators, and by anyone assessing the institution. Correctness is not a quality goal, it is the requirement.
What we did
We built the site and the content management system behind it, so the bank publishes announcements, products, rates, articles and governance pages itself. Complaint forms route to the right desk, and the structure is built around the disclosure requirements a bank operates under.
What we built
The public site
Built and delivered as the bank’s public face.
A content system the bank operates itself
Announcements, products, rates, articles and governance pages are published by the bank’s own team.
Rate publishing without a deployment
Daily rates maintained by the people responsible for them.
A disclosure-shaped content model
Content types built around what a bank is required to publish, rather than generic pages the team has to bend.
Routed complaint intake
Complaint forms that reach the correct desk instead of a shared mailbox.
See it live
Tell us what you are trying to solve
Chat on WhatsApp