Claude Projects for Dubai Business Owners — 7 Real Projects to Set Up This Week

A Claude Project is a persistent workspace: custom instructions, an uploaded knowledge base, and every conversation inside it, all grouped together so you're not re-explaining your business every time you open a new chat (Claude Help Center). Free accounts get up to 5 Projects; paid plans raise the file capacity and Project count, and on Team/Enterprise, Projects can be shared across your whole staff (Claude Help Center).

Most owners I train never get past the default chat window. That's the gap. Here are seven Projects worth building this week, with what to upload, what to put in the custom instructions, and what to keep out.

1. Customer FAQ knowledge base

Upload: your actual FAQ document, refund policy, and 10-15 real past customer email exchanges (with names removed).
Instructions: "Answer only from the uploaded files. If the answer isn't in them, say so — don't guess."
Don't upload: live customer records with contact details.

2. Weekly content calendar

Upload: last quarter's published posts, your brand voice notes, and your content pillars list.
Instructions: "Generate a week of post ideas per pillar, in [your] voice, with one CTA option per post."
Don't upload: unpublished competitor intelligence you didn't gather yourself.

3. Contract review assistant

Upload: your standard vendor or client contract template, plus a one-page list of clauses you always flag (payment terms, termination notice, liability caps).
Instructions: "Compare any new contract against this template. Flag deviations. Do not give legal advice — flag for a lawyer's review."
Don't upload: unsigned contracts with live commercial terms from an active negotiation — treat those as confidential and keep them out of any third-party tool until signed, or use with extreme caution and your own legal sign-off.

4. Competitor research tracker

Upload: public information only — competitor pricing pages, published case studies, LinkedIn posts you've screenshotted.
Instructions: "Track positioning shifts over time. Summarize what changed since the last upload."
Don't upload: anything obtained through a source that isn't public (an ex-employee's inside info, a leaked deck).

5. Meeting prep

Upload: the agenda, the other party's public LinkedIn/company profile, and notes from your last interaction.
Instructions: "Give me 5 questions I should ask and 3 objections I should expect, based on the uploaded context."
Don't upload: internal salary or margin data unless the meeting is internal and access-controlled.

6. Arabic-English translation style guide

Upload: a glossary of your brand's approved Arabic terms, past translated marketing copy, and notes on tone (formal Gulf Arabic vs. conversational).
Instructions: "Translate using the uploaded glossary first. Flag any term not in the glossary before inventing a translation."
Don't upload: anything containing customer personal data alongside the translation samples.

7. Financial summary

Upload: anonymized or aggregated monthly revenue/expense summaries — not raw bank statements with account numbers.
Instructions: "Summarize trends month over month. Flag anomalies over 15% variance. Do not treat this as tax or audit advice."
Don't upload: bank account numbers, IBANs, or anything with your Emirates ID or passport number attached — redact before uploading, every time.

The one rule across all seven

Anthropic's own guidance is that concise, one-to-three-page documents outperform one long dump file (Claude Help Center), and on paid plans Claude automatically extends usable knowledge-base capacity through a RAG mode once you're near the limit. So don't over-upload — curate the files, keep sensitive data out entirely, and let the custom instructions do the constraining.

How to sequence the setup, realistically

Don't build all seven in one sitting — you'll rush the instructions and end up with generic outputs. A realistic week looks like this:

• Day 1-2: Customer FAQ base and Contract review assistant — these are the two most owners reach for first because they solve an immediate, repeated task.
• Day 3: Content calendar and Meeting prep — lower-risk, quick to test, immediate feedback on whether the outputs are useful.
• Day 4-5: Competitor research and the Arabic-English style guide — these benefit from a few days of accumulated uploads rather than a one-time dump.
• End of week: Financial summary, once you've decided exactly what to redact and how to aggregate the numbers before anything goes in.

Why most owners stop at one Project and never build the rest

The honest reason isn't lack of value — it's that the first Project takes 20 minutes to set up properly and the payoff isn't obvious until the third or fourth time you reuse it. A one-off chat feels faster in the moment. A Project only proves its worth after a week of repeated use, which is exactly the point most owners give up before seeing it. Block 20 minutes per Project, test it on a real task the same day you build it, and the value becomes obvious fast.

Reviewing what you've built

Once you have three or four Projects running, do a monthly 10-minute review: which ones did you actually open this month, and which custom instructions produced outputs you had to heavily rewrite? Delete or rebuild the ones that aren't earning their place — a Project with stale reference files gives worse answers than no Project at all, because it's confidently wrong instead of honestly uncertain.

Figures current as of July 2026 — Project limits and RAG capacity are subject to change; check Claude's Help Center for the current numbers before building at scale.

Beyond the first seven

Once these seven are running, the same pattern extends to almost any repeated task in your business: an onboarding checklist Project for new hires, a supplier negotiation Project that tracks past pricing conversations, a course-feedback analysis Project if you sell training or content. The setup logic doesn't change — curate the reference files, write specific instructions, keep sensitive data out. What changes is which recurring task you're pointing it at. The seven above are simply the ones that apply to nearly every Dubai SME regardless of industry; your business likely has two or three more that are specific to what you actually sell.

A closing checklist before you start

Before you build the first Project, write down two things on paper: which category of data is genuinely off-limits for any AI tool in your business (this list should already exist if you've thought about it — if it doesn't, that's the first thing to fix), and who in your business is allowed to add new Projects or connect new files. Small businesses skip this because it feels like overkill for a two-person team. It isn't — the habit is easier to build when the stakes are low than to retrofit once you've scaled to five Projects and three staff members using them daily.

None of these seven Projects require technical skill to set up — every step is uploading a file and writing a paragraph of plain-English instructions. The barrier isn't ability, it's the 20 minutes most owners never quite get around to spending. Block the time this week, build one, and the rest tend to follow once the first one proves its worth.

I walk through this exact setup — live, project by project — inside the Claude Masterclass. If you want the structured version instead of building it from scratch, start there.