Search creators⌘K
  1. Home
  2. Creators
  3. Mustafa Waseem Yousuf Zai

Mustafa Waseem Yousuf Zai

Mustafa Waseem Yousuf Zai shares practical advice on building SDR teams and hiring for growing businesses, including how to assess sales candidates by their activity and results. Yousuf Zai's posts also explain how to build narrow, no-code AI agents.

7K followersSales hiringAI agentsRecruitingBased on 11 posts · latest Oct 2026
LinkedIn

At a glance

Mustafa Waseem Yousuf Zai is most useful for practical SDR hiring and narrow no-code AI agent advice.

Best for

Sales-assessment, recruiting, or sales-tech campaigns aimed at founders, sales managers, and SMB sales leaders.

Not for

Microsoft Dynamics or enterprise ERP implementation expertise campaigns needing deployment methods and case-study proof.

Key takeaways

  • For SDR hiring, consistency, meeting conversion, and self-tracked activity matter more than corporate pedigree.
  • An AI agent is defined by goal, tools, and ability to check and retry.
  • Keep AI automation narrow, tested with ten real examples, and under human review.

Check first: Confirm audience data beyond their 6,957 LinkedIn followers, plus sponsorship terms, deliverables, and inquiry route.

Main ideas
For lean SDR teams, hire for demonstrated output rather than résumé prestige · Judge an AI agent by whether it can act through a task, not by the label · Keep AI automation narrow, tested, and under human review
Audience
6957 LinkedIn followers
Read first
Unlearning corporate sales hiring for SDR teams
Sources for this section

What they are known for

Mustafa Waseem Yousuf Zai writes about hiring for growing businesses and applying AI to practical tasks.

Their posts turn broad ideas into practical checks.

  • For SDR hiring, they argue that consistency, meeting conversion and self-tracked activity matter more than corporate pedigree, citing a candidate who tracked six months of calls in a spreadsheet.
  • On AI, they distinguish an agent from a chatbot by its goal, tools and ability to check and retry.
  • They recommend a focused build: test ten real examples and have a person review results during the first two weeks.
  • A Microsoft Dynamics recruiting post shows another side of the work: direct hiring calls tailored to technical roles, with workplace humor.
Sources for this section

Ideas and priorities

Across the posts reviewed, Mustafa Waseem Yousuf Zai favors practical tests over labels: judge SDR candidates by evidence of sustained activity, distinguish AI agents by what they can actually do, and start automation with a narrow task and human checks.

Read more

A separate Dynamics hiring post shows a direct, role-specific recruiting style.

For lean SDR teams, hire for demonstrated output rather than résumé prestige

Mustafa argues that startup and small-business SDR roles call for different hiring criteria than corporate sales jobs.

Read more

A lean team needs someone who can handle rejection, manage daily activity, and produce qualified meetings quickly, so evidence of past behavior matters more than a famous employer on a résumé.

The post recommends checking candidates’ calls per day over the previous 90 days, cold-to-booked-meeting conversion, and whether they track their own activity. Mustafa says the best SDR his team placed had no Fortune 500 company on their résumé but had kept a spreadsheet of every call for six months.

Read original

Judge an AI agent by whether it can act through a task, not by the label

Mustafa distinguishes a chatbot, which responds to a message, from an agent that pursues a goal using tools and multiple steps.

Read more

Their three-part test: a goal, tools it can use, and a loop to check results and try again. This puts capability—not terminology—at the heart of what makes something an agent.

The post gives examples of tools such as web search, database queries, and CRM updates, and concludes that a system without the goal, tools, and loop is “a chatbot with a better prompt.”

Read original

Keep AI automation narrow, tested, and under human review

In a second AI post, Mustafa turns the agent idea into a cautious build sequence.

Read more

Rather than automate an entire business, start with one task, connect the automation and language-model steps to a clear destination for the output, and test before using it live. Human review is part of the initial process, not an afterthought.

They suggest qualifying inbound leads from a form as a bounded task, testing the system on ten real examples, and keeping a person in the review loop for the first two weeks. They prefer a working single-task agent to a “do everything” system that fails.

Read original

Sources for this section

Start with their work

Unlearning corporate sales hiring for SDR teams

