A case study concept Riyadh · GCC

Sheryar Ali Khan

Great infrastructure deserves a growth engine.

This page shows three things, in order: a working automation I built, my plan for the first 90 days, and where I would start.

See the automation ↗ The 90-day plan ↗

A plan and a working prototype.

01 / The automation

Which accounts should Sales chase this week?
And what should they say?

First: proof I can build. Sales teams lose hours deciding which accounts to chase and what to say to each one. This small system does that homework - running today, shown below.

BUILT WITH Google Sheets Apps Script

01 / FIND

Find the accounts

GCC banks, lenders and fintechs with dated public signals - hiring sprees, product launches, new leadership. Every record sourced.

02 / SCORE

Rank the priorities

Google Sheets formulas score product fit, signal strength and access. The best accounts rise to the top on their own.

Google SheetsApps Script

03 / DRAFT

Draft the angle

For each top account, AI drafts the angle - why them, why now. A human reviews every word.

ChatGPTClaude

04 / HAND OFF

Hand it to Sales

Contacted accounts get stamped, follow-ups dated. One view exports straight into HubSpot.

HubSpot
Also hands-on with Apollo Clay Make Zapier n8n Airtable ElevenLabs Canva lemlist Twilio
Account Pulse tracker: GCC target accounts with dated public signals
Accounts ranked by fit score, each with a drafted outreach angle
Live scoring formulas: product fit, signal strength, access feasibility, fit score out of 100
Installed Apps Script: custom menu plus automatic status-change stamping

THE WORKING PROOF OF CONCEPT

Account Pulse

What Sales would get every week: a ranked list of GCC accounts, each with its fit score, the public signal behind it, and a ready outreach angle.

Working prototype

02 / The first 90 days

Learn fast. Ship faster.
In parallel.

Second: the plan. How I would spend the first 90 days - learning the product and shipping real work at the same time.

1

DAYS 1–30

Absorb, then move.

LEARN

  • Product immersion: I would sit down with the product team and learn.
  • Brand audit: I would audit and absorb the brand.

EXECUTE

  • Weekly Sales sit-downs: 5 named accounts at a time.
  • First 50 accounts mapped.
  • HubSpot foundation shipped: routing, follow-up, weekly report.
Live HubSpot foundation · 50 accounts · 3 automations · 1 dashboard
2

DAYS 31–60

Systemize.

LEARN

  • Where deals stall, in the team's words.

EXECUTE

  • One live lending ABM pilot.
  • A different story per seat.
15 accounts · approved sequences
3

DAYS 61–90

Scale what works.

LEARN

  • What produced real conversations.

EXECUTE

  • Double down. Cut the rest.
  • Write the playbook the next person could run.
Scale, fix or stop · a repeatable playbook

ILLUSTRATIVE PLAN

Learn vs Execute, by phase

Where the effort sits as the 90 days progress.

Days 1–3060 / 40
Days 31–6050 / 50
Days 61–9030 / 70
LearnExecute

ILLUSTRATIVE PLAN

The automation ramp

What is live by the end of each phase.

1
workflow live
day 30
2–3
workflows running
day 60
Playbook
+ reporting loop
day 90

Every week: one Sales review, one product deep-dive, one shipped improvement.

All numbers are proposed targets, to agree with Sales.

“Real artists ship.”

— Steve Jobs

03 / Where I would start

Three opportunities
I see from outside.

Third: where I would start. Three opportunities.

01

Turn one-off research into an always-on engine

Good research and publishing should be done on a weekly basis.

FIRST MOVE · DAYS 1–30

One asset becomes a founder post, a page series, a Sales one-pager and a nurture sequence.

Cadence · engagement · sourced meetings

02

Make the proof as strong as the platform

From outside: one detailed partner story. Buyers need numbers.

FIRST MOVE · DAYS 31–60

Document 2–3 outcome stories with Sales and Product. Feed the ABM sequences.

Stories shipped · proof in live deals

03

Wire every event into the pipeline

The experience vision exists. The engine around it is not visible.

FIRST MOVE · NEXT EVENT

Pre-show account mapping, 48-hour automated follow-up, HubSpot attribution.

Meetings · opportunities · cost per meeting

04

Build the GTM for Saudi first

Stitch is Saudi. The buyers are Saudi. The go-to-market should feel built here, not adapted here.

FIRST MOVE · DAYS 61–90

Saudi-first messaging and Arabic-first assets, with one local proof point in every campaign.

Saudi meetings · asset engagement · sourced pipeline

05

Run one motion, not four campaigns

Event, report, case study and digital marketing each stand alone. They should be one motion.

FIRST MOVE · NEXT EVENT

One event feeds a report, a case study and the digital push, in sequence.

Assets per event · engagement · sourced meetings

Sheryar Ali Khan

LinkedIn ↗ sheryarakhan1234@gmail.com