Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #5,868 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
Pay the Goblin is a self-reported mobile accountability app built with React Native and SQLite, designed for people who ignore ordinary reminders. The app uses a playful "goblin" metaphor to encourage habit tracking without public shame or real-money penalties. It includes local-first functionality, proof-based commitments, and optional social features via Supabase and RevenueCat.
What changed
The project evolved from an idea around a “little goblin” collecting commitments into a functional mobile app with core habit-tracking elements like commitment filing, proof submission, reminders, and a wallet/ledger system. The author reports building it using AI tools (GPT-5.6, Codex) and iterative development phases.
The single most important open question
Is there any evidence of user engagement or adoption beyond the founder’s own use? The description contains no data on users, revenue, traction, or customer feedback — only self-reported claims about intent and design.
What The Product Actually Is
The description states that Pay the Goblin is a local-first mobile accountability app built with Expo / React Native, SQLite, and optionally Supabase and RevenueCat. It includes features such as:
- Commitment filing
- Proof flows (e.g., photos, videos, timers)
- Reminders
- A wallet and ledger system
- Vault cosmetics and themed screens
- Optional Mailroom/private friend-challenge functionality
The app is described as intentionally local-first — meaning users can file and complete commitments without needing an account or backend.
Evidence
- The author states: “Pay the Goblin is a local-first mobile accountability app built with Expo / React Native and SQLite.”
- Features listed include: commitments, proof flows, reminders, wallet/ledger, Vault cosmetics, Desk equipment, themed docket screens, feedback form.
- Supabase powers optional Mailroom/private friend-challenge direction.
- RevenueCat is used for the Bureau Pro subscription path.
Inference The app appears to be a prototype or early-stage MVP, not yet a commercial product with users or monetization confirmed.
Positioning & Claim Evolution
The author claims that Pay the Goblin targets people who ignore ordinary reminders, and aims to offer a playful way to make small promises feel real without turning them into punishment. It is positioned as an alternative to sterile habit trackers or shame-based accountability tools.
It started with the idea of a “little goblin” collecting commitments, which evolved into a functional app with proof-based accountability.
Evidence
- The author states: “I never really thought of building a habit tracker... I just had and idea around a little Goblin coming to collect.”
- “Most habit trackers feel sterile... I wanted something smaller, stranger, and more useful — a playful way to make small promises feel real without turning them into punishment.”
- “This is not meant to be a serious application, its more a prompt to keep you on track with the little (and big) goals you have.”
Inference The positioning evolved from a whimsical idea to a functional app, but no evidence of market validation or user feedback exists.
Target Customer & ICP
The description states that Pay the Goblin is for people who ignore ordinary reminders, and wants to offer private, playful accountability without shame or real-money consequences. It is described as appealing to those who want to make follow-through feel “a little more tangible, a little more fun, and a little easier to come back to.”
Evidence
- The author states: “Pay the Goblin is for people who ignore ordinary reminders...”
- “It’s more a prompt to keep you on track with the little (and big) goals you have.”
- “Solo goals stay local by default.”
Inference The target customer appears to be individuals seeking private, low-stakes habit tracking. No evidence of segmentation or specific personas is provided.
Business Model & Pricing Evidence
There is no clear business model or pricing information in the description. The app uses RevenueCat for a “Bureau Pro” subscription path, suggesting a freemium or paid tier may be planned, but no details are given about pricing, monetization strategy, or revenue streams.
Evidence
- RevenueCat is used for the Bureau Pro subscription path.
- The author states: “There are no real-money penalties, no public leaderboard, and solo goals stay local by default.”
Inference A paid model may exist, but there is no evidence of pricing, conversion rates, or monetization strategy.
Technical & Delivery Signals
The app was built using Expo / React Native, SQLite, Supabase, and RevenueCat, with AI tools like GPT-5.6, Codex, and ChatGPT used in the development process.
The author reports a phased build approach, using prompts to guide implementation, validating with TypeScript, SQLite checks, and manual review.
Evidence
- Built with: Expo / React Native, SQLite, Supabase, RevenueCat, TypeScript.
- AI tools used: GPT-5.6, Codex, ChatGPT (Sol 5.6 High, GPT-5.6 Terra).
- Development process: Phased build, prompt-based implementation, validation steps.
Inference The technical stack and development approach suggest a lean, prototype-style build, not yet a scalable or production-ready product.
Traction & Maturity Signals
There is no evidence of traction, customers, revenue, or user engagement. The author describes the app as a personal project with early testing via feedback forms and manual validation.
The app is described as a prototype, not yet released to the public.
Evidence
- “This is probably because the thought is half baked when I start...”
- “I want to continue building on the mailroom/ friend and social side of the app.”
- “Next will be the initial release, most likely during the Shipaton hackathon.”
Inference No measurable traction or adoption exists. The project appears to be in an early development stage.
Competitive Context
The description does not mention competitors or market positioning relative to existing habit-tracking apps. It only states that current tools are either “sterile” or involve public performance/shame.
Evidence
- “Most habit trackers feel sterile...”
- “A lot of accountability tools either become public performance or shame.”
Inference The app positions itself as a niche alternative to mainstream habit trackers, but no competitive analysis or market data is provided.
Key Risks & Red Flags
- No user data or adoption metrics: The project is entirely self-reported with no evidence of traction.
- Prototype stage: No commercial product or monetization strategy is evident.
- Founder-only development: Only one team member (Joel Hayward) is mentioned, suggesting limited scalability.
- Unverified claims: All descriptions are self-reported and unverified.
Inference Without evidence of users or revenue, the project may not yet have a viable business model or market fit.
Diligence Questions To Ask The Founders
- What specific user feedback has been gathered so far?
- Are there any early adopters or beta testers using the app?
- How is the “proof” mechanism validated — is it just self-reported or does it include verification?
- Is there a plan for monetization beyond the optional subscription path?
- What are the key assumptions about user behavior that underpin the product design?
Investment/Partnership Verdict
Not evidenced.
There is no evidence of revenue, customers, traction, or commercial viability. The project is described as a prototype built by one person using AI tools and is not yet released to users.
The description contains only self-reported claims about intent, design, and development — no data on performance, adoption, or market demand.
Confidence Low. This analysis is based entirely on the author’s own account, which is unverified and lacks any evidence of commercial progress.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.