PhilRadar

Note: This analysis is based entirely on the self-reported project description provided by the caller. No external verification, revenue data, customer list, or independent sources are available. All claims in this report are labeled as "the author states" and not confirmed.

The description states that PhilRadar is a tool that allows users to search for medications (e.g., Paracetamol) and see nearby pharmacies with real-time stock status. Users can view whether a pharmacy has the medication in stock, low stock, or is out of stock. It also includes functionality for users to confirm or flag reports to maintain accuracy.

Pharmacies have their own portal where they can register, manage inventory, and update stock information using a shared catalog or by adding new medications.

The author built the frontend with Next.js and Leaflet.js, used Supabase for backend functions including authentication and database storage, and integrated browser geolocation APIs to calculate distances.

Inference: The product appears to be a real-time inventory tracking system for pharmacies, connected to a map-based UI. It is not described as a marketplace or platform with monetization features beyond basic access.

The author states that the idea came from a personal frustration — trying to find medication after hospital discharge and encountering multiple pharmacies out of stock. This led to the claim that “why should someone have to visit five pharmacies just to find one medication?”

They describe PhilRadar as a solution to this problem, positioning it as a tool for people who want to avoid wasting time walking around looking for medications.

Claim: The product is positioned as a practical utility for patients and caregivers seeking medication availability in real-time.

Inference: There is no indication of broader market positioning beyond solving an immediate need. No branding, messaging, or strategic differentiation beyond the core use case.

The author describes two main user types:

1. Patients/Caregivers who want to locate nearby pharmacies with specific medications in stock.
2. Pharmacists/Pharmacy staff who manage inventory through a dashboard.

The target location is specified as Accra, Ghana, though the author notes plans to expand beyond that city.

Inference: The ICP seems narrowly defined around individuals needing quick access to medication and pharmacy workers managing local stock levels. No evidence of segmentation or targeting other demographics (e.g., elderly, chronic disease patients).

The description does not mention any pricing model, monetization strategy, or business model. It only describes the core functionality of the platform.

Not evidenced: There is no indication of how the service will be monetized, whether through subscriptions, transaction fees, advertising, or other mechanisms.

The author built the frontend using Next.js and Leaflet.js with OpenStreetMap/CARTO tiles. Backend uses Supabase for authentication and database management. Geolocation comes from the browser API, and distances are calculated via the Haversine formula.

They used AI coding agents during a Buildweek hackathon to accelerate development but emphasized that manual intervention was necessary due to integration issues.

Inference: The tech stack suggests a lightweight, full-stack web application built quickly under time pressure. It is not described as scalable or production-ready beyond the prototype phase.

The author claims to have shipped a complete working product during a hackathon and that all components function together (search, map view, stock status, confirm/flag system, pharmacy dashboard).

However, there is no evidence of:

• Users
• Customer engagement
• Revenue or monetization
• Active pharmacy registrations
• Data on how often users search or update inventory

Absence of evidence: No traction indicators are present in the description.

The author does not reference any competitors. The project is described as a novel solution to a common problem, but no comparison with existing tools or services is made.

Not evidenced: No competitive landscape or differentiation strategy is described.

• Single-person development: Only one team member (Theophilus T) is mentioned. This raises questions about scalability and long-term maintenance.
• Prototype-only status: The project was built during a hackathon; no indication of post-hack development or product maturity.
• No traction or adoption data: No evidence of users, customers, or engagement beyond the author’s own experience.
• AI dependency with limited control: While AI helped build the system, the author notes that manual fixes were required for integration — suggesting potential fragility in scaling or consistency.

Inference: The project lacks commercial viability signals and appears to be a proof-of-concept rather than a scalable business.

1. How many users are currently using the platform?
2. Have any pharmacies registered or updated inventory?
3. What is the plan for expanding beyond Accra?
4. Is there any intention to monetize the service, and how?
5. How do you intend to ensure data accuracy over time without relying solely on user confirmation?
6. Are there plans to integrate with hospital systems or pharmacy chains?
7. What are the key challenges in maintaining real-time stock updates at scale?