Artifact
A shipped Base mini-app, full sender flow, onchain reward/payment contracts, Beepi AI composition, BeeperX SDK/API, partner campaign rail, and physical pager roadmap.
A-01 / paid signal layer / 2025–2026
Beeper
A Base-native paid attention product where users set an inbox price, earn for engagement, and unread messages can refund the sender.
44.8Ktotal users
32.8Kactive users
39.1%read rate
2.4Kpaid senders
Source: Base Batches 003 evidence bundle + public Beeper / Base APAC receipts. Definitions available on request.
44.8K users / 39.1% read rate / #3 mini app
Ownership
What I owned, and where the line was.
My roleCo-founder / product + front-end + growth
Team context
Built together with a small founding team. Sungwoo led infrastructure, smart contracts, and backend; Mario led hardware engineering for the pager.
What I directly owned
- Full front-end rebuild: compose, targeting, reward planning, quote, and onchain transaction flows
- Product design and interaction states across the sender flow
- Campaign mechanics and partner activation surfaces
- Copy, story, and the public proof layer
- Partner research and launch
What I influenced
- Reward / payment contract behavior and settlement UX
- BeeperX SDK/API surface for agent access
- Physical pager product direction
Proof
Base Batches 003 evidence bundle + public Beeper / Base APAC receipts
Mechanic
Money changes the message.
Sender pays
Signal starts with a real cost instead of another free notification.
Receiver prices
Humans set the inbox price that makes interruption worthwhile.
Engage → earn
Attention becomes a reward event, not a platform-captured leak.
Ignore → refund
Unread messages can return value instead of becoming spam residue.
Sender flow
From intent to onchain receipt.
01Compose
02Targets
03Missions
04Plan
05Confirm
06Final tx
Proof / Traction
Receipts before adjectives.
01
44,850 total users and 32,793 active users in the Base Batches evidence bundle
02
7,936 unique users and 5,675 transaction users in the last 28 days
03
2,400 unique paid-message senders
04
39.1% read rate — nearly 2x email, 8x push
05
1,215 repeat senders / 50.6% repeat retentionsource pending
06
106K+ battery check-inssource pending
07
60+ Base mainnet contracts with 412K+ total transactionssource pending
08
BeeperX SDK/API with 2,400+ API keys issuedsource pending
Proof, up close
What the screenshots actually prove.
The arc
How the work actually went.
- 01
Problem
Attention is captured by platforms and spammed by senders. The hard part of Beeper was never sending a paid message — it was making paid attention feel like a fair exchange instead of an ad product. If a receiver could not see why the loop was fair before the transaction, the whole thing read as one more spam surface.
- 02
Decision
I worked across product, front-end, and growth, and the recurring call was the same: hide the chain until it becomes proof. Compose, targeting, reward planning, quote and transaction states — every screen had to explain money, attention, and onchain settlement without making anyone read protocol copy. The better versions surfaced the chain only as a budget, a receipt, or a refund.
- 03
Resolution
The sender flow shipped as a real product system, not a landing page: compose, targets, missions, plan, confirm, and an onchain receipt, with a refund path for ignored messages. BeeperX extended the same attention rail to agents that need permissioned access to humans, and the Beep Works site became frontend proof — a custom pixel/CRT world that makes inbox pricing legible in one screen.
- 04
Impact
44,850 total users, 32,793 of them active, and a 39.1% read rate — nearly 2x email. 2,400 people paid to send a message, which is the loop actually working: senders paying for signal, receivers earning for attention. The deeper figures — battery check-ins, total transactions across Base mainnet contracts, repeat-sender retention, BeeperX API keys, and the Base APAC residency track — are real but still moving from internal dashboards to public receipts, so they ship as source-pending until each carries a link.
Receipt timeline
Company years, visible in public receipts.
Beeper hardware waitlist ↗
hardware for Farcaster, filtering noise and amplifying real signal on Base
first 1,500 beepers ↗
early waitlist / stress-test signal
first 2,000 beepers ↗
waitlist growth before closed beta
top 5 miniapp signal ↗
ranked near other leading Base miniapps without a token
1,351 beepers answered stable vs degen ↗
campaign mechanic + user response loop
Brick Side Chat #67 with Steemhunt ↗
contacts, BeeperX, BP rewards, and product overhaul
Why Beeper ↗
attention thesis: every app takes attention for free
Farcon Rome NFC name tags ↗
first offline experiment for attention/social identity
Base APAC / Base Founders Residency feature ↗
external validation: hackathon wins, Base Camp support, flew from Korea to residency
Base APAC / Celebrating Based Builders in APAC ↗
external builder profile: Beeper, TradeFish win, Base Camp 2025, Residency Batch 001, and Base Batches 003
Frontend proof
The website is part of the product, not a wrapper around it.
I designed and built the Beep Works surface as a full product artifact: pixel typography, CRT scanlines, responsive layout, live CTAs, metrics, protocol tags, and a hardware-like visual system that makes paid attention feel tangible.
desktop homepage / live site ↗
mobile responsive proof ↗Art direction
Custom pixel/CRT system, green-on-black signal language, dithered hardware object, and a coherent product world instead of a template.
Responsive craft
Desktop splits the value prop and hardware artifact; mobile keeps brand, CTA, metrics, proof tags, and the device visual readable in one narrow flow.
Product clarity
The page explains the core behavior in one sentence: attach money, set your price, unread messages auto-refund.
Interaction surface
Clear app/video CTAs, marquee protocol cues, metric strip, and stateful beeper screens turn the frontend into product proof.
Partner rail
Campaigns should move rank, not just impressions.
Signet#120 → #6
ReviewMe#34 → #6
imagineclub#219 → #36
TYSM#23 → #5
Video receipts
Use X videos as public proof; host clips only after rights/file cleanup.
What went right
- The incentive is clear: senders pay for signal, receivers get paid for attention, and unread messages can refund.
- The product found two wedges at once: consumer inbox pricing and partner mini-app distribution.
- The sender flow is a real product system, not a landing page: compose, targeting, missions, planning, quote, wallet, transaction, success/failure states.
- BeeperX extends the same attention rail to agents that need permissioned access to humans.
What went wrong
- Some metric definitions still need cleanup before investor-grade charts, especially claim-like value fields.
- Paid attention still needs crisp non-crypto framing; outside Base/Farcaster, the refund loop must be explained in one interaction.
- Hardware makes the idea tangible, but also raises expectations around shipping, latency, battery, support, and reliability.
- Campaign memos are useful pipeline context, but many partner fields are unconfirmed and cannot be used as public proof.