# Lokalise Developer Hub

<figure><img src="/files/29nvVIVcYladhgltaoU8" alt="Lokalise Developer Hub" width="563"><figcaption><p>developers.lokalise.com</p></figcaption></figure>

### Introduction

As a Senior Product Marketing Manager, I spearheaded the creation and successful launch of the [Lokalise Developer Hub](https://developers.lokalise.com/), an all-inclusive platform for developer tools and resources aimed at automating and customizing localization workflows. This was achieved through in-depth market analysis, strategic product positioning, and technical Marketing tactics.&#x20;

### Problem

The pre-existing ***scattered*** API documentation, tutorials on blog posts, and product information on Intercom articles caused **confusion** and **slowed** the adoption process for developers wanting to utilize Lokalise's features. Our challenge was to drive awareness and adoption of developer tools through strategic go-to-market planning, compelling positioning, engaging demos, and active community participation.&#x20;

### **Outcome**&#x20;

The launch of the Lokalise Developer Hub led to an **increase** in **API calls** from the hub, elevated web **traffic**, and improved the **developer experience** by offering a centralized location for all necessary materials. This consolidation not only **quickened** the evaluation process for prospective developers but also significantly increased **customer satisfaction** and **adoption**.

### **Tactics**&#x20;

I used a blend of **technical product marketing strategies** to communicate complex product features in an understandable manner to a highly technical audience. I developed a deep understanding of our product and its market, synthesizing technical information and conveying it effectively to drive adoption. Collaboration with cross-functional teams, including product, marketing, partnership, and sales, was key to our successful outcomes.

### **Market Research**&#x20;

The initial market analysis included a benchmark report comparing developer portals from Stripe, Twilio, and Slack. This critical step was accompanied by thorough research on developer hub platforms to decide on a '**build vs. buy**' approach.

### **Sales Enablement**&#x20;

To ensure the wider team was equipped to promote the Developer Hub, I led sales and customer success training sessions, providing sales decks to explain concepts, and created demo sandboxes and getting-started guides.

### **Tactics for Adoption**&#x20;

To further boost adoption, I utilized various tactics such as creating demo videos, conducting user testing with developers and early adopters, and improving developer examples based on feedback. Demo example projects were created to facilitate faster adoption.

### Testimonials&#x20;

What feedback did customer developers provide about the Lokalise Developer Hub?

<figure><img src="/files/uteYShttphszclF2NfNH" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://anilkumark.gitbook.io/portfolio/technical-product-marketing/lokalise-developer-hub.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
