Where a rep’s week goes
Ask a rep where last week went and “calls” is rarely the first answer. It went on account research, on copying a LinkedIn thread into Salesforce so the deal record stops lying, and on digging one procurement email out of a hundred. Each is a few minutes of clicking that ought to come out identical every time, which is asking a lot of anyone at 6pm on a Thursday.
dassi takes that work in each rep’s own browser, on the accounts they’re already signed into, and the CRM and Gmail need no integration. A rep teaches it a job once, in plain English or by doing it while it watches, and it saves that as a workflow to run on demand or on a schedule. We’d set one hard rule on day one: nothing goes to a prospect, and no deal changes stage, until the rep has seen it.
6,238 companies, fifteen rows
Lead lists are pure clicking, and they’re where I’d start. In one run we recorded, the instruction was a single paragraph asking for fifteen early-stage B2B fintech companies that are hiring, from the Y Combinator directory, with name, one-liner, batch, team size, location, website and open roles. dassi opened the directory (6,238 companies), ticked Fintech and Is Hiring (165), kept batches from Winter 2025 on (31), screened those for B2B, and read fifteen company pages. Three and a half minutes, no empty cells.
One row bothered me. Freya is tagged Fintech in the directory, and its one-liner says “Voice AI for Enterprises.” I’d drop it. Someone selling a different product might keep it, which is exactly why I’d rather it sat in the sheet for a person to squint at than got quietly filtered by a model. The lead list page has the rest. YC’s directory is unusually tidy. I’d expect more blanks from an association member list, though I haven’t timed one.
The CRM, the inbox and a first week
After a call or a LinkedIn exchange, dassi can find the contact in HubSpot or Salesforce, create it if it’s missing, write what was agreed and set the follow-up date. It will also sort the inbox each morning and draft the “just following up” notes. Teams that sell into communities can have it work saved searches and subreddits daily. And the Friday forecast, pulled out of the CRM into a manager’s sheet, is the sort of recurring admin that can run on its own at 3pm.
The first week works best with one rep and the CRM logging. On Monday the rep logs two LinkedIn threads while dassi watches and says which fields matter; on Tuesday dassi logs the rest and the rep checks each record. Save the workflow once the corrections stop, then schedule it for 5:30pm to sweep the day’s threads in before the rep leaves. The next rep can read those instructions, which are plain English, and set up the same job in an afternoon.
LinkedIn, Reddit and the logged-out CRM
LinkedIn is the one your sales ops lead will ask about. It caps weekly invitations and its user agreement restricts automated activity, so dassi works there at a person’s pace, sends no connection requests in bulk and doesn’t scrape profiles at scale. Reddit communities set their own rules on self-promotion, and a drafted reply that breaks them should stay a draft.
Scheduled runs need the rep’s browser open when they’re due. If the CRM has logged out, dassi signs in with what Chrome’s password manager fills in, and SSO or two-factor prompts go to the rep. Whatever page content a job needs goes to the model provider you chose, through dassi’s relay on plans with credits.
What it costs per rep
Free credits to try dassi, good for 7 days. No card required. After that it’s $10 a month on the Developer plan with your own API key, or $25 to $300 a month on a plan with credits included. A rep building lists all day uses far more than one logging five calls, and a week with one rep will show which of those your team is before anyone writes a purchase order.