Every issuer, and the relationship behind it.

One record per issuer that joins the relationship to the work: who at the bank owns it, who at the issuer takes the call, what was discussed, which mandates came from it, and the documents and figures that support every fact. It is a CRM built for the way a public finance desk covers issuers, not a sales pipeline adapted to it.

Your CRM records what a banker typed. Issuer intelligence starts from the issuer's own documents and the desk's own work, then ties each fact to where it came from. It can write activity back to the CRM you already run, so the firm keeps one system of record and the desk gets the evidence beside it. See how the desk runs it. For the platform comparison, see Starch vs Microsoft Copilot.

No. The coverage list and the deal book stay in the formats the group already uses. Starch reads them, keeps them current and flags what changed, rather than asking the desk to maintain another sheet.

From the issuer's filings and official statements, the group's own portals and documents, and the activity the desk already produces. Every figure carries its source, so a banker can open the page a number came from before using it.

Against the group's own criteria: mandate history, outstanding debt, upcoming calls and maturities, rating changes and how recently the desk spoke to the issuer. The score is a prompt for a conversation, not an instruction to call.

Yes. Approved activity is written back to the firm's CRM, and the issuer record links to it rather than competing with it. Nothing is written until a person approves the update.