MourkTherapy

The description states that MourkTherapy is a platform combining daily operations with official EOPYY certificates and secure subscription onboarding for Greek therapy and special-education centers. It includes:

• Appointment and calendar management
• Client, therapist, specialty, assignment, and invitation handling
• Pricing rules, discount logic, and therapist payouts
• Payments, balances, receipts, and operational statistics
• Diagnosis PDFs and client file support
• OCR assistance for extracting structured information from diagnosis documents
• Administrator review before preparing certificates
• EOPYY-related certificate and monthly-document workflows
• Subscription management and secure therapy-center onboarding

The platform is built with React and Firebase, using Firestore, Cloud Functions, Stripe, and other technologies. It supports role-based access where administrators, therapists, and clients have distinct experiences.

Evidence Self-reported by the author; no independent verification or demonstration of actual functionality beyond codebase structure.

The author states that MourkTherapy was inspired by their seven-month experience working in an occupational-therapy and special-education center. They observed inefficiencies in administrative processes, such as repeated data entry, fragmented tools (paper notes, Excel files), and time spent on non-clinical tasks.

Their positioning claim is that the platform reduces repeated work, makes important information easier to find, and gives teams more time to focus on therapy and people they support. It is described not as a replacement for human care but as a tool to improve operational efficiency.

The evolution of the product's positioning appears to be from an internal solution developed by one individual to a scalable platform aimed at helping multiple small centers facing similar challenges.

Evidence Self-reported; no external validation or market positioning data provided.

The description states that MourkTherapy targets Greek therapy and special-education centers, particularly small ones with limited budgets. The author emphasizes affordability as a core value, stating that the system should not be available only to large organizations with large budgets.

It supports multiple user roles:

• Administrators who can organize the whole center
• Therapists who see their schedule, assigned clients, and earnings
• Clients who follow appointments, documents, and their balance

Evidence Self-reported; no evidence of actual customer segments or personas beyond stated intent.

The description states that MourkTherapy includes subscription management and secure therapy-center onboarding. It integrates with Stripe for payments and supports role-based access control.

It also mentions "general prices, client-specific prices, discount rules, and therapist payouts" as part of its financial workflow features.

However, there is no evidence provided about pricing tiers, revenue models, or monetization strategies beyond the mention of subscriptions and Stripe integration.

Evidence Self-reported; no pricing details, revenue model, or customer acquisition data available.

MourkTherapy is built with React and Firebase, using Firestore, Cloud Functions, Stripe, authentication, and other frontend/backend utilities. The author used Codex and GPT-5.6 to assist in development throughout the process.

Key technical elements mentioned include:

• Role-based access control
• Authentication flow improvements
• Stripe checkout return state validation
• Subscription attachment to centers
• Center creation recovery after interruption
• Keyboard, modal, mobile, and accessibility behavior enhancements
• Automated test expansion for edge cases and regressions

The author notes that the application is connected end-to-end, requiring thorough journey testing across all components.

Evidence Self-reported; no independent technical audit or performance metrics available.

The description states that MourkTherapy existed before Build Week and was already a large, connected application. The author built the main React and Firebase application, role-based areas, appointment and member management, financial workflows, document handling, and core therapy-center environment prior to the submission period.

During Build Week, they focused on extending and strengthening the existing product rather than creating something new from scratch. They emphasize that the work was not limited to one week but involved ongoing development supported by dated commits and Codex sessions.

There is no evidence of actual users, customers, or revenue generated beyond what the author describes.

Evidence Self-reported; no traction data, user base, or financial metrics available.

The description does not provide any information about competitors or market positioning relative to other platforms serving therapy and special-education centers. It does not mention existing solutions in this space or how MourkTherapy differentiates itself.

Evidence Not evidenced; no competitive landscape data provided.

Several risks and red flags are present based on the self-reported information:

1. No traction or revenue evidence: The platform has no demonstrated users, customers, or monetization.
2. Single-person development: Only one team member (John Mourkakos) is involved, raising questions about scalability and long-term maintenance.
3. Unverified claims: All features and functionality are self-reported without independent verification.
4. Lack of market validation: No evidence that the target audience actually needs or wants this solution.
5. Language barriers: The author notes English is not their first language, which may affect clarity in documentation or user experience.
6. AI dependency: Heavy reliance on AI tools (Codex, GPT-5.6) raises concerns about quality control and reproducibility if those tools change or become unavailable.

Evidence Inferred from lack of supporting data; no external validation or competitive analysis.

1. What specific problems in therapy centers did you observe during your time working there, and how does MourkTherapy address them?
2. Have you validated the platform with actual users from therapy centers? If so, what feedback have you received?
3. How do you plan to scale beyond a single developer's capacity?
4. What is your go-to-market strategy for reaching small therapy centers in Greece?
5. Are there any regulatory or compliance issues specific to EOPYY-related workflows that could impact adoption?
6. Can you provide examples of how the OCR functionality works in practice?
7. How do you intend to ensure data security and privacy, especially given the sensitive nature of therapy records?

Evidence Inferred from lack of information; these are questions needed to assess real-world applicability.