Product Over Language: How a Product-Led Mindset Bridged the Gap with Turkish Clients

When a Dutch e-commerce platform decided to expand into the Turkish market, they partnered with a group of Turkish business clients who would be the first adopters and co-development partners for the localised product. The opportunity was significant — Turkey's e-commerce market was growing rapidly. But there was a practical problem: the Dutch product team spoke no Turkish, the Turkish clients spoke limited English, and the project involved complex requirements around payment systems, logistics, and local regulations. Emplex was brought in to help make the collaboration work.

The Challenge

The language barrier was real and immediate. Email threads became tangled when nuance was lost in translation. Video calls were exhausting for both sides as participants struggled to express technical concepts in a shared language that neither spoke natively. Misunderstandings about requirements were common — not because of disagreement, but because both sides thought they had agreed on the same thing when they had not.

Beyond language, there were cultural communication differences. Turkish business culture places high value on personal relationships and trust-building before diving into transactional discussions. The Dutch team, accustomed to getting straight to business, initially skipped the relationship-building phase, which left their Turkish partners feeling that the engagement was purely transactional and that their input was not genuinely valued.

Traditional solutions — hiring translators, writing exhaustive specification documents — were slow and expensive, and they still did not solve the underlying alignment problem.

Our Approach

We introduced a product-led communication framework that replaced words with shared visual and interactive artefacts as the primary medium of alignment. The core idea: when language is a barrier, let the product itself be the conversation.

Clickable prototypes as the shared language: Instead of written requirements documents, we built interactive prototypes in Figma that the Turkish clients could click through, annotate, and react to visually. A screenshot with a red circle and an arrow communicates more clearly than three paragraphs of translated text. We established a rhythm: prototype first, discuss second, document last.
Show, don't tell — weekly demo sessions: Every Friday, the development team demoed working software to the Turkish clients. Not slides, not mockups — the actual product running on a staging environment. The Turkish clients could point at the screen, gesture, use simple phrases, and everyone understood immediately whether something was right or wrong. These sessions replaced lengthy written feedback cycles.
Visual feedback tools: We set up tools that let the Turkish clients record short screen recordings with voiceover in Turkish. A quick AI-assisted translation gave the Dutch team the gist, and the screen recording provided the precise context. This was faster and more accurate than email threads.
Relationship investment: We coached the Dutch team to open every meeting with five minutes of personal conversation — asking about families, sharing photos, discussing football. We also arranged an in-person kickoff in Istanbul where both teams spent a day together before any work discussion. This investment in relationship-building transformed the Turkish clients from cautious partners into enthusiastic collaborators who went out of their way to help the project succeed.

The Implementation

The shift to product-led communication happened over three weeks. Week one, we replaced the existing requirements backlog with a prototype map — every planned feature represented as a clickable flow rather than a text story. Week two, we trained the Turkish clients on the visual feedback tools and ran the first demo session. Week three, we established the full rhythm: Monday prototype sharing, Wednesday async feedback, Friday live demo.

The critical moment came in week two. During the first demo, a Turkish client pointed at the checkout flow and said, in halting English, "This — no. In Turkey, this." He pulled out his phone and showed the team how a popular Turkish e-commerce app handled the same flow. In thirty seconds, he communicated what three rounds of written requirements had failed to convey. The Dutch team immediately understood, and the feature was redesigned that same week. That moment convinced both sides that the product-led approach worked.

Results

After two months of the product-led framework:

Requirements misunderstandings dropped by 80% — the prototype-first approach eliminated most ambiguity before development started
Feedback cycle time went from an average of 8 days (email back-and-forth with translations) to 2 days (visual feedback + demo)
The Turkish clients became active co-creators — they started sending unsolicited prototype annotations with local market insights that significantly improved the product's market fit
The relationship deepened beyond the project — the Turkish partners introduced the Dutch company to their business network, opening three additional market opportunities
The product launched on time in Turkey with a localisation quality that competitors who had used traditional translation-heavy approaches had not achieved

Key Takeaway

Language barriers are only insurmountable when you insist on language as the primary communication medium. By shifting to a product-led approach — where prototypes, demos, and visual artefacts carry the conversation — both teams found common ground that transcended vocabulary limitations. The added investment in personal relationships created trust that made the Turkish clients feel like partners rather than customers, and that trust made every interaction more productive and forgiving of the inevitable miscommunications.

Working with international clients or teams across language barriers? Talk to us about building a product-led communication framework that keeps everyone aligned.