Studio / Capabilities
Most digital products in Southeast Asia get designed by teams who have never used an Indonesian network on a mid-tier Android. We design differently. Bahasa-first copy, WhatsApp-native patterns, low-network-tolerant flows, screen-density tested on the devices your users actually hold. UX that earns engagement, UI that earns trust, and a design system that keeps both coherent as your product grows.
An Indonesian user will uninstall your app at the first crash. They will screenshot your pricing page and send it to WhatsApp. They will expect your checkout to work on a 3G connection in a mall basement. Designing for this reality is not a constraint. It's the job. We design with research grounded in Indonesian and SEA behavior, interaction patterns that respect how customers actually complete tasks, and design systems that let your product team keep pace without losing coherence.
A four-phase practice built around evidence, systems, and the user's Monday morning.
Research grounded in the user's actual context: Indonesian network conditions, Android mid-tier devices, Bahasa + regional-language reading behavior, WhatsApp as the messaging primitive. We run interviews, usability tests, and data audits before the first wireframe.
Flows, interfaces, and interactions designed for the product's job-to-be-done. We work in a live design system, not a screen library, a system of tokens, components, and patterns that your engineering team will actually ship.
Usability testing with real SEA users. Accessibility audit to WCAG 2.2 AA. Performance-budget review (design-time decisions that will or won't allow the frontend to hit target load times). Bahasa + regional language review. Design quality is measured before handoff.
Design system maintenance, pattern evolution, and embedded design partnership as your product grows. Your team gets the Figma files, the documentation, the token manifests, and direct access to ours, for as long as you need us.
Four disciplines that together make design a compounding asset, not a one-time spend.
Flows, information architecture, content strategy, and the interaction decisions that define whether your product is usable, learnable, and loved. We design for SEA user behaviors first, not global templates retrofitted for Indonesia.
Visual language, hierarchy, typography, color, and the component craft that makes your product look like itself. UI that works as hard at small sizes and low contrast as it does in a hero screenshot.
Motion, transitions, gesture, feedback: the moments where good UI becomes good UX. We design interactions for network and device realities, not idealized lab conditions.
Tokens, components, patterns, and documentation that let your product team ship quickly without drifting. Figma libraries that match the code library; accessibility built in, not bolted on.
Some engagements aren't one-time design handoffs. They're an embedded design function. Fractional Head of Design, lead product designers, research specialists, and design-system engineers who run alongside your team on a monthly or quarterly cadence. Part of Sprout's augmented-teams model.
Explore the augmented-teams model →A cross-section of design work that has shipped into production and stayed there.
Deep research revealed that drop-offs clustered around moments of missing trust signals, not interaction complexity. Redesigned flows added verification checkpoints, clearer security language, and a regulated-disclosure pattern that respected UU PDP. Conversion moved accordingly.
End-to-end patient journey mapping identified critical drop-off moments across onboarding, first consultation, pharmacy pickup, and follow-up. Redesigned flows compressed the path to a patient's first useful outcome: the moment engagement actually locks in.
WhatsApp is the primary messaging and commerce channel for Indonesian users. Product design that ignores it (or treats it as a notification layer) misses how customers actually interact with brands. The design implication is structural, not cosmetic.
Information architecture, content density, and reading patterns that shift when your product actually lives in Bahasa. The design-system implications most global systems haven't faced.
Why every design we ship passes accessibility audit, what we found the first time we made that the default, and the commercial case for treating a11y as a quality floor.
The decisions that separate design systems engineers adopt from design systems that live as an abandoned Figma library. Token strategy, code-side parity, documentation rhythm.
Tell us what product and what audience: a new customer flow, a design-system consolidation, an accessibility overhaul, an app redesign. We'll scope an engagement sized to the problem, anchored in real user research, with design-system thinking built in. Worst case, you get a clear no and a short memo on what to fix first. Best case, you get a design partner who ships with your engineers, measures what matters, and stays as the system evolves.
Start a project