Athena already has a page that says it sits on top of the Workday a company runs, with permissions and processes unchanged. That removes the hardest objection a new US brand faces, ripping out the HRIS, and gives the BDR a specific, checkable reason to write.
First action
Pull 50 US job posts this week that mention Workday and a People Ops or HR helpdesk role.
How to measure it
Positive replies from the Workday list
- Now
- –
- Target
- 5% of contacts
- By
- 6 weeks
Steps
Define the slice
US, 500 to 5,000 people, Workday in job posts, at least one open People Ops, HR ops or HRIS role.
Founding US BDR 2 hours
Build the list
Use job-post search and enrichment to reach 200 accounts with the Head of People and HR ops lead.
Founding US BDR 2 days
Write the sequence
Three touches: the Slack-to-Workday request, the 80% of requests answered claim, a 20-minute demo on their own top five questions.
Founding US BDR 1 day
Load it with tracking
Tag the list "Workday layer" in HubSpot so replies are measured separately.
GTM Engineer 2 hours
Send in two waves
100 accounts, review replies, rewrite the weakest touch, then the second 100.
Founding US BDR 2 weeks
Hand over hot replies
Same-day handoff to the Founding US AE with the account's Workday notes.
Founding US BDR ongoing
Share what worked
A one-page summary of which titles and lines replied, for the team lead and Marketing.
Founding US BDR 1 hour
Run this outreach. The sequence sent for you: addresses found and verified, replies routed to your CRM. Usually live within days.
Book a working sessionWhy it works
Build a list of US companies of 500 to 5,000 people that run Workday (job posts that mention Workday, HRIS analyst roles) and are hiring People Ops, HR helpdesk or HR systems roles. Write a three-touch sequence led by the Workday page: "your employees ask in Slack, Athena does it in Workday".
The BDR's job is to test best-fit customer profile hypotheses through live outreach. "Workday customers drowning in HR tickets" is the sharpest hypothesis Humaans can test this week, and it does not depend on brand recognition.
Ready to use
EmailFirst touch for Workday accounts
Subject: Workday, from Slack
Hi {first_name},
Saw {company} is hiring for {role}. Most of that role's week is answering the same questions and filing the same Workday requests.
Athena sits on top of the Workday you already run. Employees ask in Slack or Teams ("can I take Friday off?") and Athena does it in Workday with your existing permissions. Nothing to migrate.
Worth 20 minutes to see it answer your five most common HR questions?
{sender}Risks and how to handle them
Workday customers have long contracts and IT gatekeepers
Lead with no change to Workday and offer a Slack-only pilot on one agent.
Wrong-fit accounts dilute the test
Keep the slice narrow and record why each lost account was not a fit.
Evidence
- Athena sitewithathena.ai/workday: "The AI operating layer for Workday." "Athena sits on top of the Workday you already run... no forms, no logins, no opening Workday. Your permissions, processes and governance stay exactly as they are." The demo request reads "I want to take a week off in August" and "your holiday request has been sent to Workday".Source
- HiringFounding US BDR - Agentic AI (San Francisco): opens Athena's first US opportunities, will "Test our best-fit customer profile hypotheses through live outreach", experiments with "messaging, positioning, channels and creative approaches", and reaches HR, Finance, Operations, AI and Transformation leaders; activity volume is explicitly not the goal.Source
- HiringFounding US Enterprise Account Executive - Agentic AI (San Francisco): "we're expanding into the US from San Francisco. This role is about bringing Athena AI Agents there first." Owns the first wave of US customers, closes "$100k+ ARR opportunities" with senior HR, Finance, Operations and AI leaders, sells "outcomes rather than features", and is warned off if they "rely on strong brand recognition to open doors. We're still establishing Athena in the US".Source