Why we build software from the Philippines

Mrkd is a Philippines-based software studio serving global teams. That sentence sits at the top of our homepage on purpose, and we mean it in a specific way.

There is a version of the "we build software from the Philippines" line that gets used by cheap-hourly outsourcing shops to fish for Western budgets. That is not the model we run, and it is not the argument we're making. What follows is the honest case for what a Philippines-based studio can actually be — and why we chose to build ours here rather than anywhere else.

The four things that make the Philippines specifically strong

Every country has trade-offs when it comes to software work. These are the four that make the Philippines specifically strong for the kind of studio we run.

1. English-first communication. The Philippines is one of the largest English-speaking countries in the world, and — importantly — English is used in business here, not just at a conversational level. Contracts, documentation, meetings, code review, engineering disagreements — all of it happens natively in English. There is no "translation tax" a client pays for working with us. Slack messages read the way a US or Australian colleague's would. Written specs look like written specs.

This sounds like a small thing. It is not. A great deal of software work is text — asynchronous, precise, revised in place. Working with a team that writes English the way you do removes an entire category of misunderstanding from the project.

2. Time-zone overlap in three directions. Manila sits at UTC+8. For our clients that means:

• United States (West Coast): their late afternoon overlaps our morning of the following day — real synchronous working time, every day, on both sides.
• Australia and New Zealand: near-perfect overlap. Our working day is their working day.
• Europe and the UK: their morning overlaps our afternoon, with three to five real hours of live conversation daily.

We do not run a night shift. We do not ask our team to work at 2 am for a stand-up. The overlap is real, in the middle of both our working days, in every direction. That is a deliberate outcome of where the country is, not a heroic effort by anyone on either side.

3. Depth of engineering and design talent. The Philippines has a genuinely deep pool of senior engineers and designers. The country's tech industry didn't start last year — it has been maturing for two decades, with a large community of people who have built real systems inside multinational companies, product startups, and long-tenured local teams. Manila and Cebu in particular have strong communities across React, React Native, Node, Python, iOS, Android, and modern design tooling.

The bottleneck at studios here is not finding talent. It is choosing among it. A well-run hiring process — like the one we run — has plenty to filter down from.

4. Craft as a cultural default. This is the least measurable of the four, and probably the most important. There is a strong craft ethic in Filipino design and engineering work that shows up in the details: careful spacing, considered typography, restraint in animation, code that is clean without being clever. It is not universal — no culture is — but it is common enough that hiring for it is not hunting for a rare trait. We think it comes from a mix of the strong local design and illustration community, the maturity of the engineering industry, and a general preference here for doing things properly rather than fast.

The distinction that matters — studio, not shop

The Philippines has both kinds of software business: sophisticated studios and generic outsourcing shops. Naming which one you're buying from is the whole conversation.

	Outsourcing shop	Studio (like ours)
How they hire	Against a rate card, quickly	Against a craft bar, slowly
Team size on a project	Large, changes often	Small, stable
What they sell	Hours	Outcomes
Who joins the client calls	Account manager	The people doing the work
Decision-making	Escalated to a director	Made by the practitioner
Output quality	Averages to the mean	Averages to the top
Cost model	Rate × hours	Scope × outcome

The market conflates these because from the buyer's side they can look similar in the first pitch. They are not similar in what they deliver. We built our version of the model deliberately in the studio column, and we structure our pricing, our hiring, and our project shapes around it.

The business case, honestly

For most of the work our clients hire us for — a website, a product, a mobile app, an admin dashboard — the honest picture is:

• Blended rate range: meaningfully below a comparable US or Australian studio of the same craft level.
• Team size: smaller than an equivalent local agency, because each person is doing more of the work.
• Total build cost: typically 50–70% of the local-market equivalent for the same scope, at the same quality bar.
• Time-to-first-working-version: roughly the same as any strong studio anywhere — the two-week prototype phase runs the same regardless of geography.
• Ongoing cost of ownership after launch: significantly lower, because the same team stays with the product at the same rate.

The 50–70% figure is not because we are cheap. It is because our overheads — office, salaries, cost of living, insurance — are all denominated in a currency where the same craft costs less to produce. That savings is passed through honestly. It is not the result of underpaying anyone.

Where the model does not apply

We are honest about the shape's limits.

Regulated on-soil work. Anything requiring physical data residency in the client's country, or engineers with local security clearances, is a different shape of engagement.

Buyers who need in-person presence weekly. Some engagements genuinely need a team on-site every week. We are not that team. We are on your video call, in your Slack, and in your shared document — not in your office.

Buyers who value physical proximity above all. This is legitimate, and expensive. If your priority is the person in the room, hire someone in your room.

For everything in between — which is the majority of software work — a Philippines-based studio like ours is the shape that delivers the most craft for the money.

The answer

The Philippines is where we build from because the model actually works here — English-first, time-zone-aligned, deep talent, craft as a default. Cost is a real outcome of that, but it is a consequence, not the pitch.

If you want to see what a Philippines-based studio actually delivers on your kind of work, send us a short brief. We reply within one business day.