The most useful sentence in a reward brief is the one that explains when the reward is owed. Complete this action, within this window, under these conditions, and earn this benefit. If the team cannot finish that sentence, a larger prize pool will not make the program clearer.
A crypto startup may be trying to teach a workflow, activate a first feature or recognize a contribution. Each objective leads to a different qualifying action. The reward becomes an operating commitment as soon as the published conditions are met.
Choose the action the product is ready to support
Early campaigns often combine every available mechanic: a follow, a community join, a referral, a transaction and a leaderboard. That creates activity across several channels without identifying which step delivers value.
Start with one audience and one useful outcome. For a new wallet feature, that could be an eligible participant completing their first supported payment. The task should explain the network, any fees, the verification delay and how to get help. If the feature is still unreliable, resolve that before increasing the invitation volume.
Learning and contribution can be valid outcomes too. A test environment may be the appropriate place to introduce an unfamiliar workflow. Avoid paying for financial activity merely because it is easy to count.
Write a campaign contract participants can understand
The following is an illustrative brief for a tutorial and test-action campaign. It is a design example, not a Claimr customer result or a claim that every rule is available without integration work.
| Decision | Example rule |
|---|---|
| Audience | New product accounts eligible for the test environment |
| Journey | Read the tutorial, complete the test action, see an achievement |
| Qualification | One verified completion per eligible account |
| Window | A published 14-day campaign with a stated closing time |
| Reward | A $5 product credit under published usage terms |
| Limit | Up to 400 qualifying rewards, with availability shown before entry |
| Verification | A completion event from the product, with a visible pending state |
| Help | A named support route for missing progress and incorrect exclusions |
An account limit is a program rule, not proof that accounts correspond to distinct people. Design duplicate handling and review around the integration. Make the status visible when verification is delayed so a participant does not repeat an action unnecessarily.
Price the obligation before promoting it
Using the illustrative brief, 400 rewards at $5 create up to $2,000 in face-value credits. Assume another $600 for delivery, support and review. The planning total is $2,600 on those assumptions. Product-credit face value and cash delivery cost may differ; record both instead of treating the credit as free.
If 320 participants qualify and all qualifying credits are issued, the face-value reward amount is $1,600. Adding the assumed $600 operating cost gives $2,200, or $6.88 per qualified account after rounding. That is a cost calculation. It says nothing yet about revenue, unique people or incremental acquisition.
Include platform cost, promotion and any other relevant costs before comparing this campaign with another channel. State what happens when capacity is reached. A capped budget needs a participant experience that stops promising rewards once they are unavailable.
Choose a reward that fits the next step
Recognition works when the achievement means something to the participant. Access works when there is a feature or experience worth unlocking. Product credit works when the audience has a reason to use the product. Monetary rewards are easy to explain, but create a direct cost and an obvious reason to collect repeatedly.
Points need a defined role. They can represent progress within a season or eligibility for a published benefit. Avoid leaving participants to infer future token value from an undefined score.
Reward timing matters too. Show progress promptly, even if the economic reward waits for verification. Referral program economics explores how moving the qualifying event changes the cost base; the same reasoning applies to a reward campaign.
Close the loop after the claim
Report starts, qualifying completions, issued rewards and subsequent use as separate steps. Investigate where participants stop and whether they understood the exchange. A high claim rate shows that people collected an available benefit. Repeat product use needs its own event and observation window.
Claimr can connect quests, achievements and rewards to tracked activity through the Widget or your own interface. Begin with a brief that a participant, operator and finance owner can all explain. The first campaign should leave the team with a better rule for the next one.
Keep learning
Further reading
Continue with the sources and practical guides behind this article.
How qualification and reward timing change acquisition cost, with a worked comparison and the limits of the evidence.
Work through the audience, participant journey, rewards, launch checks and evaluation for your own campaign.
The events, rules, state and outcomes behind a repeatable engagement program, with research and a build-or-buy example.
