Amol Chitale | 21 November 2025

How Tekdi Used a Product First Approach to Simplify

Localization for Digital Public Infrastructure

At Tekdi, our core purpose is to catalyze societal transformation by empowering organizations with technology. But it is hard to focus on transformation when you are stuck in a loop of repetitive data entry.

Recently, while implementing a Building Permits module for an African nation, we hit a roadblock that threatened to stifle our innovation. The project required full localization between English and French to ensure a seamless experience for native speakers.

The specific version of the DIGIT framework we were using didn't support text label localization for workflows out of the box. We were left with a manual grind: editing JSON payloads one by one, hitting APIs twice, and praying there were no typos.

This wasn't just a productivity issue; it was a culture issue. One of our core values is Enjoying the Magic of Creation. There is no magic in copy-pasting JSON for 12 hours a week.

Here is how we applied the Tekdi Way—specifically, our Product First mindset—to turn this manual nightmare into a reusable asset for teams working on Digital Public Infrastructure and government technology solutions.

The Challenge: Stuck at the Base of the Pyramid ⏳

If you visualize software as a pyramid, the base consists of foundational blocks, while the apex holds the unique innovations. We found ourselves stuck fixing the base rather than building the apex.

For 9 different permits, we had to localize hundreds of unique labels.

  • The Process: Identify the label, translate, format JSON, and manually trigger APIs for en_IN and fr_FR_IN.
  • The Cost: 3–4 minutes per label. With 175–200 labels a week, we were burning nearly 2 days of developer time.

This friction wasn't just slowing us down; it was preventing us from delivering the "unique differentiators" that the client actually valued.

For projects involving Digital Governance and public service delivery, these foundational details matter. Development teams need to spend their time improving the services people use, rather than repeatedly handling manual configuration tasks.

The Solution: A "Product First" Approach 🤖

At Tekdi, we believe in Sustainable Open Source—the idea that when you improve a foundational block, you should do it in a way that reduces the burden for everyone.

Instead of just "hacking" a fix for this one project, we decided to build a tool. I teamed up with AI assistants to co-pilot the logic and built a custom React-based automation script that interacts directly with the DIGIT APIs.

The New Workflow:

  1. Prepare: We add labels and translations to a Master CSV.
  2. Execute: The script reads the CSV and automatically hits the DIGIT APIs for both languages.
  3. Verify: A success report is generated instantly.

This approach reflects our Product First philosophy: solve the immediate problem while creating something reusable. It also demonstrates how a practical improvement to an existing government technology platform can make Government Digital Solutions more efficient to develop and maintain.

The Result: From 4 Minutes to 2 Seconds

A label update that took 4 minutes now takes ~2 seconds.

The Impact: Empowering the "Sarkar" and "Bazaar" 🚀

The efficiency gains were massive—9 to 12 hours saved per week. But the true success lay in how this aligned with our mission to empower organizations.

From Vendor Reliance to Client Autonomy

Because we built this tool with a product mindset (intuitive, CSV-based), we were eventually able to hand it over to the client's team.

Instead of relying on us for every typo fix, they now control their own content. We empowered the "Sarkar" (Government) to move with the speed of the "Bazaar" (Business).

For a Government Engineering Partner, enabling client autonomy is an important part of building sustainable technology. The goal is not just to deliver a working solution, but to help government teams manage and improve their digital services independently.

Giving Back: Building For Most, Not For Few 🌍

A key tenet of the Tekdi Way is to Build for most, not for few.

While this project focused on English and French, we designed the automation to be language-agnostic. Whether the next DIGIT adopter needs German, Spanish, or Hindi, this tool works without rewriting code.

By open-sourcing this script, we are Giving Back to the community. We are strengthening the foundations of Open Digital Ecosystems and contributing to the wider Digital Public Infrastructure community. These improvements can help future teams working on Public Service Delivery Platforms avoid repetitive groundwork and focus on building solutions that create meaningful impact.

🔗 Explore the open-source localization tool on GitHub

Reflection

The first time we ran the script and saw 200 labels processed successfully while we sipped our hot coffee, we realized that we hadn't just saved time. We had unlocked the capacity to Give Our Best to the problems that actually matter.

For us, this is what building better Digital Systems for Social Impact looks like: identifying everyday challenges, solving them thoughtfully, and sharing improvements that make technology more accessible and sustainable for everyone.

Frequently Asked Questions

1. How does a Product First approach improve Digital Public Infrastructure?

A Product First approach focuses on solving immediate challenges while creating reusable solutions. In this project, Tekdi developed a language-agnostic automation tool that simplifies localization and supports more efficient Digital Public Infrastructure development.

2. How can automation improve Government Digital Solutions?

Automation reduces repetitive manual tasks, minimizes errors, and saves development time. By automating workflow label localization through DIGIT APIs, government teams can manage content more efficiently and focus on improving public services.

3. Why is an experienced Government Engineering Partner important for Digital Governance projects?

An experienced Government Engineering Partner understands the technical and operational needs of public-sector projects. By building reusable tools and encouraging client autonomy, partners can help create sustainable Digital Governance solutions and strengthen Open Digital Ecosystems.

 

View Similar