Before you generate a single email or proposal, you need a reliable sales co-pilot — an AI assistant you have configured with your context so every answer is grounded in your deal, not a generic template. In this first lesson you set that co-pilot up once and reuse it for the entire course. Treat this as foundational plumbing: ten minutes here saves you from re-explaining yourself in every later prompt.

Why a configured co-pilot beats ad-hoc prompting

A raw chat with Claude or ChatGPT knows nothing about your product, your buyer, or the MENA market you sell into. Every prompt then wastes tokens and effort re-establishing context, and the output drifts generic. A configured co-pilot stores that context once, so your outputs are sharper, more consistent, and far faster to produce. The difference between a beginner and an expert AI user is rarely a clever one-off prompt — it is a well-prepared, reusable workspace.

Step-by-step: build your co-pilot

  1. Pick one AI tool you have access to — Claude (Projects), ChatGPT (a Project or Custom GPT), Microsoft Copilot, or Gemini. Any works; this course is deliberately tool-agnostic.
  2. Create a dedicated workspace named after your deal, e.g. Red Sea Bank — Core Renewal. Keeping one workspace per deal stops contexts from bleeding into each other.
  3. Write a system / custom-instructions block describing your role, product, ideal customer, and constraints. Keep it under 300 words — precision beats volume.
  4. Attach reference files: your one-pager, pricing sheet, and any past proposal. The co-pilot now answers from these instead of guessing.
  5. Save the role text somewhere reusable so you can paste it into any new chat that lacks persistent projects.

Ready-to-use prompt

You are my B2B sales co-pilot. I sell [PRODUCT] to [BUYER TYPE]
in the MENA market (mostly Egypt and the GCC). Buyers are often
bilingual; default to English but be ready to switch key terms to
Arabic (e.g. عرض سعر for "quote", عقد for "contract").

Always: be concise, commercially specific, and avoid hype.
When I describe a deal, ask me up to 3 clarifying questions
before giving a full answer. Reference the files I attach.

A second prompt to validate the setup before you trust it:

Summarise back to me, in 5 bullet points, what you now know
about my product, my buyer, and my market — so I can correct
anything before we start.

Try it

Create your workspace, paste the role prompt, attach at least one real file, then run the validation prompt. Read the co-pilot’s five-bullet summary and correct every wrong assumption — this is the moment to catch a misunderstood product or buyer. You now have a co-pilot that genuinely knows your deal. Keep this workspace open; every later lesson builds on it.

Next