How we work: brief, plan, prepayment, delivery and report

What goes into the first brief?

Quick test: Count how many of the 4 inputs you have today: project link, audience, goal and dates. Send what you have.

A useful brief tells us what the project is trying to achieve, who it needs to reach and what is already in place. It does not need to be polished; it needs enough context for us to ask the right questions and define a workable plan.

Include the following where available:

• Project website, product description and relevant social or community channels.
• Your current priority, intended audience and the action you want them to take.
• Launch or campaign context, including any fixed dates or dependencies.
• Existing creative, approved claims, brand guidance and compliance constraints.
• The decision-maker and the person who can provide assets or approvals.

We review the material for gaps, unclear claims and dependencies, then send focused questions rather than asking you to rewrite everything. If you are unsure which channel or service fits the goal, tell us what outcome matters and what has already been tried. We can map the options before defining a plan. For a broader view of our team and approach, see About us; to discuss your project directly, use Contact.

How a brief becomes an approved plan

We translate the brief into a written plan that makes the work reviewable before payment. It states the selected plan, the what you receive, the client inputs required, the approval points and the expected sequence of activity. This gives both sides a shared reference if priorities change during delivery.

The planning exchange usually follows this order:

• We clarify the goal, audience, channels and any constraints that affect execution.
• We identify the assets, account access or approvals needed from your team.
• We outline the work, handoffs and reporting format, then confirm the timing.
• You review the plan and resolve open questions before authorizing the work.

A senior reviewer checks the proposed plan for consistency: each item you receive should connect to the stated goal, and each client dependency should have an owner. If a request is outside the agreed plan, we flag it before it becomes unplanned work. You can review the broader service pricing information alongside the proposal, and use our FAQ for common process questions. We move to payment only after you approve the written plan.

Your 6-point stage checklist

Use this checklist to keep each stage clear. If one point is missing at a stage, ask for it before moving to the next one. If a line is hard to tick, that is useful news: it shows what to settle before any money or time is spent.

1. Brief: project, audience, goal and dates received.
2. Plan: items, owners, windows and price in writing.
3. Approval: you confirm the plan in your own words.
4. Prepayment: sent only after approval.
5. Delivery: updates on the agreed days.
6. Report: links, screenshots and open questions.

Terms in one line

Plan (in plain words: the written list of work, owners, dates and price you approve before paying).

Report means the final record with links and screenshots of what was delivered.

What happens after prepayment

Rule of thumb: Never pay before you have read the plan. Every plan lists items, owners and dates.

Once the plan is approved and prepayment is received, we confirm the starting inputs and begin the agreed work. The project contact keeps the communication in one thread, tracks open approvals and tells you when a decision or asset is needed, so execution does not disappear into disconnected handoffs.

We accept USDT, USDC, BTC, ETH, SOL, TON and BNB. See Payment methods for payment details. Before sending funds, confirm the agreed plan, receiving instructions and payment asset with us; do not rely on a copied address from an old conversation.

During delivery, we work against the plan, share items that need your approval and keep a record of completed actions. The timeline begins from the point agreed in the plan, with any client-side approvals or missing assets handled as dependencies. For work involving third-party platforms, their review decisions, publication status, placement rotation and interface changes are outside our control; we commit to the work and placements explicitly agreed, not to a particular platform outcome. If an issue calls for a different plan, we raise it for approval before proceeding.

What the final report shows

The report closes the loop between the approved plan and the work completed. It records delivered items, links or other available evidence, any outstanding dependencies and the next actions that make sense from the project’s current position.

We keep reporting useful rather than ornamental. For each item you receive, the report should help you answer: what was done, where can I verify it, and what decision or follow-up is now needed? If a platform page, post or placement is part of the plan, we include the corresponding reference when it is available. If a planned item could not be completed because an input or approval remained open, we state that plainly.

Use the report to decide whether to close the work, extend the plan or shift attention to another channel. You can explore related options in Trending campaigns, Listings and verification or PR and media. To start, send your project link, primary goal, relevant deadline and any assets or constraints you already know about. We will review them, ask only the necessary follow-up questions and return a plan for your approval.

Send 3 things to begin: your project link, your goal and your preferred channels.