This answers how to hire SDRs when the corporate sales playbook does not fit a startup or small business.

Read more

See the specific screening criteria Mustafa Waseem Yousuf Zai uses instead of pedigree.

Mustafa Waseem Yousuf Zai contrasts corporate sales hiring with startup and SMB hiring.

  • Corporate teams, the argument goes, hire for logos on a CV and allow 90 to 180 days to ramp because the product sells itself.
  • Leaner businesses screen for whether someone can handle rejection, book qualified meetings by week three, and manage their own pipeline and daily metrics.
  • At Sponto, while building SDR teams for US and Canadian clients, the criteria include calls-per-day consistency over the last 90 days, cold-to-booked meeting conversion rate, and self-reported daily activity.
  • The best SDR they placed had no Fortune 500 logo but kept a spreadsheet tracking every call made over six months.

For brands planning a campaign

For a sales training, recruiting, or sales-tech campaign, make daily activity and conversion the centerpiece rather than brand-name experience. Turn the screening questions into a checklist, assessment, or lead magnet for sales leaders building a first SDR team.

Chatbot versus AI agent: goal, tools, and loop

This explains what separates a real AI agent from a chatbot with a better prompt.

Read more

Newcomers can start here for a plain-language test to evaluate agent products and claims.

Mustafa Waseem Yousuf Zai argues that people use “AI agent” and “chatbot” interchangeably, though they are not the same thing.

  • A chatbot responds to a message; an agent completes a task by looking things up, making decisions, calling other tools, and taking multiple steps without a person clicking next each time.
  • The post gives three requirements for a real AI agent: a goal, tools to act such as searching the web or updating a CRM, and a loop that lets it check its own output and try again.
  • If an “AI agent” cannot do all three, the post calls it a chatbot with a better prompt.

For brands planning a campaign

For an AI platform or automation brand, use the three-part test to help buyers distinguish genuine agent capabilities from chatbot features. A comparison table, demo script, or qualification question can turn this distinction into a practical buying aid.

A minimum path to a no-code AI agent

This explains how to build a working AI agent without writing code.

Read more

See the narrow-task approach and the testing and human-review steps that come before live use.

Mustafa Waseem Yousuf Zai lays out a six-step path for building a working AI agent without code.

  • Pick one narrow task, such as qualifying inbound leads from a form rather than running a whole business.
  • Choose a no-code automation platform such as Make, Zapier, or n8n for the trigger and steps.
  • Connect an LLM API node to read the input and decide what happens next.
  • Add a data step for where the output goes, such as a CRM field, spreadsheet row, or Slack message.
  • Test with ten real examples before turning it loose on live traffic.
  • Add a human-review step for the first two weeks to catch edge cases before they become client-facing mistakes.
  • The closing advice: start narrow, because a single-task agent that works beats a “do everything” agent that does not.

For brands planning a campaign

For a no-code automation or AI tooling campaign, demonstrate one narrow workflow end to end, including the ten-example test and two-week human-review step. That sequence can anchor a tutorial, webinar, or onboarding asset instead of a broad promise about agents doing everything.

Remote Microsoft Dynamics hiring across experience levels

This shows what a remote Microsoft Dynamics hiring push looks like in practice and which roles and experience levels it includes.

Read more

It also shows how Mustafa Waseem Yousuf Zai writes a recruiting call for a technical talent pool.

Mustafa Waseem Yousuf Zai posts a remote hiring call for Microsoft Dynamics professionals with one to twenty years of experience.

  • The roles include developers, functional consultants, technical consultants, solution architects, project managers, business analysts, and support engineers.
  • The post names NAV, AX, Business Central, CRM, and Finance & Operations, and uses insider jokes such as “It works on my machine,” “Let’s check the permissions,” and “Who deployed this to production?” to signal familiarity with the work.
  • It asks readers to tag the “Dynamics person” everyone contacts when something breaks or send a message directly.

For brands planning a campaign

For an ERP, Microsoft Dynamics, or technical recruiting campaign, use role and experience segmentation to widen the candidate pool while keeping the message specific. Insider language and shared work frustrations can make a technical audience stop and respond, especially when the call clearly states location and experience range.

