Kodari Technologies · Est. 2019

We are
Kodari.

A design and development studio based in Ormoc City, Philippines. We build products, brands, and platforms for clients who want work that is honest, fast, and built to last.

No 60-slide decks. No committee sign-offs. Just a tight team that ships real things in real time.

Design Development Brand Strategy PH · Remote
Team at work the team
Planning session monday planning
Code in progress wednesday build
6+
Years shipping products
40+
Projects delivered
3
Countries with active clients
5d
Average sprint to tested prototype
Our story

Started by designers who got tired of decks.

Kodari started in 2019 with one frustration: too many studios were selling process instead of product. Clients were paying for discovery phases, research sprints, and alignment workshops — and getting Figma files that never shipped.

We built Kodari around a different premise. Every project starts with a five-day sprint. Every sprint ends with something testable. Everything we make either gets built or we have a specific, honest reason why it doesn't. No shelfware.

Six years later that discipline is still the thing that defines us. We work with startups, SMEs, and established businesses across the Philippines, Australia, and beyond — on products that range from healthcare platforms to aviation booking systems to AI-powered tools.

We are a small team by choice. Small means everyone who works on your project is someone whose work you can actually see.

Kodari team at work Ormoc City, PH
The people

Small team. Zero passengers.

Everyone here does the actual work. There is no account management layer, no client-facing team that hands off to a production team. You talk to the people building the thing.

Bobby Yu Director of Ops

Bobby Yu

Director of Operations · Philippines

Oversees delivery across all active projects, manages the Philippines studio, and makes sure every sprint stays on track and on brief. Bobby is the reason nothing falls through the cracks.

Asks "does this actually ship?" at least once per meeting.
Lead Designer Lead Design

The Design Lead

Senior Product Designer

Runs the design track from problem definition to production handoff. Fluent in both the neo-brutalist work we love and the clean SaaS interfaces our clients need. Does not use gradients on buttons.

Has strong opinions about font weights below 18px.
Lead Developer Lead Dev

The Build Lead

Full-Stack Engineer

Python, Django, PostgreSQL, Node.js, and whatever the project actually needs. Has shipped everything from custom booking systems to real-time WebSocket dashboards. Allergic to technical debt left in the brief.

Writes tests before features. Yes, really.
How we work

The sprint. Every time.

We run the same five-day sprint format on every project. Not because we lack imagination — because it works. Here is the rhythm.

01
Monday

Define the actual problem.

Stakeholder interviews, user journey mapping, and one written problem statement that everyone signs off on before Tuesday begins. If Monday is unclear, the whole week is guesswork.

Brief Interviews Problem statement
02
Tuesday + Wednesday

Sketch, decide, build.

Paper sketches Tuesday. No Figma, no digital tools — volume over quality. Wednesday we vote on direction, lock the decision, and start building the prototype. One direction. No revisiting.

Crazy 8s Dot voting Prototype
03
Thursday + Friday

Test with real people. Ship or iterate.

Five user sessions Friday morning. Compiled readout at noon. Go or no-go decision by 3pm. The sprint produces a direction, not a finished product — and that is exactly what it should produce.

User testing Readout Go / No-go
What we believe

Four things we won't compromise on.

These are not values we put on a wall. They are constraints we operate inside every day.

📦

Ship or explain why you didn't.

Work that sits in Figma is not work. We hold ourselves to a simple rule: if it is not live or in active production, it needs a specific, honest reason. "We ran out of time" is a reason. "It wasn't good enough" is a reason. "It just sort of stalled" is not.

🔍

Honest over comfortable.

We will tell a client when we think they are solving the wrong problem. We will push back on feedback that would hurt the work. We will say "this is going to take longer than we thought" the moment we know it, not the day it is due. Comfortable conversations produce uncomfortable results.

🔬

Small and intentional beats big and vague.

We take on fewer projects than we could fill. That is a deliberate choice. Every project we accept gets our actual attention — not a project manager's check-ins and a junior team's execution. If we say yes to your project, the people who said yes are the people doing the work.

🌏

Remote is not a compromise.

We are based in the Philippines and we work with clients across Australia, Southeast Asia, and beyond. Distance has never cost a project quality or speed. What matters is process, communication, and the decision-maker being available when decisions need to be made. Everything else is logistics.

Life at Kodari

What it actually looks like.

We work hard, argue about type choices, ship things on Fridays, and celebrate when things land well. Here is a look inside.

Team collaboration deep work mode

We ship on Fridays.

Not because we are dramatic about it. Because five-day sprints end on Friday and we like the feeling of closing the week with something real in the world.

Team meeting friday readout
Working session wednesday decisions
Team celebration when it ships
Code on screen thursday build

We are always looking for people who care about the work more than the job title. If that sounds like you, say hello.

Say hello →
Work with us

Got a project?
Let's build it.

We take on a small number of projects at a time. If you have something worth building, we'd like to hear about it. No forms, no NDAs on the first call — just a conversation.