Case study
Turning Codilar's marketing function into a growth capability.
- Marketing & Communications Manager
- Digital Commerce
- India · UAE · Saudi Arabia · USA
Codilar was stronger than its marketing made it look.
01
The challenge
Codilar had the harder half already: technical depth, enterprise customers and platform partnerships. What it did not have was a market-facing version of that credibility. Marketing was an execution function producing output, not a capability the business could rely on to create visibility.
So the problem wasn't effort. It was the gap between real capability and how little of it a prospective customer could see: no shared positioning, a website that read like a brochure, content produced without an architecture behind it, and customer proof that lived in conversations instead of assets.
Strong capability, fragmented visibility. The job was to close that gap.
02
The strategic shift
The operating change was from producing marketing outputs to building a system, website, SEO, content, customer proof, events and reporting working together around commercial priorities rather than as separate channel programmes.
Everything that follows is the implementation of that decision, not a list of campaigns. Each part was built to feed the next: positioning shaped the website, the website shaped search and content, content and customer proof supported sales, and reporting told us where to spend attention next.
03
Building the marketing organisation
The team grew from 4 to 12. That growth is what made a system possible: marketing moved from executional support to owning content, SEO, social, design, events and marketing operations, with clearer ownership, review processes and reporting rhythms.
04
Website transformation
I owned the website from the marketing side - positioning, information architecture, messaging, content and conversion-focused structure - working with internal and external design and development teams to deliver it.
It was restructured around how buyers actually evaluate a digital commerce partner: platform capability, industry context, proof and regional relevance. The result was a site that expressed what the company could actually do.





05
Regional SEO
The logic was market → search intent → regional pages → organic visibility. Rather than publishing SEO pages for volume, we mapped commercial-intent demand in UAE, Saudi Arabia and the US and built 34+ regional pages against it.
Search visibility was then validated against commercial-intent queries across UAE and Saudi Arabia, giving the regional page strategy a measurable organic outcome.






06
Content system
Content stopped being a publishing calendar and became an architecture: topic clusters tied to platforms, industries and regions, with blogs and case studies feeding the same demand paths.
Customer proof was part of that system rather than a separate exercise. Existing relationships were converted into documented case studies, testimonials and enablement assets the commercial team could use directly in a deal.
07
Events & co-marketing
Participation in 14+ international commerce events was treated as market-facing work rather than event execution: presence in UAE, Saudi Arabia and US markets, relationships built in person, and partner and platform co-marketing used to extend reach in regions where the brand was still unfamiliar.

08
Reporting & business alignment
Reporting moved past channel activity. It was rebuilt around a small set of measures leadership could act on - traffic, content coverage, regional visibility, customer proof and inbound demand - with an inbound lead baseline reported at roughly 10 per month.
No single channel is claimed as the sole source of that volume, and no confidential dashboards are reproduced here.
09
Results
Documented changes across the period. Revenue and pipeline attribution are deliberately not claimed.
10
Reflection
The biggest change wasn't a campaign or a channel. It was turning marketing from a collection of activities into an operating capability - positioning, website, regional search, content, customer proof, events and reporting that continued to work as a system after I left.