Athanas Jamo

Athanas Jamo

Chief Client Director

About

With over 18 years of experience in research, insights, and strategic marketing, I currently serve as Chief Client Director at Ipsos, advising clients across the GCC and wider region on growth, transformation, and audience strategy. I help organizations translate market dynamics and consumer behavior into actionable strategies, enabling them to anticipate disruption, identify commercial opportunities, and make faster, evidence-based decisions across media, streaming, sports, gaming, and broader Technology, Media & Entertainment ecosystems.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Forums

•

2d ago

How to do market research before you write any code

Last year I spent six weeks building a reporting dashboard that I thought founders needed. At launch, all I heard was silence. I had taken nods in casual talks to mean people would pay for a special tool.

Before we started our idea, we talked with 18 founders over two weeks. We asked how they keep track of numbers right now. We did not pitch features. We asked what they tried month and where it fell apart.

Fourteen of them used sheets. Three said yes to trying a weekly digest before we built anything. Talk to buyers about the workarounds they use now before you build software on a guess. What question gives you the signal when you test a new product idea?

•

3d ago

Why do some B2B tools create more work than they save?

I've spent years working in hotel operations, where teams often have to complete inspections, reports and follow-up tasks.

One thing I've noticed is that digitising a process doesn't necessarily make it easier. Sometimes, it simply moves the paperwork onto a screen.

I think this is a challenge for anyone building software for frontline employees: making the workflow genuinely simpler, rather than just making it digital.

For those building B2B products, how do you distinguish between features customers request and features that actually reduce their workload?

•

4d ago

How do you set the price for a software feature without making your early customers feel upset?

When we created an automation tool our first thought was to add a separate charge for each user. Current customers objected away saying they took a chance on our product when it was just a basic version. We adjusted our plan. Added the new feature to our top plan while letting existing users keep their current price. This made our early users happy. Helped twenty percent of mid-tier customers move up to the higher plan. How do you choose whether to include a feature, in a package or sell it separately?

View more