From Zero QA Structure to Ten Engineers Deep. In Two and a Half Years.
Every brand wants to understand its customers. Very few actually can. Zeotap is a Customer Intelligence Platform that makes it possible to help brands collect, unify, and activate first-party data so they can build real relationships instead of guessing. In an era where data is the most valuable resource a company owns, Zeotap is the infrastructure that makes that data usable.
But here's the thing about data platforms: when the data is wrong, every decision downstream is wrong. A bad recommendation engine is annoying. Bad customer data feeding a brand's entire marketing, sales, and product strategy? That's a business-level failure. The quality bar for a platform like Zeotap isn't just high, it's existential.
What does this tell us on the surface?
Every brand wants to understand its customers. Very few actually can. Zeotap is a Customer Intelligence Platform that makes it possible to help brands collect, unify, and activate first-party data so they can build real relationships instead of guessing. In an era where data is the most valuable resource a company owns, Zeotap is the infrastructure that makes that data usable.
But here's the thing about data platforms: when the data is wrong, every decision downstream is wrong. A bad recommendation engine is annoying. Bad customer data feeding a brand's entire marketing, sales, and product strategy? That's a business-level failure. The quality bar for a platform like Zeotap isn't just high, it's existential.
What does this show us if we look closely?
When Moolya started working with Zeotap on November 25th, 2019, there was no QA structure in place. Not a weak one. No established testing process, no structured workflows, no documentation trail. The product was sophisticated, the engineering was moving fast, but testing was an afterthought.
For a data intelligence platform handling first-party customer data, the kind of data that's now at the centre of every privacy regulation and every brand's digital strategy, that's a risk that compounds quietly until it doesn't.
Moolyans didn't walk in with a playbook. They walked in with notebooks.
The first few weeks weren't about running tests. They were about sitting in meeting rooms, gathering information from different teams across Zeotap, and building a picture of how the product actually worked from the inside out. Three Moolya testers started the engagement, and their first job was understanding not executing.
More importantly, they spent that early time building trust. In a client-partner relationship where you're being asked to own quality for someone else's product, trust isn't a nice-to-have. It's the foundation. Without it, you're just a vendor running scripts. With it, you're embedded in the team and making decisions that shape the product.
How did we do it?
The first release happened on December 12th, 2019 less than three weeks after Moolya joined. It was the first-party data SDK, a critical component that enables Zeotap's clients to collect customer data directly. That first release was a success, and it set the tone for everything that followed
From there, the engagement scaled. Three testers became ten test engineers by mid-2022, with senior resources joining as the product's complexity grew. Moolya followed an Agile methodology with Zeotap iterative development where the entire project team participates in every activity, requirements evolve as sprints progress, and coding and testing happen interactively throughout the development cycle rather than as a gate at the end
Once the team had a deep technical understanding of the product, the work shifted from reactive testing to Moolya's bug prevention method finding and eliminating the conditions that create bugs rather than just catching them after the fact. That's the difference between quality assurance and quality engineering, and it's what allowed Zeotap to ship with increasing confidence as the platform grew more complex.
One of the key recent releases was the Demo environment and customer website builder, a crucial tool that enables Zeotap's Sales Engineers to offer customized product demos to prospects. This wasn't a user-facing feature. It was a sales enablement tool, which means the quality bar was different: a bug in a demo isn't just a defect, it's a lost deal. Moolya understood the business impact and treated it accordingly.
Over two and a half years, Moolya went from having no QA structure at Zeotap to being deeply embedded in the product team, participating in sprint planning, driving test coverage, and shaping how quality was measured and delivered across the organization.
The best proof of a testing partner isn't the first release. It's whether they're still there for the fiftieth.
Moolya has been part of many project releases with Zeotap not because of a contract, but because the trust built in those first few weeks in the meeting rooms never broke. That's what turns a three-person engagement into a ten-person team. That's what turns a vendor into a partner.