SUDA / سُدى / AHMAD RASAS
From brand texture
to a useful workflow.
I designed a fictional identity and products, created imagery, a film, campaign and training materials, and built a knowledge/enquiry desk.
Try the demo ↗
THE PROBLEM
Policies change. Answers should follow.
Brief hypothesis: repeated delivery, returns and availability questions can produce stale replies. Editable evidence and explicit review help staff work from one source.
Research rationale: MoDEE household data supports mobile access; Novajo provides a service-clarity precedent. Workflow need remains a hypothesis for customer interviews. RESEARCH.md ↓
MY CONTRIBUTION
Designed, built and tryable.
- Bilingual knowledge with visible source IDs
- Intake, draft, review, approval and resolution
- Identity, creative assets, campaign proposal and training
Names, records, prices and products are fictional. No client feedback, sales or advertising returns are claimed.
From the application I built
ORIGINAL CREATIVE
An identity. A collection. A finished film.
Original imagery made with imagegen, with authored design and motion editing in HyperFrames. The film combines generated still imagery, typography and motion; it is not fully generated video.
Silent promotional motion film · 12 seconds · fictional brand. Uses the previous collection imagery.
A campaign proposal, not a campaign result.
Goal: generate qualified enquiries about the fictional SUDA collection in Amman. Audience hypotheses: adults in the serviceable delivery area who value practical everyday pieces; compare a broad local audience against a relevant clothing-interest hypothesis only if the account allows it. These are assumptions to test, not known buyers.
Proposed structure: one Leads campaign with a website enquiry conversion location, one local ad set and three creative variants. Before launch verify the actual account’s available conversion locations/performance goals, business-owned Page/ad account, permissions, payment method, consent requirements, approved destination and delivery capacity. If website enquiry measurement is unavailable, review an Instant Form setup rather than treating traffic clicks as leads. No account or campaign was created.
Everyday texture
Pieces that find their place in your day. Explore the sample SUDA collection.
نَسج من يومك. اكتشفي مجموعة سُدى التجريبية.
A clearer choice
See the material, size and availability before you ask. Meet SUDA.
الخامة والقياس والتوفّر واضحين قبل السؤال. تعرّفي على سُدى.
Ask with confidence
Delivery and returns in one place. Ask a question and get a reviewed answer.
التوصيل والإرجاع بمكان واحد. اسألي وخلي الرد يمرّ بمراجعة الفريق.
Assumed test scenario: 14 days at 10 JOD/day (140 JOD total), subject to approval and account billing/tax. Keep audience, landing page and offer consistent; vary the creative angle. Record delivery and early quality for 3–4 days before decisions. Define a qualification rubric (serviceable location + genuine product question + consent to follow up). Compare qualified enquiry rate and cost; investigate delivery/landing problems before reallocating. This sample budget is not an estimate of profitable spend or expected results.
Measurement plan: separate landing views, enquiry starts, submitted enquiries, staff-qualified enquiries and fulfilled orders. Only a real successful enquiry submission may map to Lead after provider verification; only a real completed paid order may map to Purchase with actual value/currency. A WhatsApp click is interest, not a lead or sale. Use consistent UTMs and a provider that supports them, plus consent and documented attribution windows. Never send draft text, names, phone numbers or demo records to analytics. Browser/server duplicate events would require a shared event ID if both are introduced. No Meta Pixel or campaign measurement is connected.
Dependencies/costs: actual media spend and billing terms; hosting/database and staff operations; an optional model’s selected-model token rates; official messaging tariffs if separately authorized. Exact Meta/WhatsApp tariffs and account capabilities are not verified here. Confirm current official rate cards and permissions before quoting integration costs.
A small business-needs audit
Information
Put product identifiers, material, sizes, stock and policies in one maintained source. Agree who owns updates. The catalogue and editable source cards demonstrate the handoff.
Enquiries
Use a single queue with a category, owner/review responsibility and a visible next status. Start with the form intake shown here. Do not assume Instagram/WhatsApp access.
Marketing
Explain the product before asking for action. Test the three angles against a consistent offer and separately record enquiry quality. No growth guarantee.
Launch
Prepare identity/profile assets, domain/hosting ownership, an approved business email address, SPF/DKIM/DMARC and account access. Email/domain/social setup is proposed; no mailbox, DNS or account was created.
Operations
Production needs authenticated staff, server-side storage, backup/retention, audit trails and a knowledge update process. Add AI only after source quality and review duties are working.
Before a client pilot: measure current weekly enquiry volume, response time, repeated-question share and staff correction rate. Interview and observe with consent. Compare the same definitions after the pilot; this demo does not invent a baseline or improvement.
Practical staff exercise · 30 minutes
Open the retail demo and reset sample data. Search “returns” and “delivery in Amman”; write the source IDs and current rules.
In Edit knowledge, change the English AND Arabic returns period from 7 days to 10 days. Search again. Confirm the new rule appears with the same source ID and a higher revision.
Create an enquiry: “Can I return an unworn piece after 9 days?” Prepare source extracts, edit a concise answer that cites K-returns, submit for review, approve and resolve. Nothing is sent.
Ask “Do you offer a lifetime warranty?” The correct response is an explicit unknown; no policy should be invented.
Draft a bilingual reply for an unavailable Clay scarf using P-03. State the recorded availability; do not promise a restock date. Refresh the page and verify the task state.
Use only the supplied source excerpts below. Draft a concise [Arabic/English] reply to [question]. Cite each source ID. If the information is missing or contradictory, say what needs staff verification. Do not promise stock, delivery, refunds or dates beyond the evidence. Sources: [paste current excerpts].
راجع المسودة التالية مقابل المصادر المرفقة فقط. حدّد كل معلومة غير مدعومة، وأي سياسة قديمة أو تناقض. أعد صياغتها بالعربية الواضحة، واذكر معرفات المصادر. لا ترسل الرسالة. السؤال: [السؤال] المصادر: [المقتطفات] المسودة: [النص]
Checking guide
Checking guide: initial returns evidence is 7 days; after your edit it must be 10 days in both languages. K-delivery distinguishes Amman from other Jordan locations and excludes international delivery. P-03 begins with 0 units; no restock date exists. Warranty has no supported answer. For the 9-day example after the edit, the return window condition is met, but unworn/tags and staff inspection still apply; never promise an automatic refund.
- Question and language understood
- Current source IDs and revision checked
- Stock, price, timing and policy conditions match evidence
- Unknowns stated; no invented promises
- No unnecessary personal data
- Draft reviewed by staff; approval recorded
- Resolution does not imply delivery or sending
Use prompts in an approved tool with safe data only. This application has no model connection.