ScoreSync

ScoreSync is a self-reported role-aware collaboration platform for school and community music ensembles. The author describes it as a tool that helps directors, section leaders, and musicians maintain consistent rehearsal feedback by assigning parts, coordinating sections, and enabling annotations on shared musical materials.

The project was built by one developer (Amelie Huang) over the course of a hackathon, using a full-stack tech stack including React, Node.js, Supabase, and PDF.js. It is deployed and functional, with features such as role-scoped access, annotation systems, and cross-part annotation placement.

The description states that ScoreSync supports three roles: directors, section leaders, and musicians. It includes functionality for uploading official files, assigning parts, managing rosters, and allowing musicians to suggest annotations that are reviewed by section leaders or directors before being shared.

There is no evidence of revenue, customers, traction, or funding. The author claims the system handles complex permission models and deployment challenges but does not provide data on usage, adoption, or performance.

The description states that ScoreSync is a "role-aware collaboration workspace for school and community music ensembles." It supports three roles:

• Directors who create ensembles, manage rosters, upload files, assign parts, and share rehearsal notes.
• Section leaders who view their section library, help with part assignment, review suggestions, and coordinate feedback.
• Musicians who request access to ensembles, see assigned concerts and parts, keep personal annotations, and suggest comments for review.

It allows users to upload private conductor scores and official instrument parts. Musicians only have access to the concerts and parts assigned to them, while directors retain a full-library view.

The system supports text and symbol notes placed by measure and location on rendered PDF pages. Notes can be personal reminders, shared section feedback, director notes sent from a conductor score to selected instrument parts or multiple sections, or musician suggestions waiting for review.

It includes an annotation system where musicians can suggest annotations on their assigned official part. These suggestions are visible only to the musician, relevant section leader, and director until reviewed. Review outcomes include:

• Approve: turning the suggestion into a shared annotation.
• Disregard: returning it as a personal note instead of deleting the work.

The system preserves measure context and allows intentional shared placement on the target part when conductor scores and individual parts have different layouts.

Inference The product appears to be a web-based application designed for collaborative music rehearsal environments, with specific attention paid to managing permissions and annotations across multiple roles and document types.

The author states that ScoreSync addresses inconsistency in rehearsal feedback. They describe how directors work from full scores, musicians from individual parts, and section leaders coordinate sections — leading to fragmented communication and missed instructions.

The core positioning is: "ScoreSync keeps ensemble rehearsal feedback consistent."

It positions itself as a replacement for scattered PDFs, screenshots, messages, and verbal reminders. The author claims it gives each person the right materials and a structured way to communicate about them.

Inference This is a product built around solving a specific pain point in ensemble rehearsal workflows — not just a generic collaboration tool but one tailored to music education or community performance settings.

The description states that ScoreSync targets "school and community music ensembles." It mentions roles such as directors, section leaders, and musicians within these groups.

Membership details (instrument, grade, leadership role) are scoped to each ensemble rather than permanently attached to a user. A musician can play flute in one group, percussion in another, and have a different role in each.

Inference The ICP likely includes small-to-medium-sized music programs in educational institutions or community organizations that rely on collaborative rehearsal processes and need structured tools for managing shared musical materials and feedback.

Not evidenced.

The description does not mention any pricing model, monetization strategy, or business model. There is no indication of whether the tool will be offered free, paid, or through subscription.

The author reports that ScoreSync was built using:

• Frontend: React, TypeScript, Vite
• Backend: Node.js API with OpenAPI-generated clients
• Database: Supabase Auth, Postgres, Storage, Row Level Security
• Deployment: Vercel for frontend, Render for API
• PDF Handling: PDF.js for rendering and annotation overlays
• Storage: Private PDF storage with short-lived signed links

The author used Codex as a development collaborator throughout the process, including inspecting codebases, scoping milestones, implementing features, generating migrations, tracing production failures, and running type/build checks.

Deployment revealed bugs related to expired signed PDF links, nested-route refreshes, CORS configuration, and Row Level Security policies behaving differently in live app vs. local environments.

Inference The technical stack suggests a modern full-stack SaaS approach with cloud-native infrastructure (Supabase, Vercel, Render). The use of Codex indicates an AI-assisted development workflow, which may be relevant for understanding scalability or future tooling decisions.

Not evidenced.

There is no evidence of revenue, customers, user engagement, or adoption metrics. The author describes the tool as deployed and functional but does not provide data on usage, retention, or growth.

The project was submitted to a hackathon, suggesting it may be early-stage and experimental in nature.

Not evidenced.

There is no mention of competitors, existing solutions, or market positioning relative to other tools for ensemble rehearsal management or collaborative music annotation.

• Single Developer: The project was built by one developer (Amelie Huang), raising questions about scalability, maintenance, and long-term support.
• No Revenue or Customers: No evidence of monetization, users, or traction. This raises concerns about market viability.
• Unverified Claims: All claims are self-reported and unverifiable; there is no independent validation of the stated benefits or technical capabilities.
• Deployment Challenges: The author notes that deployment surfaced several bugs not visible locally, indicating potential instability or lack of robust testing in production environments.
• Lack of Market Data: No evidence of demand, user feedback, or competitive analysis to support assumptions about product-market fit.

1. What specific problems do you observe in current ensemble rehearsal workflows that ScoreSync aims to solve?
2. How many ensembles are currently using ScoreSync, and what is their feedback?
3. Are there any existing tools in this space? If so, how does ScoreSync differ from them?
4. What is the plan for scaling beyond a single developer?
5. How do you intend to monetize ScoreSync, if at all?
6. Have you conducted any user research or interviews with directors, section leaders, or musicians?
7. What are the biggest technical challenges you've faced in production and how were they resolved?