How we scope: paragraph to fee letter, four days.

Discovery, as most agencies practise it, is a way of billing a client for the time it takes to decide whether you want to work with them. We do not do that.

The Creative Mantra scoping loop has one shape and one clock. A paragraph arrives at hello@creative-mantra.com; a founder acknowledges it inside 24 hours; a fee letter goes out inside four working days. Then the client decides.

We have run this loop for the whole 45+ case studies documented in our brochure. It works for a two-week UI sprint. It works for a nineteen-week management-system build. It works for an agentic AI product that has to book real freight loads inside real margin floors. The shape does not bend.

The problem: discovery is where engagements go to die.

Most agencies open with a discovery workshop. Two weeks. Six calls. A Miro board. A PowerPoint. An invoice. At the end of it, the client knows less about their own product than they did when they wrote the first email — because they have spent ten hours answering questions that were never really about their product, but about de-risking the agency's proposal.

We think discovery is the studio's problem, not the client's. If we cannot read a paragraph and figure out whether we can build it, that is a signal about us, not about the brief. So we moved discovery inside the four days it takes to write the fee letter, and we stopped billing for it.

The loop.

Here is the shape, in order.

1. Paragraph inbound. A prospective client writes to us — usually four to eight sentences describing what they want to build, for whom, and why. Sometimes it is longer; sometimes it is one line. Both are fine.
2. 24-hour acknowledgement. A founder reads it, replies inside a working day, and either asks the single most important clarifying question or confirms we are drafting a fee letter. We do not send an auto-responder; we send an answer.
3. Four-working-day fee letter. The studio drafts a one-page scope, prices it, names the dedicated relations officer, and proposes a kickoff date. It goes to the client as a real letter — not a portal login, not a Google Doc with tracked changes, not a fifty-slide deck.
4. Client decides. Sign it, negotiate it, or walk. If it is signed, the named relations officer runs point from that day forward; if it is not, we part on good terms and often see the client again a year later on a better-fit brief.

What goes into a Creative Mantra fee letter.

Six things, in this order, on one page.

• Scope one-pager. What we are hired to build, and for whom. Written back in our words, so the client can catch us mis-reading them before the engagement starts.
• Milestones. The dated ones the client will actually feel — first design review, first working build, launch — not the internal ones we manage against.
• Price. One number, or a small ordered list of numbered tiers when the scope has a natural fork. No time-and-materials fog.
• Exclusions. The things this fee does not cover — third-party licences, migration data cleaning, marketing copy — written up front so nothing is a surprise in month three.
• Named relations officer. A person, by name, with a photo and an email. Whoever it is, they are the one the client will actually talk to for the length of the engagement.
• Kickoff date. Not "when you are ready." A specific week we are holding.

What we do not need up front.

Three things we are frequently asked to require, and do not.

Designs. If the client already has a Figma file, great; if not, we scope the design work as part of the engagement. Asking a client to arrive with finished designs is a way of asking them to have already hired a different studio.

Tech stack. Unless the client has an existing platform we are extending, the stack is our call. Fourteen years of receipts have earned us the right to make it. Next.js, PHP + MongoDB on AWS, Magento, Shopify, Umbraco on ASP.NET, .NET-based CMS behind a native iOS app — the shape of the product should choose the stack, not the other way around.

Timeline. The milestone dates in the fee letter are ours to propose, based on scope. If the client has a hard deadline, they should tell us; if they do not, we should not manufacture urgency.

"If we cannot read a paragraph and figure out whether we can build it, that is a signal about us, not about the brief."

How the shape works across three price points.

A $10k UI sprint. Two to four weeks. One relations officer, one designer, one developer. The fee letter names a shipped artefact — a redesigned funnel, a mobile-tuned checkout, a component library — and a launch date. No retainer, no discovery, no ambiguity.

A $60k management system. Twelve to twenty weeks. The engagement typically covers a role-based console, one or two API integrations, an admin surface, a mobile app for the field team, and a hosting plan. The fee letter breaks the price into three milestones tied to the shipped artefacts, and it names the exclusions loudly — data migration, third-party licences, on-site training — because those are where a $60k engagement quietly becomes a $90k one at other studios.

A $150k AI product. Six to nine months. Now the fee letter also names the model choices, the cost envelope per active user, the human-in-the-loop guardrails, and the audit-trail policy. The scoping loop stays four days; the letter gets denser. The client still sees one price, one relations officer, one kickoff date.

When we say no.

We turn down roughly one in five briefs that make it to the fee-letter stage. Three reasons, in order of frequency.

Bad-faith briefs. A prospective client who is fishing for pricing to negotiate with their existing agency. It shows up quickly — the paragraph is too specific about the deliverable and too vague about the business — and we are respectful about declining, because we would want the same courtesy from a studio the other way around.

Undefined outcomes. The brief describes a technology, not a job to be done. "We want to add AI" is not a brief; "we want to reduce the six hours a day our AR coordinator spends on inbound freight email" is a brief. We push back on the first and scope the second.

Fake urgency. Sometimes urgency is real — a compliance deadline, an investor commitment, a campaign launch — and we work with it. Sometimes urgency is a negotiating posture. We can tell the difference by the second reply, and we do not sign the second kind.

The numbers.

The median time from paragraph inbound to fee letter out, across the last twelve months, is about 2.7 working days. The commitment is four; the practice is faster. Eight in ten fee letters we issue convert into a signed engagement — the ratio has stayed roughly stable for the last five years, which tells us the scoping loop is doing the right filtering on both sides.

If you are considering sending us a paragraph, this is what happens next. A founder replies in a day. A fee letter follows in four. A named relations officer arrives with it. That is the whole process, and it is the same whether you are shipping a UI sprint or an autonomous freight-brokerage agent.

Write the paragraph. We will do the rest.