Delivered work Absolute tenure: October 2021–November 2024
Upaj in Brazil and Malaysia
Taking an Indian product configuration abroad meant revisiting language, units, environmental information and institutional requirements together.
My role Product adaptation and regional partner delivery with engineering and data teams.
Why this mattered
An existing product configuration could not simply be translated and shipped. The meaning of its inputs and the institutional workflow around its outputs could change with the market.
Language and the underlying assumptions
The adaptation covered Portuguese for Brazil, Bahasa Malaysia, unit conversion, local weather and soil information, and financial/agricultural requirements. Translation was one part of a configuration that needed to make sense in a different operating setting.
I joined regional requirements with engineering and data work. The product decision was to consider language and the underlying information together, rather than assume an Indian configuration could transfer once its labels were translated.
The historical records identify CRIF custom-score collaboration in India and Experian in Brazil. Those market relationships stay distinct in the scope table, instead of letting partner names imply the same configuration or delivery state in every country.
Local requirements into partner delivery
The institutional path included procurement, technical due diligence, integration and onboarding. My product contribution connected local requirements to the engineering and data work needed for partner delivery.
Bank of Brazil and Experian are named in the career records. The table shows what is known by market and leaves the commercial milestone unresolved where the account does not distinguish pilot, accepted integration and paid production.
A shared platform can reduce repeated work, but inputs and outputs still need to make sense locally. In another expansion I would inspect the receiving workflow and available evidence before deciding which configuration to reuse.
Scroll across to see every column.
| Market | Documented adaptation / relationship | Last supported status |
|---|---|---|
| Brazil | Portuguese; local information requirements; Experian credit-data collaboration. Bank of Brazil is named in institutional delivery. | Deployment/onboarding reported. Module, pilot versus paid-production status and commercial result are unspecified. |
| Malaysia | Bahasa Malaysia; local information and institutional requirements. | Deployment reported. Institution-by-module scope and commercial status are unspecified. |
| India — separate context | CRIF custom-score collaboration. | Recorded collaboration, not evidence of an international deployment. |
Unit conversion and local weather/soil adaptation are described across the programme; the records do not allocate every requirement to an individual market.
Reported deployment scope
The career records report deployment in Brazil and Malaysia and institution onboarding, including Bank of Brazil and Experian. They do not establish market-by-module scope, contract value, regional adoption, or whether each milestone was a pilot, accepted integration or paid production service.
Sources & technical detail
Original artifacts, detailed tables and source notes.