Question 1

Is Qoolo built by a team with life sciences experience, or is it a general technology platform?

Accepted Answer

Qoolo is built by a team that comes from inside life sciences, not one that discovered the industry as a market opportunity. Our founding team brings 40+ years of combined experience across life sciences strategy, commercial operations, marketing, and medical communications - on both the client and agency side. Before building Qoolo, our founders worked with 60+ life sciences companies across 4 continents, including organizations in pharma, biotech, medical devices, diagnostics, animal health, and consumer health.

We've sat in the MLR rooms. We've managed the impossible timelines. We've heard from field teams that they never get past the cover slide of the iVA. We didn't read about these problems. We lived them. Qoolo is the platform we wished existed when we were on the other side.

Question 2

How did Qoolo start, and what problem does it solve in the life sciences industry?

Accepted Answer

We started with a simple idea: make science fit naturally on a phone screen. Our early attempts focused on layout. Then it became clear the layout was not the problem. The format was. For years, life sciences teams had been packaging important content into the wrong assets, including 137-slide iVAs, 21-page PDFs, and slide decks rebuilt from scratch for every market, all built for a world where doctors had time to sit down and study them. That world is gone. The formats stayed. Content that took months to create became unreadable or too long to scroll when doctors needed it on mobile instead.

We stopped optimizing the old assets and built something new: a platform designed to make compliant medical micro-content easier to create, review, and use in real-world moments. What started as a formatting problem became a new category, and Qoolo is the platform that powers it.

Question 3

Is Qoolo compliant and secure enough for regulated content in the life sciences industry?

Accepted Answer

Yes. We built compliance and security into Qoolo from day one, not added later.

On the content side, we manage references and endnotes centrally with PubMed integration, important safety information can be locked into brand themes, and one-click storyboard export generates MLR-ready PDFs structured for workflows such as those managed in Veeva Vault. On the infrastructure side, we use AES 256-bit encryption at rest, TLS 1.2+ in transit, AWS-hosted serverless architecture, logically separated customer data, role-based access controls with audit logging, and annual third-party penetration testing. Our compliance framework aligns with HIPAA, GDPR, and CCPA. Full security information is available on our Security page.

Question 4

Does Qoolo work for both emerging and established life sciences companies?

Accepted Answer

Yes, both.

Larger, established teams use Qoolo to solve the scale problem: managing multiple brands, localizing across markets without rebuilding from scratch, keeping brand control centralized, and producing MLR-ready outputs that fit existing review workflows. Qoolo can also connect into the systems teams already use, so nothing has to change on their end.

Earlier-stage and growing companies use Qoolo to solve a different problem: credibility and capacity. It gives them the content infrastructure to put out compliant, mobile-first, visually credible content. No big design team. No dev resources. No complex tech stack.

The platform is the same either way. Only the starting point differs.

Question 5

Does Qoolo use AI?

Accepted Answer

Yes. We use AI in practical ways across the platform to help life sciences teams work faster and more effectively. One example is Qoolo Assistant, an AI-powered guide that detects where you are in the platform and provides structured support. We also use AI for content structuring, localization, PDF-to-micro-content conversion, medical-article-to-micro-content conversion, and other evolving workflows designed to reduce manual work while keeping teams in control. Some of these AI-powered features are genuinely innovative, and several are patent pending.

Our AI is designed to assist, not replace, human judgment. Content still moves through the appropriate review, approval, and compliance processes before use.

Question 6

I'm a medical doctor or healthcare professional. Can I get involved with Qoolo as an advisor?

Accepted Answer

Yes. Qoolo is open to connecting with medical doctors and other healthcare professionals around the world who believe in the mission and in the potential of medical micro-content to improve how scientific information is created, shared, and experienced. To explore an advisory relationship, send a LinkedIn profile or CV to medicalteam@qoolo.com, and the Qoolo team will review the background and explore whether there is a fit for collaboration.

Question 7

Where is Qoolo based?

Accepted Answer

Qoolo is a US startup headquartered in Princeton, New Jersey, with R&D team members in Subotica and at the Science and Technology Park in Novi Sad, Serbia.

Question 8

Does the Qoolo team have global experience?

Accepted Answer

Yes. Qoolo's founding team has lived and worked in the life sciences industry across the United States, Europe, and Australia. We've also worked with and advised companies across Asia, the Middle East, Africa, and South America. Along the way, we've supported professionals in global roles, regional and multi-country roles, and country-level roles. Our advisor network extends that footprint further.

This international experience helps Qoolo build for the realities of life sciences teams working across regions, markets, and operating models.

We didn't start Qoolo to build a tool. We started it to make science fit on a small screen.

This is why Qoolo exists.The format problem.

This is what we're building instead. The medical micro-content category.

This is what drives us.

Mission

Vision

THESE ARE THE PEOPLE BEHIND QOOLO.

Qoolo leadership

Alex Stojanovic, PhD

Mika Stojanovic, MBA

Mladen Prijic

Advisory board

Medical advisors

John Hwa, MD, PhD, FRACP

Steven J. Evans, MD, FACC

Eric Arehart, MD, PhD

Jonathan Pirruccello, MD

Sanja Maricic Prijic, MD, PhD

John Hwa, MD, PhD, FRACP

Steven J. Evans, MD, FACC

Eric Arehart, MD, PhD

Jonathan Pirruccello, MD

Sanja Maricic Prijic, MD, PhD

Business advisors

Kurt Kessler, PhD

Sri Madabushi, PhD

Barb Carlin, MBA

Philippe Ghem

Mathias Hess, MBA

Kurt Kessler, PhD

Sri Madabushi, PhD

Barb Carlin, MBA

Philippe Ghem

Mathias Hess, MBA

Kurt Kessler, PhD

Sri Madabushi, PhD

Barb Carlin, MBA

Philippe Ghem

Mathias Hess, MBA

The answers you're looking for:

This is why Qoolo exists.
The format problem.

This is what we're building instead.
The medical micro-content category.