How We Work: From Web3 Brief to Campaign Report

How does a Web3 brief become an execution plan?

1. Brief: Share the project, objective, audience, channels and constraints.
2. Scope check: We confirm what is in scope, what needs your approval and what inputs are missing.
3. Plan: You receive a written outline of deliverables, owners, dependencies and timing.

We convert your request into work that can be reviewed and verified. A concise brief is enough to begin; it does not need to be a polished strategy document. Include links to the project site and social channels, the product or token context, target markets, any launch milestones, and the action you want the audience to take. Flag legal, brand or platform restrictions early.

Before you approve the plan, check that each deliverable has a clear format and approval owner. For placements, clarify the intended channel and what proof of delivery will be available. For content or community work, identify who can approve copy and answer product questions. Our scope review is the named quality check: we compare the requested work with the proposed deliverables and return unresolved questions before payment. If you need to compare packages, see pricing; for ongoing coordination, start from the project overview.

What happens after the plan is approved?

1. Approval: You confirm the scope, deliverables and working contacts.
2. Prepayment: We share payment instructions for the agreed work.
3. Execution: The assigned team follows the approved plan and raises decisions that need your input.

Crypto prepayment is collected before execution. Available payment options include USDT, USDC, BTC, ETH, SOL, TON and BNB. The payment instructions identify the asset and destination for the agreed transaction; use the payment methods page for the relevant process. Send transaction confirmation through the agreed project channel so the team can match it to the scope.

Once payment and required materials are confirmed, work starts according to the schedule in the plan. The schedule is set around the deliverables, approval points and any dependencies, rather than assumed from the first enquiry. Keep one project contact available for approvals and factual questions. If an input changes, we document the effect on scope or timing before proceeding with the changed work. This keeps the execution record aligned with what you approved and paid for.

How are timing, client inputs and reporting handled?

1. Timing: The plan records the expected sequence and client review points.
2. Client inputs: You provide accurate project information, access or approvals that the work requires.
3. Report: We summarize completed deliverables and attach available evidence.

There is no useful universal schedule for every Web3 campaign. A single placement, a content sequence and an ongoing program have different dependencies. We set the expected timing after checking the scope, required materials, platform or publisher coordination, and how quickly your team can approve work. If a dependency changes, the account contact tells you what is waiting and updates the working schedule.

The closing report is a delivery record, not a claim about future business performance. Depending on the agreed scope, it can identify the completed item, its destination, a public link or other available confirmation, and any open follow-up. Ask for the evidence format during planning if your team needs a particular handover. For examples of how work can be documented, review case studies; for questions before kickoff, see the FAQ.

What should you confirm before kickoff?

1. Objective: State the decision or action you want the campaign to support.
2. Authority: Name who can approve copy, placements and changes.
3. Readiness: Confirm that links, project facts and access are current.

These checks reduce avoidable pauses. A useful kickoff pack contains a short project description, official links, target audience and markets, preferred timing, brand guidance, restricted claims, and the name of the person who can answer questions. Add any existing campaign assets you want us to use. Do not send credentials in an open message; agree on an appropriate access method with the account contact.

Third-party platforms and publishers control their own reviews, eligibility decisions, placement availability and display periods. We can commit to the agreed work and provide its delivery record, but cannot control a platform’s decision or promise that a placement will remain visible for a particular period. If your project needs formal review or a specific delivery condition, make that a planning question and read our guarantees and refunds terms before approval.

To begin, send AEOTech your project links, objective, preferred timing and approval contact. We will review the brief, return scope questions and prepare a written plan for your decision.