Sources for this section

Topics and approach

Hiring SDRs for output in lean teams

In a post about building SDR teams, Mustafa contrasts corporate hiring for résumé pedigree with startup and small-business hiring for sustained activity, resilience to rejection, and pipeline management.

Read more

They offer concrete screening measures: calls per day over 90 days, cold-to-booked-meeting conversion, and whether candidates track their own activity. They illustrate the point with a placed SDR who kept a six-month call spreadsheet despite lacking a Fortune 500 résumé.

Contrasts corporate and lean-business hiring, then adds a short screening checklist and a placement anecdote.

For brands planning a campaign

Relevant to brands serving sales leaders, recruiters, or growing businesses seeking practical SDR hiring guidance. A campaign could show how to evaluate candidates by evidence of activity and results, rather than résumé logos.

Examples: Source 1

Explaining AI agents through clear distinctions and steps

Two posts distinguish an AI agent from a chatbot by whether it can pursue a goal, use tools, and repeat or check steps without a person prompting each action.

Read more

Another turns that distinction into a no-code build sequence: choose one narrow task, connect an automation platform and language-model API, decide where the output goes, test ten real examples, and add human review for the first two weeks. The guidance favors a bounded task over an agent intended to run an entire business.

Defines terms through contrast, then lays out numbered steps with concrete examples of tools and destinations. Testing and human-review advice offers a practical basis for discussing deployment risk.

For brands planning a campaign

A fit for brands offering AI tools, automation platforms, or implementation support to nontechnical business users. A campaign should demonstrate a narrow workflow and its review process, rather than promise a general-purpose autonomous system.

Examples: Source 1 · Source 2

Recruiting Microsoft Dynamics professionals

A recruiting post invites professionals across a wide experience range and lists roles spanning development, consulting, architecture, project management, analysis, and support.

Read more

It uses familiar troubleshooting lines for humor, then gives remote-work and experience details and asks readers to refer or message candidates.

Pairs a role list and basic job details with workplace humor and a direct referral call to action.

For brands planning a campaign

Potentially relevant to technology employers or recruitment services seeking reach among Microsoft Dynamics professionals. The post offers a candidate-facing, role-led format.

Examples: Source 1

Sources for this section

Brands and businesses

Zai’s posts name Sponto, where they describe building SDR teams for US and Canadian clients, and Microsoft Dynamics as the technology context for a recruiting post.

Read more

Their relationship with Sponto is unclear; ask whether they own or work for the company. Tools such as Make, Zapier, n8n, OpenAI, Anthropic, and Claude appear only as examples in how-to posts, not as brand relationships.

Sponto

Disclosed partnership

Writing about how to hire SDRs, Zai says, “we build SDR teams for US and Canadian clients” at Sponto.

Read more

They list the teams’ screening criteria, including calls-per-day consistency and cold-to-booked meeting conversion. Their relationship with Sponto is unclear; ask whether they own or work for the company.

View example

Microsoft Dynamics

Mention

A recruiting post advertises remote roles for people with 1–20 years of experience in Microsoft Dynamics, including developers, functional and technical consultants, solution architects, project managers, business analysts, and support engineers.

Read more

It names Dynamics products as the technology used in the roles, but does not identify the hiring employer or state a relationship between Zai and Microsoft. Ask who is hiring and what Zai’s role is.

View example

Sources for this section

Topics and similar creators

Mustafa Waseem Yousuf Zai writes short, checklist-driven LinkedIn posts about hiring and AI automation.

Read more

The sales-team posts cover how a lean company should screen SDR candidates, including calls per day over the previous 90 days, cold-to-booked-meeting conversion and whether candidates track their own activity.

  • The agent posts explain what an AI agent is and how to build one without code: start with a single, narrow task, test it on real examples and keep a person in the review loop before it goes live.
  • A recruitment announcement for remote Microsoft Dynamics roles is mainly useful to professionals in that field.
  • Start with the SDR hiring post for sales-team advice, or the two agent posts for a practical automation starting point.
  • For related perspectives, see Tahnee Perry on agent-run revenue operations, David Dokes on AI agent use cases inside ecommerce brands, and Bennett Cohen on search-led growth plays.
