Cardly

Company: Cardly

Self-reported purpose: A personal finance app that tracks credit card due dates, subscription renewals, and expenses — without requiring bank sync or credentials.

Key claim: To help users avoid late fees and forgotten subscriptions by centralizing financial tracking in one offline tool.

What changed: The project was submitted as a hackathon entry for the OpenAI 2026 hackathon, with no prior commercial traction or funding evidence.

Single most important open question: Is there sufficient demand for a privacy-first, manual-input financial tracker that competes with existing solutions like Mint or YNAB?

This is a self-reported, unverified account of a project submitted by one developer (Daniel Mu) to a hackathon. No revenue, customers, or adoption data are available beyond what the author states.

The description states that Cardly:

• Tracks credit card billing cycles with smart repayment reminders.
• Aggregates subscriptions with renewal alerts.
• Allows users to log daily expenses via a calculator-style quick-entry interface.
• Operates offline, without requiring bank account access or credentials.

It is built using React Native + Expo (iOS), TypeScript, NativeWind for styling, Zustand for state management, expo-sqlite + Drizzle ORM for local-first data storage, and expo-notifications for scheduled reminders.

Inference: The app appears to be a personal finance tracker focused on control and privacy, with no bank sync or auto-import features. It is designed for manual input and offline use.

The author states:

• Most people carry 3+ credit cards and 8+ subscriptions but have no single place to track due dates or recurring charges.
• Late fees and forgotten subscriptions silently drain hundreds of dollars a year.
• Cardly was built to fix this problem.

Inference: The positioning is centered on solving a common pain point — financial oversight — through a privacy-first, manual-input approach. It positions itself as an alternative to tools that rely on bank sync or auto-detection.

Claim vs. Fact: The author claims the app solves a widespread problem and offers a better way to manage subscriptions and payments. No evidence of actual user adoption or market validation is provided.

The description states:

• The target audience includes people who carry multiple credit cards and subscriptions.
• Users are likely anxious about financial oversight, as the app aims to reduce "anxiety-prone" domains.

Inference: The ICP appears to be financially-conscious individuals or early adopters of privacy-first tools who prefer manual input over auto-sync features. It may appeal to users who distrust financial apps with bank access.

Not evidenced: No specific customer personas, demographics, or usage patterns are provided.

The description states:

• The app will offer a Pro tier at $4.99/month.
• The goal is to reach 10,000 paying users in the first year.

Inference: Cardly appears to be pursuing a freemium or subscription-based model with a paid tier for enhanced features. Pricing is set at $4.99/month.

Not evidenced: No revenue data, pricing strategy validation, or customer willingness-to-pay evidence is provided.

The description states:

• Built with React Native + Expo (iOS), TypeScript, NativeWind.
• Uses Zustand for state management, expo-sqlite + Drizzle ORM for local-first data storage.
• Designed and prototyped 18 screens end-to-end in one hackathon cycle.

Inference: The app is built with a modern, mobile-first stack and emphasizes local-first architecture. It was completed quickly (in one hackathon cycle), suggesting a prototype or MVP level of development.

Not evidenced: No production deployment, scalability, or performance data is provided.

The description states:

• 18 fully interactive screens shipped in one hackathon cycle.
• A privacy-first architecture that requires zero bank credentials while delivering genuine financial utility from day one.
• The app was submitted to the OpenAI 2026 hackathon.

Inference: This is a hackathon project, not a product with traction or market validation. It has no users, revenue, or adoption metrics.

Not evidenced: No evidence of user base, retention, or monetization is provided.

The description does not mention competitors directly. However, the app's positioning implies it competes with:

• Subscription tracking tools (e.g., Truebill, Clarity Money).
• Personal finance apps that rely on bank sync (e.g., Mint, YNAB).

Inference: Cardly positions itself as a privacy-first alternative to these tools, focusing on manual input and local data storage.

Not evidenced: No competitive analysis or market positioning against existing players is provided.

• No traction or revenue: The app is a hackathon submission with no evidence of adoption or monetization.
• Manual input may limit scalability: Users must manually enter data, which could reduce usability and growth potential.
• Unproven demand: No evidence that users are willing to pay $4.99/month for this service.
• Limited team size: Only one developer is involved, raising questions about execution capacity.
• Privacy vs. utility trade-off: While privacy is a selling point, it may also limit the app’s utility compared to tools with bank sync.

1. What specific user pain points did you identify that led to this product idea?
2. How do you plan to validate demand for the Pro tier at $4.99/month?
3. What is your go-to-market strategy for reaching 10,000 paying users in year one?
4. Are there any technical or design limitations of manual input that you’ve encountered?
5. How do you intend to scale beyond a single developer?
6. What are the key features in the Pro tier that justify the $4.99/month price?