Different time zones. One clear plan.

SAMPLE BRIEF / 001

From the first post to the first API request.

FICTIONAL BRIEF — Not client work or reported results.

Follow a fictional Web3 data API from audience choice to Korean copy and a reporting plan. A look at the thinking behind the work—not a case study or a performance forecast.

Project

Sample Project A: a Web3 data API.

Audience

Korean developers choosing data for a prototype.

Product step

Make a successful first API request.

Hypothesis

Inviting developers to check supported data and make a first request may work better than a generic launch announcement. Test it with this audience; it is not a claim about Korean developers generally.

Channel decision

Fictional assumption: relevant Korean developers already follow the client’s X account, so this sample uses X rather than Telegram. Verify audience access in a real brief; if it is not there, re-scope distribution instead of posting eight times to an empty channel.

Korean post draft

온체인 데이터로 프로토타입을 만들고 있나요? 지원 데이터와 응답 예제를 살펴보고, 빠른 시작 가이드로 첫 API 요청을 보내보세요.

English meaning

Building a prototype with on-chain data? Explore the supported data and sample responses, then make your first API request with the quick-start guide.

Client readiness

The client provides a working trial, accurate product facts, and a Korean quick-start guide. Product development and full-documentation translation are outside the eight-post pilot.

What to measure

If the client can lawfully share aggregate events, record tagged guide visits separately from successful first API requests per trial account. Report known internal tests and incentivized activity separately.

Attribution limit

Without a link between visits and product events, do not label trial activity as campaign-acquired users. Name the data source, reporting window, access owner, and unavailable measurements. Use a comparable baseline only if one exists.

Week 1

Confirm audience access, product readiness, approvals, and permitted measurement. Agree the desired-action threshold and minimum evidence with the client, based on the product and budget—not a preset benchmark. This fictional example includes no results.

Week 2

Prepare the first content batch. Review product accuracy, Korean wording, and the destination page with the client approver.

Week 3

Publish approved content and coordinate only confirmed creator work. Track delivery, spend, and issues blocking the product step.

Week 4

Report deliverables, observed actions, data gaps, and the next decision, alongside unsuccessful outreach and unspent budget.

Continue, change, or stop

Continue only if the agreed action and evidence thresholds can be measured and met. Test message or landing-page changes only when audience/source and funnel evidence supports a drop-off hypothesis. If visits and product events cannot be linked, report them separately; conversion diagnosis remains inconclusive. Stop or re-scope when distribution or measurement is unavailable. A small sample alone does not prove there is no demand.