The Exclusions Are the Part Worth Reading
A brand commissioning work in Japan asks for a quote and gets back a document with an unfamiliar shape. Not a list of deliverables with a number beside each one. Something closer to an argument: here is the objective, here is the set of things that objective requires, and here — stated plainly, in its own section — is what this does not include.
The last part is the one worth slowing down for. A list of exclusions is not a disclaimer. It is the part of the document that says where the work stops.
This is our own position, and the pages that state it are ours, so treat what follows as a description of one way of scoping rather than a claim about the right way. The cost of doing it this way is in the last section.
Why the list does not carry a number
Our services page puts the reason in three sentences:
We do not price each deliverable separately. We define the objective, then propose the set of touchpoints that objective requires. Anything outside that set is named as outside it.
The first sentence is a refusal, and it needs the second to make sense. A deliverable list can be priced item by item only if the items are independent — if the value of each one does not depend on which other ones exist. That holds for commodities. It does not hold for the pieces of a launch, where a set of five touchpoints designed together is a different object from the same five specified separately, and where the sixth one either finishes the set or is decorative.
Our capability page makes the same point from the other end:
These are capabilities, not a menu. We assemble what a single business objective requires — and say what it does not.
A menu invites addition. You pick items and the total goes up. A set does not work that way: adding to it or removing from it changes what the rest of it is doing. So the question a quote has to answer first is not what would you like but what is this for — and until that is settled, no list can be the right length.
The distinction is not a Japanese one, and this piece is not describing a national practice. It is simply easier to see from outside a market than inside one. A buyer who cannot read the market personally has no way to judge whether a list is the right length — and an explicit exclusion is one of the few parts of a proposal that can be checked without that reading.
What naming the outside actually looks like
Stating a principle about exclusions is easy. Printing them is not, because each one is a place where a reasonable buyer might have assumed otherwise.
The page carries four offers, and two of them have a section for this of their own. The one for a paid digital pilot is headed What it is not:
Not a full production system. Not 24/7 operations. Not a guarantee of AI output accuracy. Large-scale development is a separate contract, entered with eyes open.
The one for an ongoing partnership is headed What it excludes:
Unlimited revisions. Same-day turnaround. Media spend, venue and vendor costs. Large rebuilds, film production, events and system development are scoped separately.
Worth noticing: the offer that states the scoping principle is not either of these. It has a section called How we scope it and no exclusion section at all. What covers it is a fourth block, printed once at the foot of the page after all four offers — and that block does not split the world in two.
It has three headings. Under We lead:
Market and audience context. Brand localization. Creative production. Space and experience. Launch operations. Local production partners and their management.
Under We coordinate with partners:
Media buying. PR. E-commerce operations. Logistics. Legal and regulatory compliance.
And under We do not take on:
Sales representation. Distribution. Import licensing.
The middle band is the one whose meaning is least obvious from outside. It is not the band where partners appear — the first band ends with local production partners and their management, so partners are in both. The split is by function, not by whether someone else is involved, and coordinated is neither done by us nor not our problem. A buyer who reads it as either is reading something the page did not say.
The sentence that follows the third band says why the page is built this way:
We would rather tell you this before the first meeting than after the contract.
Read the exclusions as answers to questions nobody asked out loud. Unlimited revisions is there because a buyer used to a retainer might assume it. Media spend is there because the line between making the work and buying the placement is invisible from outside. Not a guarantee of AI output accuracy is there because the question has only recently become one a client thinks to ask.
Each of those lines costs something to print. It closes a door that vagueness would have left ajar, and a vague scope is easier to sign. That is the trade the format makes: it is harder to agree to and harder to be disappointed by.
The exclusions describe the seam, not the wall
There is a second reason to read the excluded list closely, and it is not a commercial one.
An exclusion tells you that a piece of work exists and that this contract does not cover it. Media spend, venue and vendor costs are not absent from a launch — they are absent from this agreement. Somebody will still buy the media and pay the venue. The exclusion is the map of what has to be held elsewhere.
That is the same boundary we looked at from the other side when nobody holds the space between contracts: each supplier delivering exactly what was signed, and the assembly belonging to no one. A named exclusion does not solve that. It does something narrower and still useful — it makes the unassigned part visible while there is still time to assign it.
Our own capability page describes the shape of the gap it is trying to close:
Consultants deliver a deck. Production studios deliver files. The gap between them is where launches lose their shape.
And the arrangement it uses to avoid holding capacity that a given objective does not need:
Bilingual project leadership in Tokyo. Named responsibility on every engagement. Specialist partners assembled per project rather than kept on payroll — which is why the team fits the work instead of the other way around.
The phrase that matters there is the last one. A team kept on payroll has to be given work; a team assembled per objective has to be justified by one. Both arrangements have a direction of pull, and the exclusions are where the second one’s pull becomes legible: if a capability is not required, it is not in the set, and the document says so.
What this way of scoping costs
The format has a real cost, and it lands on the buyer, not on us.
An objective-led scope moves as a whole. If the objective changes in month two — the launch date shifts, the target audience is revised, a channel is added — the set does not adjust by one line item. It is re-derived. A deliverable-priced quote absorbs that kind of change by adding or removing a row. An objective-led one has to be re-argued, and re-arguing is slower than adding a row.
It is also hard to compare. Three deliverable lists can be laid side by side, because they are lists of the same kind of thing. Three objective-led proposals cannot, because each one has interpreted the objective slightly differently and derived a different set from it. A buyer running a competitive process has to compare arguments rather than totals, and that takes a kind of attention a procurement process is not usually built to give.
And it moves the decision upstream of the approval process. A deliverable list can enter an internal approval with numbers attached while the objective is still being argued internally. An objective-led scope cannot: the objective has to be settled before there is anything to approve. For a buyer whose organization approves spend before it agrees on purpose, that ordering adds a step rather than removing one.
Those are not edge cases. They are what the format asks for in exchange, and a buyer who wants a list of rows priced separately is not making a mistake — they are buying something this shape does not sell.
The two questions a quote can answer
Set the two side by side and the difference is not quality. It is which question the document is built to answer.
A deliverable-priced quote answers what will I receive. It is precise about objects and silent about whether the objects add up. An objective-led scope answers what is this meant to achieve, is precise about the boundary, and asks the buyer to accept that the object list is derived rather than chosen.
Neither is the correct form. But only one of them prints the exclusions, and the exclusions are where a buyer who cannot read the market for themselves can still see the edge of the work.
The exclusions are worth reading before the itemization. They are short, and they are the part that had to be decided rather than assembled. A quote with nothing named as outside has not put its edge anywhere a buyer can find it, and that absence deserves more attention than any line in the list above it.
Sources: Studio INTERPLAY, Japan Readiness Sprint and capabilities pages. Quotations are verbatim from those pages as published on 11 September 2026. This article describes our own scoping practice and cites our own material; the section on what the format costs is there because the rest of it is not disinterested.