About

We build monitoring infrastructure for the outside world.

Zipf gives teams and AI agents programmable web monitoring with judgment. Consumer tools send notifications. Zipf delivers scored, structured signals to your systems.

The goal is simple: know what changed before the rest of the market does, without forcing your team to spend its day re-checking the same sources.

Mission

Build the monitor, not just the query.

Zipf exists for teams that need ongoing awareness, not occasional lookup. The work is to stay current without forcing people to watch the web by hand.

The fewer things that matter, the wider you have to look.

Zipf's Law shows up everywhere on the web. A tiny fraction of updates drive real outcomes, but you cannot know which fraction without watching broadly. That is the paradox the company is named after.

The problem

No team can watch every source that matters.

The old model of search, scan, repeat was built for humans clicking through lists of links. It breaks down when the question is recurring and the surface area keeps expanding.

The work is not finding one answer once. The work is staying current without asking people to live in tabs.

The product

Zipf turns search and crawl primitives into monitoring infrastructure.

We build monitors that watch the web with judgment. They check the sources your team would normally look at by hand, extract the fields you care about, score every change for information gain, and compare each run against what mattered before.

Search and crawl are primitives. The product is the infrastructure layer on top: programmable monitors with structured output, signal scoring, and delivery to any system — Slack, webhooks, CRM, or AI agents via MCP and API.

The team

We come from search, retrieval, and production systems that operated at web scale.

The founding team built search and LLM systems at Microsoft Bing, Snowflake, Neeva, Amazon, Walmart, Qualtrics, and Mendel.AI. We have published dozens of papers, hold dozens of patents, and shipped systems handling billions of queries daily.

The company

Curiosity is required. Burnout is not.

We are serious about the work and equally serious about building it at a sustainable pace. Zipf should compound over years, which means hiring people with real lives and giving them room to keep them.

Beliefs

What we optimize for.

These are not marketing claims. They are the operating choices behind the product, the company, and the kind of work we want to compound over time.

01

Breadth before precision

Power laws demand watching widely before filtering narrowly. The vital few signals emerge from the many, so you cannot skip the haystack and keep the needle.

02

Operators should control the system

Teams and agents need to define sources, extraction targets, schedules, and delivery paths with precision. Monitoring infrastructure should be programmable and transparent, not a black box that decides what matters for you.

03

The monitor matters more than the query

A useful system remembers what it is watching, what changed last time, and where the answer should go next. One-shot retrieval is the starting point, not the destination.

04

Structured outputs beat raw links

If someone still has to open ten tabs to understand what happened, the job is not done. The output should already carry the fields, context, and delta that matter.

05

Threads and looms, not crystal balls

We are not in the prediction business. We pull threads from across the web, compare them with discipline, and help teams read the resulting pattern with confidence.

06

Research has to survive contact with production

We value deep technical work, but only if it ships. The best idea is the one that keeps working under customer load, messy inputs, and real operating constraints.

Team

Meet the people building Zipf.

Daniel Campos

Daniel Campos

Profile
  • Built web-scale search and LLM systems at Microsoft, Neeva, Walmart, and Snowflake after too much time in school at UIUC, UW, and RPI.
  • Proud father of three. Always glad to talk search systems, biological and electronic intelligence, restoring old houses, coffee and wine, and hunting.
Charlie Schwartz

Charlie Schwartz

Profile
  • Built ML platforms, video-to-video search, and other high-availability backend systems at Amazon Prime Video after studying economics and computer science at Vanderbilt.
  • Previously scaled Kubernetes and AWS infrastructure at Red Ventures. Enjoys distributed systems, production ML, cloud infrastructure, mountaineering, golf, and poker.

Location

New York City base. Hybrid by default.

We are based in NYC and open to hybrid and remote work. If you are in the neighborhood, come say hello.

Office

368 9th Ave

New York, NY 10001

Skip to main content
About | Zipf AI