SDR team building Sales hiring AI agents No-code automation Recruiting Microsoft Dynamics Step-by-step explainers LinkedIn posts Sales leaders Startups and small businesses Microsoft Dynamics professionals

Tahnee Perry

Both explain how to aim an AI agent at a specific revenue problem, using a numbered method built around a named client example rather than describing the technology in general terms.

Read more

Perry writes from inside revenue operations, rebuilding a single buyer journey, naming a source of truth and measuring recovered pipeline. The posts reviewed here focus on what counts as an agent and how a small team can build its first no-code one.

Read original · Original 2

David Dokes

Both make the case for an agent by showing what it does in production, including its goal, the tools it touches and where a person stays in the loop, rather than treating an AI label as the point.

Read more

Dokes draws on ecommerce and direct-to-consumer brand operations, with agents auditing ad spend, payment failures and attribution models at scale. The agent posts reviewed here are for someone building a single-task automation for the first time.

Read original · Original 2

Bennett Cohen

Both write short posts for growth teams that open with a common mistake, then offer a specific corrective play backed by a client outcome rather than theory.

Read more

Cohen's plays focus on search visibility, keyword choice and measuring AI-search referrals. The overlap is the teaching format; the material reviewed for Mustafa covers sales hiring and agent basics.

Read original · Original 2

Sources for this section

Audience

For a campaign to build an SDR team, this creator is relevant: their LinkedIn posts speak directly to hiring, screening, and managing SDRs.

Read more

They also cover no-code AI agents and remote Microsoft Dynamics recruiting, suggesting their audience may include sales operators, founders, and technical hiring audiences.

  • The only published audience measure is 6,957 LinkedIn followers as of October 8, 2026.
  • To confirm whether the audience includes sales leaders or hiring managers, ask for recent LinkedIn follower analytics by job title, seniority, industry, and geography, plus post-level impressions and engagement for SDR-hiring posts compared with AI-agent posts, and any audience survey results.

LinkedIn followers

6957

LinkedIn account-level metadata attached to the profile; not taken from post text · 2026-10-08

Sources for this section

Partnership options

Mustafa Waseem Yousuf Zai's posts do not state available partnership or sponsorship terms.

Read more

Across four full posts, they provide no sponsorship rate, deliverable menu, content-format specification, exclusivity term, disclosure practice, or official partnership or inquiry page.

  • Instead, they describe services for client and hiring organizations: one post says Sponto builds SDR teams for clients in the United States and Canada, screening candidates on calls-per-day consistency over the previous 90 days, cold-to-booked meeting conversion rate, and self-reported daily activity tracking.
  • A separate post recruits Microsoft Dynamics professionals with 1–20 years of experience for remote roles.
  • These are different arrangements from sponsored placements or co-marketing deals on a creator's own channels.
  • Before allocating budget, ask for the commercial terms and an inquiry route.
Sources for this section

Campaign fit

A campaign to shortlist

Good fit: A campaign for a sales-assessment, recruiting, or sales-tech platform aimed at founders, sales managers, and SMB sales leaders on how to hire SDRs who can book qualified meetings by week three.

Read more

Mustafa Waseem Yousuf Zai is a strong content fit because their SDR post directly answers that need.

  • They contrast corporate hiring for pedigree and a 90–180 day ramp with lean-team hiring for rejection tolerance, self-managed pipeline, and daily metrics.
  • They name concrete screens: calls-per-day consistency over the last 90 days, cold-to-booked meeting conversion, and self-reported daily activity.
  • The placement anecdote about an SDR with a six-month call spreadsheet gives the campaign a usable proof point.
  • The fit is strongest for a checklist, scorecard, or assessment asset.
  • Before budgeting, ask for audience data beyond their 6,957 LinkedIn followers on October 8, 2026, plus sponsorship terms, deliverables, and an inquiry route.

When to choose a specialist

Poor fit: An implementation-focused thought-leadership campaign for a Microsoft Dynamics or enterprise ERP vendor on deployment best practices, measurable business outcomes, and case-study proof, distributed across video and multiple channels.

Read more

