Reach the relevant audience — then fund the right action.
Pulino and Board were designed around a different advertising question: instead of asking how many people can be reached, ask which people are actually relevant to this business, this product and this local context — then connect spend to a defined relationship, interaction or transaction rather than to anonymous exposure alone.
A small local business should not need a national advertising budget to reach a relevant local audience.
A local business with a limited budget may have little reason to pay for exposure far outside its geography, category fit or customer context.
The business chooses the value. The user chooses the relationship.
Follow in Pulino is stronger when it is understood as a qualified business-user relationship, not as a generic “get paid to click Follow” mechanic. The business defines who is relevant and whether that relationship has a funded Follow reward; Pulino sits between context and eligibility; the user still decides whether to Follow.
A relationship is not the same thing as active product attention.
Follow establishes a qualified business-user relationship. Board asks for something different: present the product or campaign to a relevant audience, require active interaction with the information, attach a business-funded reward to successful completion, and keep the response as a richer campaign signal.
Cashback moves the funded value from relationship or attention to the transaction itself.
The historical proposal describes a seller-controlled cashback mechanism connected to local Mazzaneh commerce: the seller chooses a cashback percentage, the buyer discovers an eligible opportunity through Radar/map or Gram, the purchase occurs in the applicable local flow, and eligible value returns to the buyer wallet after the purchase is confirmed.
Precision is valuable only if it remains governable.
Historical and later Pulino materials include context such as interests, skills, profession, location and profile fields such as age/gender. Board’s canonical architecture supports profession, interests, skills, location and combined context while explicitly treating exact targeting scope as version-sensitive.
Follow boundary
Supported: business-configured Follow value, qualified/relevant relationship logic, user choice, coded business-facing user representation in historical design, verification need once rewards exist, and later reinforcement/business-protection logic. Not claimed: guaranteed income, a universal Follow payment, proof of purchase, perfect targeting, universal anonymity, modern privacy compliance, or that every verification/settlement rule was active in one Phase 1 version.
Board boundary
Supported: product-learning before questions, active participation rather than passive exposure, reward-linked completion, connection to Pulino and Analytics, and a richer interaction signal than an impression alone. Not claimed: guaranteed understanding, guaranteed purchase, perfect targeting or guaranteed ROI.
Cashback boundary
Exact cashback percentages, settlement mechanics and version-specific operating rules remain evidence-routed. Demo numbers should not be read as historical rates.