A researched list of prospects every week.

Under the hood

The agent is built to work from an ideal-customer profile written with you as rules it can check, not a loose description: sectors in and out, a size range, the towns you cover, and the signals that make a business worth contacting now, such as a new branch or a job advert. It also carries your exclusions: existing customers, competitors, and a do-not-contact list that only grows. Each run is a batch with its own id, so a restart picks up where it stopped.

Under the hood

The agent searches public business listings and reads company websites with tools that can fetch a page and do nothing else. Each prospect is stored with the page it came from and the date it was read. Results are de-duplicated by website and trading name, then checked against your CRM, so a business already in your pipeline is not found twice. Contact details are kept only where the business itself publishes them for enquiries.

Under the hood

The language model tests each prospect against the profile rule by rule and returns a structured verdict: pass, fail or unknown for each rule, with a quote from the source page as evidence. The verdict is checked against a schema. A prospect goes forward only if it passes every required rule; an unknown on a required rule drops it rather than letting it through on a hunch. Dropped prospects are kept with their reasons, so you can see what the rules exclude.

Under the hood

The brief and the draft are written from the pages collected in the search, and nothing else. Each claim in the message, such as a new branch or a service they offer, is linked to the page it came from; a claim with no source is removed before you see the draft. The message says who you are and why you are writing, carries no false urgency, and ends with a plain line telling the reader how to ask not to be contacted again.

Under the hood

Approval is per message, not per batch, and it is a permanent rule, not a setting for the first weeks. The approval screen shows the draft next to the brief and the source pages, so a claim can be checked in one click. What you reject, and why, is logged, and those reasons tune the profile rules for the next run. Whether a business should be contacted at all is your decision: the agent only proposes.

Under the hood

Messages are sent from your mailbox under a daily cap you set and spaced through working hours. Just before each send, the address is checked again against the do-not-contact list, because someone may have opted out since you approved. Each send carries an idempotency key (a unique id for that message), so a retry after a dropped connection cannot send it twice. A bounced address is recorded and never tried again.

Under the hood

Each prospect is written to your CRM with its brief, sources, message and approval. Replies are read from your inbox and attached to the right prospect by the email thread they belong to, then sorted as interested, not now, or asking not to be contacted. A reply it cannot sort with confidence pauses all contact with that business until you have read it. The agent does not answer replies: a conversation with a real prospect is yours.