Client
Inviboo (Idin Studio own product)
The Problem
Indonesian wedding tech is crowded with templates but thin on product depth. Couples want more than a one-night URL — they want a place that remembers the event, holds the photos, lists the vendors, and stays useful after the wedding day. The existing tools either copy each other's invitation templates or push generic Western SaaS that does not understand Indonesian wedding flow, family structure, or payment habits. Inviboo exists to close that gap, and to give Idin Studio a domain-specific product the team controls end to end.
Constraints
- Indonesian-first design — wedding flow, family hierarchy, and event types must feel native, not translated
- Bahasa Indonesia copy that uses 'kamu' — warm, personal, not corporate
- Low-bandwidth tolerance — guests open invitations on 3G in regional cities, not fiber in Jakarta
- Local payment rails — virtual account, e-wallet, and QRIS must work alongside cards
- Pricing that fits Indonesian wallets — per-event tiers from free to Rp 149K, family plan Rp 299K per year
- Run the product on the same engineering discipline we sell to clients — no shortcut just because it is ours
Our Approach
Inviboo runs on the same stack and the same agentic workflow Idin Studio uses for paying clients. Backend is Go with the Chi router on PostgreSQL — 60+ handlers, 150+ migrations, mature enough to run a small SaaS today. Frontend is Next.js 15 with Tailwind v4, currently sitting at around 60% — the public landing, demo flow, and core invitation builder are polished, while vendor profile and a few admin areas are still in progress. Tagline live on the landing: 'Undangan Digital yang Ngerti Kamu' — the product positioning leans on understanding the user, not template volume. We ship in the open, dogfood every release on real weddings, and treat early users as design partners.
Tech Stack
Outcome
- Landing page live at inviboo.com with a working demo and the tagline 'Undangan Digital yang Ngerti Kamu'
- Backend at roughly 75% maturity — 60+ handlers and 150+ migrations covering invitations, RSVP, vendor profiles, and lifecycle events
- Frontend at roughly 60% — invitation builder and core flows shipped, vendor profile and parts of the admin still in progress
- Real testimonials from real Indonesian couples — Idin & Novi, Dudi & Elsa, and others — used the product on their own weddings
- Three pricing tiers shaped to local wallets — Traktir per event, Premium at Rp 149K per event, Keluarga at Rp 299K per year
- Pre-revenue, on purpose — no paying users yet, the focus is product depth and market fit before monetization
Why this matters
Inviboo is how Idin Studio earns the right to talk about Indonesian product work. We run the same engineering discipline on our own product that we run on client engagements — and we carry the same risk our clients carry, with our own time and money. The work compounds: every pattern we harden for Inviboo — the Clean Architecture backend, the agentic workflow, the localization defaults — becomes a reusable asset across client projects. Pre-revenue today, but the product is real, the testimonials are real, and the codebase is shipping.