Collectr Scaled to 8M Users With Two Engineers

Adam Hishla didn't set out to build a fintech platform. He wanted to track his Pokémon cards.

That's not a dismissive framing—it's actually the most important thing about Collectr's origin story, and it's the part that most infrastructure case studies skip straight past. In 2021, Hishla and his co-founders were already running one startup and burning off the stress at game stores, cracking open packs. They had collectibles. They had no idea what those collectibles were worth in aggregate. They built a tool to find out. Within 24 hours of launching, 5,000 people had downloaded it.

"At that point," Hishla said in a recent AWS-produced video, "we realized we may be onto something."

Four years later, Collectr has 8 million users worldwide and has positioned itself as what Hishla calls "the de facto global pricing authority for collectible cards." Physical game stores around the world are pricing their inventory using the app. Predictive buy/sell signals are coming. The company went from a scratch-your-own-itch hobby tool to critical market infrastructure for an industry—and it did all of that with a total team of eight people, two of whom are engineers.

That last number is what makes the Collectr story worth examining, independent of the AWS marketing context it was packaged in.

---

The 1.6 Engineers Problem

For most of Collectr's existence, Hishla describes the engineering team as "one and a half people." If you've ever worked at an early-stage startup, you recognize that math. It means one full-time engineer and someone else—a co-founder, a contractor, a very brave product manager—who handles whatever doesn't get handled. It is not a sustainable staffing model for a platform that goes viral.

The inflection point came at one million users. That's when, Hishla said, "we realized there's scale challenges that we faced that's on the platform infrastructure." AWS came in first, dispatching engineers and architects to audit how the platform was built and where it was likely to break. That got them to two million users. But AWS also made a second introduction: Dedicatted, a managed services partner operating within the AWS ecosystem.

The jump from two million to eight million came after Dedicatted got involved.

This is a specific and credible claim worth sitting with. The AWS-to-partner pipeline isn't just channel sales strategy—from Collectr's perspective, it was triage. You don't hire two full-time DevOps engineers when you have eight people total; you outsource the infrastructure layer to people who do this for a living, and you buy back the engineering time you need to actually build the product.

---

What "Managed Services" Actually Bought Them

The phrase "managed services" gets slapped on a lot of vendor relationships that amount to "we'll send someone over when it's on fire." What Hishla describes sounds more deliberate than that, and the detail he emphasizes is interesting: Dedicatted's team didn't start with solutions.

"The first interaction was they dove right in to understand what is Collector, what is the platform, what are we trying to achieve before jumping into the problem," Hishla said. "And that's a different lens that gave me a lot of trust and comfort cuz jumping into the problem immediately can rectify it for a short period of time, but not necessarily for the long term."

For a small team getting crushed by inbound requests—business development, user support, partner inquiries, all of it landing on the same eight people—the managed services relationship meant something concrete: the infrastructure layer stopped requiring attention from the founders. Dedicatted handles the scaling machinery; Collectr's two engineers handle application logic. The division of labor is clean enough that user growth from one million to eight million didn't require proportional headcount growth on the engineering side.

That's the business case. And it's a legitimate one. The alternative—hiring two or three more engineers to own infrastructure—costs real money on salary, equity, and management overhead. For a bootstrapped or lightly funded startup (Collectr's funding status isn't public), outsourcing that function to a managed services provider can be the more capital-efficient path, at least at this stage.

---

The AWS Case Study Format: What It Tells You and What It Doesn't

It's worth naming what this piece of content is. The video is produced by Amazon Web Services, features a Dedicatted partner sales lead as the interviewer, and exists to market the AWS Partner Network. That doesn't make the information wrong—Collectr's user numbers are real, and the infrastructure challenges of a 1,600% user growth rate are not fictional—but it shapes what questions get asked and what stays off camera.

We don't hear about what this costs Collectr. Managed cloud services at the scale of 8 million active users isn't cheap, and the trade-off between infrastructure cost and headcount cost is exactly the kind of calculation that founders need to actually run before deciding whether a partner model makes sense for them. AWS and Dedicatted's fees aren't mentioned. Neither is Collectr's revenue model, so there's no way to assess whether the unit economics hold up.

We also don't hear from the users themselves, or from any of the physical stores that are apparently pricing their inventory based on Collectr's data. That's a meaningful dependency—if you're a game store and you're pricing Charizard cards based on Collectr's market data, you're exposed to whatever Collectr's data quality and uptime look like. The app becoming "de facto global pricing authority" is a compelling positioning statement, but it also implies a responsibility that wasn't tested here.

None of this is a knock on Collectr specifically. It's a reminder that the case study format selects for the narrative that makes the sponsor look good. The strongest parts of this story—a genuine product-market fit, a disciplined approach to hiring, a real and growing market—survive the marketing context. The questions the format can't ask are the ones worth asking yourself if you're in a similar position.

---

The Actual Interesting Startup Story Here

Strip away the AWS packaging and there's a model worth studying: a tiny team built something people genuinely needed, resisted the temptation to scale headcount proportionally with user growth, and offloaded infrastructure complexity to a specialized partner so they could keep doing what they were actually good at.

The collectibles market is also, from a business-model standpoint, a more interesting bet than it looks. Pokémon cards and sports cards experienced a genuine speculative boom during the pandemic—prices went absurd, the hobby went mainstream—and there are real questions about whether that market sustains. But a pricing authority in any illiquid market is structurally valuable in a way that a simple tracking app isn't. If Collectr's data is what stores use to price cards, Collectr sits in the middle of every transaction even without taking a cut of it. That creates leverage for eventual monetization—data licensing, premium signals, marketplace integration—that's worth more than the app subscription alone.

The predictive pricing feature Hishla flagged as coming soon is the tell. That's not a feature; that's the business. "The ability for people to understand what they have in the inventory, whether it's a right time to buy, a right time to sell"—that's what Bloomberg terminals do for financial markets. If Collectr executes on it in the collectibles space, the infrastructure story becomes a footnote to a much bigger data story.

Whether eight people—and two engineers running on managed cloud services—can build and maintain that kind of data product at global scale is the question the next case study will need to answer.

---

By Alex Volkov, Startup Ecosystem & Venture Capital Reporter, Buzzrag