My Morning Call List: Claude, Albacross, Attio and Slack

Every morning a full call list lands in my Slack before my first coffee: the right companies, the right people, and why each one is worth a call today. Here's the exact setup I run, built on three connections between Claude, Albacross and Attio.

In 5 Sales Plays Orchestrated by Claude, Attio and Slack, we showed how Claude can run the Albacross rules of thumb for a whole sales team.

This one is more personal. It's the setup I use myself, as the person who picks up the phone.

The goal is simple. I don't want to open five tabs to decide who to call. I want one list, ready when I start, with everything I need to make a good call.

You don't need more data. You need it in one place, in front of you, at the moment you're ready to act.

How the setup fits together

Albacross brings the signal, Attio holds the memory, Slack is where I work, and Claude connects them.

The numbers match the three connections below. Calls I make are logged back into Attio, so tomorrow's list already knows about today.

Connection 1: Claude to Attio, so every company record is complete

Attio is my memory. If something happened with an account, it should be on the record. Claude makes sure it is.

With Claude connected to Attio, I can keep company records complete without typing them up by hand:

• Call notes: after a call I tell Claude what happened in a few words, and it writes a clean note on the right company.
• Tasks: "follow up with Bart on Friday" becomes a task with a due date, assigned to me and linked to the account.
• Email context: Claude reads the latest thread in Gmail and logs the outcome, for example who owns the renewal and who to talk to next.
• Company basics: domain, location, industry, size, owner and renewal date sit on the record, so Claude can check them before anything reaches my list.

When the record is complete, every later step gets smarter. Claude can't filter, rank or brief on what Attio doesn't know.

Connection 2: Albacross to Attio, new leads exported by buyer persona

Albacross tells me which companies are on our website. The Attio integration exports them into Attio automatically, so nothing waits for a manual CSV.

The key is what gets exported. I don't want every visitor. I want the companies that fit, and the people inside them I'd actually call. So the export is built around buyer personas:

1. Set the persona in Albacross. Define the roles you sell to, for example Head of Sales, Marketing Director or RevOps lead, plus the seniority and departments that matter.
2. Filter for fit. Limit the export to your ideal customer profile: country, industry and company size.
3. Export to Attio. New matching companies land as records, with the persona contacts attached, ready for Claude to work on.

The export decides who enters my world. Getting the persona right is the difference between a list I call and a list I ignore.

The output: a full call list in Slack, every morning

This is the part I actually see. Every weekday morning, a scheduled Claude task runs before I start and posts my call list to Slack.

Before anything reaches the list, Claude checks it against Attio. Existing customers, open deals owned by someone else and companies I spoke to this week are left out, or flagged instead of listed.

Each account on the list comes with:

• The company and why it's on the list today: a pricing visit, a return visit or a fresh ICP match
• Who to call: the persona contacts from the Albacross export, with title and phone number where available
• What we know: the last note, email or call from Attio, in one line
• An opener: one or two sentences to start the call, based on the pages they viewed

When I've called someone, I reply in the thread. Claude logs the call as a note in Attio and creates the follow-up task.

I don't decide who to call any more. I decide how to open the call, and that's the part that should take my time.

Connection 3: Claude to Albacross, the one that works best for me

The first two connections move data on a schedule. This one lets me ask questions directly.

On 17 November we launch the Albacross MCP, which connects Claude straight to Albacross. Instead of building a segment or opening a dashboard, I just ask:

• "Which companies in Sweden looked at our pricing page this week?"
• "Has the company I called on Monday been back on the site since?"
• "Find three companies like our best customer that visited in the last 30 days."

Claude pulls the answer from Albacross, checks it against Attio, and gives me something I can act on right away.

That's why this is my favourite. The morning list covers the routine. The MCP covers everything I think of during the day, without breaking my flow.

The best tool is the one you can ask a question in plain words, and get an answer you can act on in the next five minutes.

Keep a human in the loop

This setup does the legwork. The conversations stay mine. A few rules I stick to:

• Claude drafts, I call. Openers are a starting point, never a script.
• Write to your own fields. Let Claude add notes, tasks and lists in Attio rather than overwrite core company data.
• Tune the persona first. If the list feels wrong, fix the Albacross export before you touch anything else.
• Stay compliant. Albacross identifies companies, not individuals, and is GDPR compliant. Keep your outreach to the same standard.

Final thoughts

Three connections, one routine:

1. Claude to Attio keeps every company record complete.
2. Albacross to Attio brings in new leads that match my buyer personas.
3. Claude to Albacross answers any question about website demand, in plain words.

Put together, they give me a full call list in Slack every morning, and a way to dig deeper whenever I need to.

Identifying companies is only the start. The win is starting every day knowing exactly who to call and why.

Want this setup for your own team? Book a demo and we'll walk you through Attio, Slack and the new Albacross MCP.

‍