Noor El-Sayed

Running a design studio: pricing, scope and clients

Founder of a nine-person brand and product design studio · 11 years of pricing, scoping and choosing clients

Synthetic expert — a composite written by Avva as a worked example. Not a real person.

Synthetic demo

Eleven years running a nine-person brand and product studio: four hundred projects priced, eleven clients fired, equity and spec work refused, and one very large gambling rebrand turned down in a bad quarter. The calls below are about what to charge, what to exclude, and whom to work with.

Which clients to take and which to refuse, how to price a project, a rush and a retainer, what a deposit tests, when scope becomes a change order, chasing late invoices, when to fire a client, agency versus in-house, and what a portfolio is worth.

Taking or refusing a clientPricing and ratesScope and change ordersPayment and deposits

Updated September 2, 2026

Calls Noor El-Sayed actually made

2 of 62 decisions in this model, in their own words. This page prints them in published order — it has no way to know your situation. Your agent receives them ordered against it.

  1. A funded startup asked the nine-person studio for a full brand and website in five weeks, budget $60k, with a launch date set by a conference.

    Take it at $85k with a scope written as what is excluded — no product UI, two rounds on identity, one on the site — or decline. Five weeks is a premium, not a discount.

    A rush costs the whole team's evenings and the next client's start date. If the client cannot pay for that, the deadline is their problem, not ours.

  2. An inbound lead opened the first call by asking for a 30 percent discount 'to build the relationship'.

    Decline politely. A client who negotiates on the first call negotiates on every invoice.

    How someone treats the price is how they will treat the work. The relationship they want to build is one where we are cheap.

How Noor decides

What their model weighs first, and what you can hand your agent to ask. Avva writes no verdict: your agent reads Noor El-Sayed’s material and answers you.

What this expert weighs first

Price the outcome, never the hourMUST WEIGH
First-call behavior predicts the engagementMUST WEIGH
The team is the studioMUST WEIGH
Scope is what is excludedALSO WEIGH
Payment is a test, not a termALSO WEIGH
Take the work that points where you are goingALSO WEIGH
Portfolio is revenueTIE-BREAKER
Values have no priceTIE-BREAKER

All 8 are listed here. What each one looks for, plus stop rules and context switches, arrives when your agent asks. This is a reference model, so it answers in full to everyone — no key, nothing held back. A real expert’s model answers a caller without a key with a slice of itself, and in full with a free key.

What you can ask them

  • Check this before I commitA full pass over a plan or a draft
  • Which of these two?A call between options, their stop rules checked first
  • Anything here they would reject?A quick scan against their hard lines
  • What should I settle first?The questions they ask before choosing an approach
  • Is this even their field?Where their judgment applies, and where it stops

Each returns a protocol to follow, not a finished answer. Where the model disagrees with generic best practice, the model wins.

Connect Noor El-Sayed to your agent

The connector works now, with no key. This is a reference model, so it answers in full to everyone — no key, nothing held back. A real expert’s model answers a caller without a key with a slice of itself, and in full with a free key. The standing note is what keeps Noor El-Sayed getting asked.

You remember to ask

One URL, no key

Paste it as a custom connector. It works now and returns the complete published model.

https://avva.chat/mcp/design-studio-noor-el-sayed

You have to remember to ask your agent to use it.

Your AI remembers

A standing instruction

A line in CLAUDE.md, AGENTS.md or GEMINI.md makes your agent consult Noor El-Sayed without being asked.

Finish setup ↓

Catches the decisions you would not have thought to ask about.

  1. Add the connector

    Pick where your agent runs, then paste the line below. It connects without a key, and a reference model answers in full either way.

    https://avva.chat/mcp/design-studio-noor-el-sayed

    Settings → Connectors → Add custom connector. Works now and returns the complete published model — this is a reference model, so nothing is held back. A real expert’s model answers without a key with a slice.

    A real expert’s model answers a caller without a key with a slice of itself, and in full with a free key. Here a key buys only a higher daily limit. The key appears once, in this tab only, and anyone who has it shares that limit.

    One work email so we know who is using the beta. It is stored separately from the key — never joined to it, or to anything your agent asks. No account, no card. We send the key there too, so closing this tab does not lose it.

  2. Make it standing

    This is the point of the product. Paste it once into CLAUDE.md — or wherever this client keeps project instructions. Your agent then works under Noor El-Sayed’s rules the whole way: it asks their questions before locking an approach, gates drafts on their stop rules, and reviews against their bar before anything ships. Not a one-off second opinion.

    # CLAUDE.md — standing advisor (Avva: Noor El-Sayed) For running a design studio: pricing, scope and clients work: - Early in a task, call `expert_questions` before locking an approach. - Use `red_flag_check` as a cheap gate on drafts/diffs. - Before finalizing a significant decision, call `review` with context + proposal; follow the returned protocol exactly — the model wins over generic best practice. - For A/B choices, call `compare_options` (hard stops apply before scoring). - Unsure this domain applies, call `about_expert`. It states what a packet costs, so budget with the real number rather than guessing. - Not on mechanical work: renames, typo fixes, formatting, questions of fact, or anything trivially reversible. Once per decision, not once per message. - Err toward calling. A packet you did not need costs some context; a decision finalized without one is the failure this advisor exists to prevent. If `review` returns "reject", revise before proceeding. Coverage labels describe approved-decision breadth, not predictive accuracy.

    Or try a single review first

    Paste this in your next message once the connector is in. One decision, one protocol.

    Use the Avva expert Noor El-Sayed before we finalize this. What we're deciding: <paste your plan, doc, or diff here> Call the review tool with that as the proposal, follow the returned protocol exactly, and give me the verdict and any required changes before you continue.

    Not legal, medical, financial, or other professional advice. Terms of Use

What this is
  • Written by Avva. A reference model — a worked example so you can see what a published model looks like and connect an agent to one. Labelled Demo wherever it appears.
  • Not a real person. The name is invented and the record is a composite, authored in one consistent voice. No real expert's positions were copied.
  • Same protocol. Your agent receives it exactly as it would a real expert's model: the cases, the forces, the fitted order, the stop rules.
  • Steps aside. When a real expert publishes in this domain, this model leaves the shelf.