Built for every kind of link team

It arrives as a prospect, usually in a CSV of a few hundred rows from a backlink tool export. Bulk qualification runs the mechanical checks: does it resolve, is it indexable, does the language match, how many outbound links per page, and optionally the authority and traffic estimates if you are spending metric credits. Whatever survives becomes a supplier domain with a score and a status.

Then it gets a contact, or several, stored on the supplier record rather than in someone's address book. Outreach happens against that contact using a template with merge variables, and every send is logged with a date, which is the field that stops a teammate emailing the same editor next week. Follow ups queue automatically and stop the moment a reply arrives.

When terms are agreed, the deal gets typed. This is the step that determines whether your reporting means anything later: reciprocal, three way, ratio, insertion, guest post, or paid are genuinely different obligations, and collapsing them into one schema is how pipelines start lying. If the deal involves a return link, that obligation is created at the same time and starts aging immediately.

The placement goes live and becomes a monitored link. From then on it gets checked on your plan's cadence for presence, anchor match, rel attribute, indexability, and whether the source page still resolves. A failed check creates an alert, and a lost link drops into a recovery queue with the partner contact already attached, which is the whole reason the contact lives on the supplier record instead of in your inbox.

Everything above rolls into two views. The project dashboard and client report, scoped to one client or product line, and the workspace rollup that sums across all of them. That second view is the one that catches the shared partner, the aggregate over-give, and the duplicate outreach, none of which are visible from inside a single project.