Why exclusivity matters

The arithmetic

Three map pack positions exist for a given query in a given place, and one first organic result. If an agency represents two firms competing for them, every position one client gains is a position the other did not get. No management process resolves that; it is the structure of the result page.

Agencies holding competing clients usually describe the accounts as separated: different teams, separate data, no shared strategy. The separation may be entirely real, and it does not address the problem, because the conflict sits in the search results and not in the office.

The effect on effort

The subtler consequence is worse than the obvious one. An agency serving two competing clients has no incentive to push either past the other, because the gain is cancelled by the loss and the second client's complaint costs the same as the first's.

The stable outcome is both clients mid-table and both retained. Nobody has to act in bad faith for this to happen; it is simply where the incentives settle.

What to ask

• Which other criminal defense firms in this metro are current clients?
• Would you sign a second defense firm in my market while I am a client?
• Will you put that in writing, naming the metropolitan area rather than the city limits?
• If exclusivity is offered, is it a paid upgrade or a standing rule?
• How do you define the market: municipal boundary, metro, or something else?

The answers worth noticing are the qualified ones. Exclusivity offered as a paid upgrade puts a price on the conflict without removing it, and tells a firm its competitor could buy the same protection. Exclusivity defined nationally by practice area permits two defense firms in one city as long as they are in different states, which permits exactly the conflict the question is about.

What counts as one city

A promise about cities is empty until somebody says where one ends. The working boundary is the metropolitan market a firm competes in, which is the area its prospective clients search from and the area a grid scan covers.

Two firms fifteen minutes apart in the same metro are competitors, whatever the municipal lines say. Adjacent metros are separate, since the courts, the searches and the competitor sets differ. That is a judgement call, which is why the claimed market should be stated explicitly and in writing at the outset.

The publisher's own rule

SBD Marketing takes one criminal defense firm per city and will not sign a second in a market where it already represents one. There is no premium tier that removes the restriction. A firm enquiring about a taken market is told so and declined, without a waiting list implying the incumbent might be displaced.

That rule caps the agency's revenue per market at a single retainer, which is the cost that makes it worth anything. It is also falsifiable: a firm that later finds SBD Marketing representing a direct competitor in its own market has a concrete complaint. The same question should be put to SBD Marketing as to anybody else.

Chapter assignment

The assignment for Why exclusivity matters is to turn the chapter's advice into a decision record that states the firm's market, scope and present constraint. Begin with the question that caused the reader to open this chapter. Write it in one sentence and name the person who can approve the answer. The chapter premise is: An agency that represents two competing defense firms in one city is choosing between them. This chapter explains why that is arithmetic rather than ethics, and what question to ask any agency before signing.

For Why exclusivity matters, define completion before doing the work. A task is complete when the firm can inspect the changed asset, recover the starting state and repeat the check without relying on memory. Activity counts and dashboard labels do not satisfy that rule. The retained deliverable is a dated assumption sheet and the next question to resolve.

Set up the working file

Create the Why exclusivity matters folder under the market and observation date. Put the baseline or source copy first. Add a short manifest that names the asset owner, operator, approver, measurement unit and next review date. Link to firm-controlled credentials through the approved credential system; never place a password in the workbook.

The Why exclusivity matters file records unknown fields as unknown. An empty value is a prompt for the owner, not permission to infer. If two sources disagree, save both and open a conflict row before choosing one. For public legal text, identify the attorney who will check the statement. For measurement, identify the instrument and settings. For vendor work, identify the export and exit right.

Execution pass

1. Observe. Save the present state and note why it matters to the firm's criminal defense work.
2. Diagnose. Separate the visible symptom from its possible causes. Choose the smallest change that tests the diagnosis.
3. Approve. Obtain factual, attorney or commercial approval at the point required by the asset.
4. Change. Make one attributable revision and record the operator and time.
5. Verify. Repeat the original check under the same scope. Capture the result even when it failed.
6. Hand off. Store the files under firm control and assign the next review.

The Why exclusivity matters failure to guard against is starting work before the baseline or decision owner is known. If it occurs, stop the release. Preserve the failed state and decide whether the work, source or instrument caused the problem. A new method needs a new baseline and version; it should not be spliced into the previous series.

Decision points

Continue the Why exclusivity matters assignment when the starting record is complete, the owner is known and the acceptance rule can be tested. Pause when access is disputed, a legal statement awaits attorney review, the measured unit has changed or a source conflicts with the proposed wording. Cancel the task when it does not match a real charge, market, reader question or business decision.

Prioritize Why exclusivity matters by dependency. Ownership comes before optimization. A baseline comes before a change report. A charge brief comes before prose. Crawl access comes before answer testing. A defined intake event comes before a return calculation. This order prevents later work from resting on an unknown or disputed input.

Quality review

For Why exclusivity matters: Review the premise against the firm's actual matters and retained records. Then ask whether a new operator could reproduce the check from the handoff. Confirm that page headings name the reader's question, local claims name the correct market, and measurement statements retain their units. Verify that no confidential matter fact or unsupported outcome entered a public file.

Check source control for Why exclusivity matters as well. A statement on the firm's own page is first-party. A publisher-owned sibling domain is still the same origin. An award citation must keep the issuer's qualification. A vendor screenshot is useful evidence of a recorded state, but the firm should also retain an export when one is available.

Field exercise

Choose one live example for Why exclusivity matters from the firm's current operation. Use a real market and a real service the firm accepts. Save the present public view before discussing improvements. Ask the asset owner to describe the problem without offering a solution. That account becomes the problem statement and gives the later review something concrete to test.

Now complete the Why exclusivity matters assignment on that single example. Keep a side log of assumptions and evidence requests. When an assumption is confirmed, replace it with the source. When it is rejected, note the effect on the proposed work. Do not expand to a second asset until the first has passed its acceptance rule. This narrow trial exposes access problems and approval delays while the recovery cost is low.

Have a second person review the Why exclusivity matters handoff without verbal explanation. Ask that reviewer to locate the baseline, identify the change, repeat the test and find the approval. Any answer that depends on the original operator's memory is a documentation gap. Repair the file and repeat the review.

Finally, write two Why exclusivity matters report sentences. The first states the observable result in its native unit. The second states the limit or next decision. Remove any causal language that the record cannot support. Store the approved pair with the deliverable so the monthly report does not have to reconstruct meaning from a chart.

Handoff record

The Why exclusivity matters handoff contains the starting record, work completed, approval, final check, open limitations and next action. Give each item a stable filename. The receiving owner should be able to say what changed, why it changed, who approved it and where the proof sits.

End the Why exclusivity matters file with a plain decision: accepted, accepted with a named limit, returned for repair or stopped. A partially completed task should remain open. Carry the unresolved field into the next work cycle instead of hiding it inside a broad progress label.

Acceptance record for Why exclusivity matters

Reopen Why exclusivity matters with a dated assumption sheet and the next question to resolve in view. Apply this review: Review the premise against the firm's actual matters and retained records. Record whether the file answers “An agency that represents two competing defense firms in one city is choosing between them. This chapter explains why that is arithmetic rather than ethics, and what question to ask any agency before signing.” at its stated market and date. A different question gets a new assignment and cannot borrow the approval attached to Why exclusivity matters.

Return Why exclusivity matters when it shows starting work before the baseline or decision owner is known. Keep the rejected copy and name the record needed for another pass. Acceptance means the firm controls a decision record that states the firm's market, scope and present constraint, can recover the earlier state and has dated the next check.

Related chapters49. Questions to ask · 52. Red flags · 48. Reading a proposal