Book the first meeting
Who to call this week, and why now
Real Canadian companies, each with a public event from the last three months that gives a reason to call. Every event links to its source. Pick an account to open its call sheet.
Scoring weights
Recency fades from full marks at 0–21 days to a fifth at 90 days. Event strength ranks how directly the event creates a technology decision. Size fit favours 50–1,000 employees, the usual range for a new-customer sales team.
| # | Account | Why now | Days ago | Score |
|---|
No accounts match. Clear the search or pick another province.
Discovery questions
Likely objection
Voicemail under 20 seconds
Follow-up email
Six touches, ten business days
Follow-up cadence
One unanswered call is not a no, so every account gets the same six-step sequence before it is set aside. Dates skip weekends and Ontario statutory holidays.
By day
Activity against target
Dial log
Log each calling block: dials, connects, conversations and first meetings booked. The funnel shows where calls drop off, and the pace line shows whether this week's meeting target is on track.
| Date | Dials | Connects | Conversations | Meetings | Connect rate | Remove |
|---|
Delete every logged block in this browser?
How this was built
Method and limits
I built this to practise the work of a cloud sales development rep: research an account, find a reason to call, open in thirty seconds, ask good questions, hand clean notes to a seller, and keep calling until the meeting is booked.
Where the accounts come from
- Each account has one public event (an expansion, acquisition, funding round, new digital service, leadership hire, grant or contract) dated between and . The event links to the press release or news story it came from.
- Companies were left out if their own public material says they are customers or partners of a major cloud provider, if they sell IT services, or if they have more than about 5,000 employees.
- Employee counts appear only where a source gives one. Otherwise the page says "unknown".
- The page names job titles to call, never individual people. The only names shown are executives named in the event itself.
How the call sheets are written
The opener, discovery questions, objection, voicemail and email are built from the event type and the account's own event. They are starting points to rehearse and rewrite, not finished scripts. The "hypothesis to test" is a guess about the business problem, written to be confirmed or dropped in the first conversation.
What this page does not know
- Which cloud provider, if any, each company uses today, and whether it already has a sales relationship with one.
- Any internal CRM data, territory assignment or qualification method used by a real sales team.
- Real call results. The dial log holds only what you enter, in this browser. Until you log a block it shows a made-up sample week, labelled as such.
Tools
Built with Claude Code. Research used public web sources, each checked against its page. The page is plain HTML, CSS and JavaScript with no libraries.
Independent student project by Abdullah Al Mneni (Business Technology Management, Toronto Metropolitan University). Not affiliated with, endorsed by or built for Amazon Web Services or any company listed here. No one listed here has been contacted through this project.