What leadrack is

leadrack is a kanban CRM for leads that fills itself. It differs from a normal CRM in two ways. A fleet of agents sweeps public sources and puts scored leads on your board every day. And everything is API-first, so anything a teammate can do to a lead, an outside agent can do too, with the same operations and the same paper trail.

The board

The main surface is a board. Columns are pipeline stages: a few come with sensible defaults, and all of them can be renamed and reordered. Cards are leads. Drag one between columns, or let an agent move it through the API. Both are the same operation underneath, and both show up on the timeline.

Pipelines

A team can run several pipelines (outbound and partnerships, say), each with its own stages. A lead lives in exactly one stage of one pipeline. Stages are addressed by key, like new or contacted, which is what agents use when they move cards.

Cards and contacts

A contact is a person or company: email, name, title, company, domain, plus whatever custom fields you define. A card is that contact's place in a pipeline. The same contact can have cards in several pipelines, but one pipeline holds at most one card per contact. Adding the same email twice converges on the existing card instead of creating a duplicate.

Typed custom fields

Contact and card fields are typed (text, number, url, email, date, select, checkbox) rather than free text. When an agent pushes enrichment data in, it lands in a predictable shape you can filter and sort on.

The timeline

Every change to a lead is logged on its timeline, whether a person or an agent made it: who added it, which agent scored it and why, who moved it, what was sent. Nothing happens to a lead silently.

What stays human

Pipelines, stages, and custom fields are configured in the app by a person. Agents operate within the structure you define. They don't redefine it.

Next up: Your first agent.