# Two million page views took two years last time, and a month this time

> Vlad Cealicu on reaching two million page views with Anchor Terminal in about a month, with two developers and two Claude subscriptions, after it took CryptoCompare two years and a team of ten, and what that speed does next.

- Canonical: https://www.anchorterminal.com/blog/what-the-next-model-is-for
- Markdown: https://www.anchorterminal.com/blog/what-the-next-model-is-for.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/blog/what-the-next-model-is-for.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/blog/what-the-next-model-is-for.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-10-31

By Vlad Cealicu, 31 October 2026. 855 words, about 4 min to read.

My last business took two years and a team of ten people to reach two million page views. Anchor Terminal reached 2,004,331 on 31 October 2026 [[1]](#ref-1), about a month after its first commit on 25 September, built by two developers with two Claude subscriptions. The speed is just crazy.

I spent twelve years building CryptoCompare, and I was the CTO the first time we got to two million. This time it was Quynh and me, Opus 5.5 and a lot of agents, and before Opus 5.5 I think it would have taken us much longer. (It's not a perfect comparison. These are page views of every kind, people, agents and crawlers, and the first time round there were no agents reading anything. I still don't think the gap is anywhere near small enough to explain it away.)

## What a day looks like now

At 22:38 on Friday 30 October I sent a launch post about opencommerce and asked whether we should list it. By 22:49 I'd sent four more, and while I kept going each one was checked, and the three new models were researched and graded by an agent of their own. Two of them claimed "#1" or "first" on their own pages and were wrong on the leaderboards they named. By midnight they were listed, with the reasons and sources for every score.

This is that Friday from git and GitHub, counted at 23:45 [[2]](#ref-2).

- 28: pull requests opened, 26 merged by midnight
- 93: commits on main
- 24: new listings graded (20 on the site that night, 4 waiting for review)
- 17: research agents I started, one per listing or check (Quynh ran her own)

Friday 30 October 2026

The same day we shipped accounts, live stats, a security sweep, the company dashboard and four blog posts. I think a team of five researchers and five developers would need about two working weeks for that (my estimate, and it leaves out the months it takes to hire them).

## Why it feels surreal

I know roughly how long things take, and that sense is now wrong by a factor I can't hold in my head. Every listing still gets read, checked and argued with, and I still read what goes out. What's gone is the waiting. I ask, and by the time I've read the answer to the last thing, the next one is done.

The other surreal part is that it already does anything I need. The next model is coming and it'll be faster, and I don't even know what it could be for. I can't name a task in my week it can't already help with.

## Every model drop is an expansion

I don't know if anyone can relate to this, but it feels like going from vanilla WoW to The Burning Crusade. The gear that dropped at level 62 was better than the gear people had spent months farming. That's how every model drop feels now. A huge power spike in the first few days that puts you level with people who have been grinding the previous model for months.

It's weird. If you start something now, you have until the next model to have a bit of an edge, and when the next wave comes you're immediately behind. So I think you need to save the things you want to achieve and the methods you think are best, written down, so you can run them again on the next model on its first day. That's why every decision on Anchor Terminal goes into a written spec with the reason we took it, and every listing is graded against a checklist anyone can read.

## It isn't only software

Software is where this showed up first, because the work is text and you can check it by running it. I don't think it stays there. Imagine the same month for a solicitor going through a stack of contracts, an accountant closing the books for thirty clients, or a newsroom checking every claim in a story against its source. Most of those hours are reading, checking and writing things down, and that's the part that just got compressed.

## What worries me

Checking becomes the job. On Friday the fastest things were the agents and the slowest thing was me, reading what they made and deciding. When we got lax (and I said that night that we were starting to be), the fix was more checking. A second agent that hadn't seen the code reviewed every change to sign-ins, payments and the numbers, and it caught a serious bug before it shipped.

Claims will outrun checks. Two of the three models we listed that night overstated their own ranking, and the people making the claims have the same tools we do.

The gap gets wider. If two people can do in a month what took ten people two years, I don't know yet what the other eight do instead, and I don't think anyone does.

## What's next

I'm going to keep counting. Two million took two years the first time and a month this time, and I'm curious what the next model does to that.

---

More in [Opinion](https://www.anchorterminal.com/blog/opinion/index.md) · Older opinion [Five new things in agent tooling that nobody compares yet](https://www.anchorterminal.com/blog/agent-tools-nobody-compares-yet.md) · Newer opinion [We already have AI judges, but not at the top courts yet](https://www.anchorterminal.com/blog/ai-judges-not-at-the-top-courts-yet.md)

- Older: [Five new things in agent tooling that nobody compares yet](https://www.anchorterminal.com/blog/agent-tools-nobody-compares-yet.md)
- Newer: [We already have AI judges, but not at the top courts yet](https://www.anchorterminal.com/blog/ai-judges-not-at-the-top-courts-yet.md)
- All posts: https://www.anchorterminal.com/blog/index.md

## References

Read on 31 October 2026.

[1] Anchor Terminal's own request records, as the admin page counted them on 31 October 2026: page views of every kind (people, agents and crawlers) answered 2xx or 3xx since the site started. The first commit is dated 25 September 2026. What the records keep is on the privacy page. https://www.anchorterminal.com/privacy/#visits

[2] Anchor Terminal's pull requests and main branch, counted on 30 October 2026 at 23:45 London time: pull requests created that day (#324 to #351), merged or open, commits on main between 00:00 and 24:00 UTC, and listings whose `listed` date is 30 October. The new listings are on the directory. https://www.anchorterminal.com/tools/

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
