How to write a Khamsat proposal that wins without sounding like a catalog reply

Khamsat is built around services: fixed packages, clear tiers, predictable deliverables. That is a strength until you treat every buyer request like a button that auto-fills your gig description. Buyers can tell in seconds when your reply is a catalog paste. They wanted someone who read their request, not someone who broadcast the same offer to twenty people.

This guide is for the moment you have a live Khamsat request open and you need a proposal that sounds human, specific, and hireable without rewriting your entire storefront.

How Khamsat buyers skim (and what they punish)

Most buyers on Khamsat are not reading like an editor. They scan the first lines, look for whether you understood the task, check price and timing, then compare two or three sellers. Arabic and English mix depending on the buyer; clarity beats flair.

They punish three signals quickly:

1. Generic opener that could apply to any category (“I am professional, high quality, fast delivery”).
2. Gig mismatch where your reply describes a package that does not match what they asked.
3. No proof tied to their niche (random portfolio links with no sentence explaining relevance).

If you have ever wondered why a strong gig still loses custom requests, start with why clients ignore your proposals. The same skim logic applies; Khamsat just adds package culture on top.

The catalog reply trap

The trap looks like this: you have a polished gig page. A buyer posts a custom need. You paste the gig intro, change the buyer name, and hit send. It saves time. It also trains the buyer to think you will not adapt scope.

Catalog replies fail because custom requests usually include at least one of these:

• A constraint your default package does not mention (tool, deadline, industry, file format).
• A deliverable count different from your tiers.
• A question they expect answered in the first message.

Your job in a custom proposal is to show you noticed the difference. One paragraph of mirroring plus a short plan beats a long list of gig features.

A structure that works on custom requests

Use this order every time. Swap details from the request; keep the skeleton.

1) Mirror the outcome in plain language

Restate what they want in one or two sentences. Use their words where possible (landing page, logo, montage, Shopify fix). If the post is vague, say what you are assuming and invite correction. That pattern is the same muscle as writing when the job post is basically empty, but on Khamsat you still have gig context: do not let the gig replace reading the request.

2) Name what is included and what would change the price

Buyers want boundaries. Three to five bullets is enough:

• Deliverables you will hand off (files, formats, rounds).
• What you need from them before you start (content, access, examples).
• What is not included unless they add it (extra pages, rush, source files, ads setup).

You are not writing a contract. You are preventing the “I thought that was included” argument later.

3) One relevant proof line

One example beats ten links. Tie it to their industry or deliverable type:

Last month I built a similar product page for a Saudi skincare brand: mobile-first layout, Arabic RTL, and checkout in under ten days.

If you are newer, use a smaller honest proof: a student project, a volunteer build, a partial case with metrics you can defend. Beginner proposals without case studies covers that posture without fake authority.

4) Clear price and timeline hook

Khamsat buyers compare numbers early. Give either a fixed quote for a defined slice, or a first milestone with a number. If scope is unclear, price the discovery step:

To quote the full build fairly, I would start with a 30-minute scope confirmation (fixed [X]) then send a locked price for milestones.

5) One easy reply question

End with a question they can answer in one line: deadline, preferred style link, or whether they already have hosting.

Example: design request that does not match your top gig tier

Buyer request (summary): Logo refresh plus social kit, wants files in AI and PNG, deadline in one week, budget mid-range.

Weak catalog-style reply:

Hello, I offer professional logo design with unlimited revisions and fast delivery. Check my gig for packages. I am expert designer with 5 stars.

Stronger custom reply:

You need a logo refresh and a small social kit (profile and cover sizes), with AI and PNG sources, within about a week. I would treat this as one brand pass, not a full identity system unless you want that added.

Included in my offer: one main logo direction, two revision rounds on the chosen direction, and exported PNG plus AI for the agreed sizes. Not included unless you ask: brand guidelines booklet, animated logo, or extra platform sizes beyond the list you send.

I recently refreshed a logo for a local restaurant chain and delivered social sizes in the same week; I can share before/after in chat if useful.

For your timeline, I can deliver first concepts in 3 days if you send your current logo and two reference styles you like. Fixed price for this scope: [amount]. If you also need packaging mockups, tell me and I will adjust.

Do you already have brand colors locked, or is color exploration part of this job?

Notice what changed: outcome mirror, scope box, one proof, price with conditions, one question. No gig dump.

Example: development or automation request

Technical buyers on Khamsat often paste half a spec. Mirror the stack they named. State what you will verify before coding:

You want a Zapier flow from Google Forms to Notion plus email alerts when status is “urgent.” I would map fields first, build a test form submission, then turn on the live zap.

Included: one zap, tested with your accounts, short Loom handoff. Not included: cleaning historical spreadsheet data or building a custom web app unless you scope that separately.

I have connected similar form-to-Notion flows for small agencies; typical build is 1-2 days after access.

Fixed price [amount] if the form has under 15 fields. If you have multiple forms or conditional branches, reply with a sample form link so I can confirm.

Arabic tone notes (without sounding stiff)

Many buyers appreciate clear Modern Standard Arabic or light Gulf/Levant tone depending on your brand. Rules of thumb:

• Short sentences beat formal essays.
• Put numbers and deadlines in Western digits if that is what the buyer used.
• Avoid empty praise (“honored to serve you”) unless that is genuinely your brand voice.
• If you write in Arabic, keep technical terms consistent (موقع، متجر، تعديل) so they do not think you are guessing.

Bilingual sellers can open in the language of the request and offer English deliverables where relevant.

Mistakes that make you sound like a bot

Mistake	Why it hurts	Fix
Opening with your star rating	Buyers already see stats	Open with their task
Listing every gig you sell	Looks unfocused	One service line tied to request
”Unlimited revisions” on rush jobs	Sounds risky	Name revision rounds
Ignoring budget hints	Wastes both sides	Acknowledge range or ask one scope question
Ten portfolio links, zero explanation	Skim killer	One line of relevance

Pre-send checklist

• First two sentences mention their deliverable, not your gig title.
• Scope includes at least one “not included” line.
• Price or first milestone has a number (or a priced discovery step).
• One proof example matches their category.
• No em dash characters anywhere (use commas or periods).
• Run the proposal checklist for tone and clarity.

FAQ

Should I link my gig in the proposal?

Yes, if it helps them see samples, but after you have customized the message. Lead with the custom plan; add the gig as “full packages here if you want compare options.”

Do I lower price to win custom requests?

Sometimes, but do not race to the bottom on unclear scope. Shrink deliverables or offer a smaller first milestone instead of the same work for less.

What if they only want my cheapest tier work?

Confirm deliverables match that tier. If not, quote the tier that fits or decline politely. Underpricing custom work is how Khamsat becomes exhausting.

Can I reuse the same proposal skeleton?

Reuse structure, not sentences. Reusing across similar jobs explains how to vary openings so buyers do not see duplicate phrasing.

Closing

Khamsat rewards sellers who look organized on the gig page and thoughtful in the inbox. Custom requests are where thoughtful wins. Mirror the request, box the scope, show one relevant proof, and make the next reply easy.

If you want a faster first draft while keeping your voice, Lervos can help you generate a Khamsat-shaped offer from the buyer text so you spend your time on scope and pricing, not on fighting a blank box.