The Microsoft Dynamics post is a recruitment call for remote roles at 1–20 years of experience; it lists role types and uses insider humor but does not show implementation methods, client results, or technical depth.

  • This could support a talent-pipeline or employer-brand campaign, but not an implementation expertise campaign.
  • A buyer looking for this should look for a creator with documented Dynamics deployment work and case studies.
A worked campaign example

Worked campaign angle for a campaign aimed at hiring SDRs: 'Hire for output, not logos: the first-five SDR screening scorecard.' The hook comes from the post's central argument — corporate sales hiring criteria do not transfer to a lean SMB.

  • The campaign asset is a one-page scorecard that turns the creator's three screens into interview questions: How many calls did the candidate make per day over the last 90 days?
  • What was their cold-to-booked meeting conversion rate?
  • Do they track their own daily activity before being asked?
  • A companion post or short session walks through the placed-SDR anecdote: no Fortune 500 logo, but a six-month spreadsheet of every call.
  • The call to action is to download the scorecard and use it in the next SDR hire.
  • Before setting the format or budget, ask for pricing and disclosure terms for a webinar, workshop, or paid placement.
Sources for this section

Who else to consider

Tahnee Perry

If the campaign targets sales pipeline automation and revenue operations, Tahnee Perry is a stronger choice.

Read more

Their posts outline a method for using AI agents to find and recover pipeline leakage: rebuild one buyer journey by hand, name a source of truth, build bounded agent jobs and verify results against approved examples.

  • They name Angela Ferrante at Zapier and cite dropping weekly pipeline leakage from the high six figures to the thousands.
  • For a sales-tech or RevOps platform targeting teams that already have SDRs but lose qualified leads between systems, Perry offers a tested approach and named results.

Perry's material focuses on fixing broken sequences after lead generation, assuming a team is already in place. For a campaign supporting SDR hiring and ramp-up, ask for content that covers hiring criteria, screening and onboarding.

Examples: Source 1 · Source 2

Bennett Cohen

If the campaign targets SEO and AI search visibility for a B2B software brand, Bennett Cohen is a better fit.

Read more

Their posts show how to choose winnable keywords by buyer intent rather than chase high-difficulty category terms.

  • Examples include a CRM for solar installers at difficulty 22, comparison keywords and mining customer conversations for exact phrases.
  • They also explain how to measure AI search success through AI-referred traffic, branded/direct traffic, self-reported attribution and manual spot checks.
  • For marketers seeking to rank for niche buyer-intent terms and track AI search, Cohen offers tested tactics and examples.

Cohen focuses on marketing acquisition and search, not sales team building. For a campaign about hiring SDRs or designing a sales hiring scorecard, ask for content that covers SDR hiring, sales team structure or sales management.

Examples: Source 1 · Source 2

David Dokes

If the campaign targets AI agents for ecommerce or DTC operations, David Dokes is a better choice.

Read more

Their posts document 15 production AI agent use cases from DTC brands, including finding non-incremental Amazon DSP spend, auditing Google Ads for junk search terms and spotting a retention dip caused by failed payments.

  • They also show how to build custom attribution models by prompting Claude connected to Polar through an MCP.
  • The examples include a named brand (Valabesas) and a Head of Ecommerce quote.
  • For a campaign targeting ecommerce operators who want to apply AI agents to marketing and operations, Dokes offers concrete methods and outcomes.

Dokes' material focuses on ecommerce and DTC operations, not sales team building or SDR hiring. For a campaign about hiring, screening or ramping SDRs, ask for content that addresses those topics.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Campaign brief: [creator name]

Completed brief: "Hire for output, not logos" SDR screening scorecard

Completed brief: decline and redirect for a Microsoft Dynamics implementation campaign

Sources for this section

Research methodology

  • Mustafa Waseem Yousuf Zai's four LinkedIn posts cover screening SDR candidates for lean teams, recruiting remote Microsoft Dynamics professionals, and AI agents and no-code automation.
  • The posts do not give publication dates.
  • The only audience figure published is 6,957 LinkedIn followers, observed on October 8, 2026.
  • The posts do not include video transcripts, information about other channels, per-post engagement data, or sponsorship terms.
  • The posts do not say how the audience breaks down by job title, seniority, industry, or geography.

Brands they talk about