Compass - Do not just track your money. Navigate your future

The description states that Compass is an Android-based financial navigator that helps users turn personal goals into clear savings plans. It uses AI to interpret natural-language inputs about income and expenses, calculates timelines to reach goals, and allows real-time updates of those timelines.

It also includes a landing page and is described as having a mobile-first experience, though the team lacked dedicated mobile expertise.

• Product type: Personal finance planning app
• Core functionality: Goal-based savings tracking with AI-powered input interpretation
• Platform: Native Android application (with plans for iOS)
• AI role: Used in onboarding, UI design, backend implementation, and core feature logic

Not evidenced: actual product features beyond the MVP, user behavior, or monetization model.

The description states that Compass aims to be more than a transaction tracker — it positions itself as a "financial navigator" that shows users where they are going and how their decisions affect future outcomes.

It evolved from a broad idea of personal finance planning into a focused experience centered on one core question: “what is the clearest next step that moves the user closer to their goal?”

• Original claim: A tool that goes beyond expense tracking to show paths toward financial goals.
• Evolution: Narrowed focus to one concrete goal, with AI helping interpret inputs and visualize progress.
• Vision statement: Not about judging spending but making trade-offs visible; helping users navigate their future.

Inference: The shift from a broad personal finance tool to a goal-centric app reflects an attempt to avoid feature bloat and improve usability. However, this evolution is self-reported and not validated by user feedback or market testing.

The description does not clearly define the target customer segment beyond “individuals” seeking financial goals like saving for an apartment.

It implies a user who:

• Has a specific financial goal (e.g., buying an apartment)
• Wants to understand how their current actions impact progress toward that goal
• May be uncomfortable with complex financial planning tools

Not evidenced: demographics, psychographics, or behavioral data about the intended audience. No mention of personas, customer interviews, or segmentation.

The description does not provide any information on pricing models, monetization strategies, or business model assumptions.

• Monetization: Not stated
• Pricing: Not stated
• Revenue streams: Not stated

Inference: Since this is a hackathon project with no revenue or customer data, the business model remains speculative. The team may be exploring investment opportunities, but there’s no evidence of a defined path to monetization.

The description indicates that:

• The app was built using Android (Kotlin, Jetpack Compose), backend (Spring, PostgreSQL), and AI tools like ChatGPT.
• The team consisted of 4 members, including backend developers and one designer (xpepelok).
• AI played a role in every stage: idea shaping, development, UI exploration, and content creation.
• The app was built quickly, with deliberate trade-offs in architecture for speed.

Not evidenced:

• Actual product performance or scalability
• Technical depth of the AI integration
• Infrastructure or security practices

Inference: The team’s use of AI to overcome lack of mobile expertise suggests a pragmatic approach. However, the absence of technical reviews or benchmarks limits confidence in delivery quality.

The description states that:

• This is an MVP built for a hackathon.
• The team delivered a working product quickly.
• There are plans to collect user feedback and publish on Google Play.
• No revenue, customers, or usage metrics are mentioned.

Not evidenced:

• User base
• Active users
• Retention rates
• Conversion from trial to paid (if any)
• Product usage analytics

Inference: The project is at an early stage with no traction. It lacks evidence of user engagement or product-market fit beyond the initial build.

The description does not mention competitors or market positioning in relation to existing financial apps.

Not evidenced:

• Direct or indirect competitors
• Market size or growth trends
• Differentiation from similar tools

Inference: The team notes that there is no obvious direct equivalent to Compass on the market, suggesting a potential gap. However, this is unverified and not supported by competitive analysis.

Key risks identified:

1. No traction or user data: The project is described as an MVP with no evidence of users or adoption.
2. Unproven AI integration: While AI was used in development, the description does not clarify how well it performs in real-world use cases.
3. Limited team expertise: The team lacks dedicated mobile developers and designers; this may impact long-term product quality.
4. Unclear monetization path: No indication of how the product will generate revenue or sustain itself.
5. Over-reliance on AI: Heavy dependence on AI for both development and user-facing features raises concerns about consistency, transparency, and scalability.

Red flags:

• Lack of any revenue, customer, or usage data
• No mention of market testing or feedback loops
• Ambiguity in the product vision beyond MVP

1. What specific financial goals are users targeting? Are there any user personas or segments?
2. How is AI used in the core product experience — is it a feature or part of the logic engine?
3. Have you conducted any user testing or feedback collection beyond the MVP stage?
4. What is your plan for monetization, and how do you intend to scale the business?
5. How do you plan to address the lack of dedicated mobile expertise in future development?
6. Are there any plans to integrate with financial institutions or third-party APIs?
7. What are the key assumptions behind the product’s value proposition?