Skip to contentSkip to content
About

An intelligence layer for the ecosystem that makes entertainment possible.

We don't create entertainment. We help the entire entertainment ecosystem understand itself, learn from itself, and improve itself.

Tagline
Connect Problems. Synchronize Solutions.
Positioning
Connecting India's Entertainment Ecosystem to Solve What Matters
Guiding principles
10

The authoritative definition

SolutionSynq is the Problem Intelligence and Solution Coordination Layer for the Indian Entertainment Ecosystem.

Status

A proposed intelligence infrastructure. The model on this site is being defined and tested. Nothing described here describes a platform already in service, a research finding already established, or an operating history.

What this is

A coordination layer, not a producer

India's entertainment ecosystem is not short of talent, capital, ambition, or output. What it is short of is a shared understanding of its own problems — and the structures that would let understanding turn into coordinated action. That gap is the thing this project addresses.

What it does

  • Connect fragmented stakeholder experiences into one structured, navigable picture.
  • Distinguish clearly between what has been reported, what has been observed, what has been inferred, and what has been tested.
  • Make the reasoning behind every conclusion visible, including the reasoning that did not survive.
  • Surface where capability and need fail to meet, and where a workable response might land.
  • Retain what was learned — including failures — so the next question starts where the last one ended.

What it does not do

  • We are not a directory, a talent agency, a marketplace, or a production company.
  • We do not manufacture content, commission productions, or take a position in any creative dispute.
  • We do not sell identifiable complaints, or build any product on the grievances of named individuals.
  • We do not publish industry statistics without a reliable source, a date, a context, and a link.
  • We do not claim the engines are operational, and we do not present the architecture as a platform already in service.
Where this fits

The places you should go instead

Most of what this project proposes to organise already exists in some form — casting platforms, professional listings, audience measurement, the federations, the WhatsApp group. Naming them is more useful than pretending they are not there. Here is what each one does, who it is for, and what it does not cover — including the parts where it is plainly better than anything proposed here.

Professional listing

FilmFreeway (opens in a new tab)

Festival and screenplay submission platform. Filmmakers use it to find festivals and screenplay competitions, submit work, and track what happens to it.

Who it is for: Independent filmmakers, writers, and the festival programmers who review their work.

What it does not cover: It handles submission and programming. It does not collect operational problems from crews, and it does not analyse why a production ran late or a payment went wrong.

Professional listing

IMDbPro (opens in a new tab)

Industry profile and contact database for film and television professionals, with credits, representation details, and listings for open roles.

Who it is for: Professionals who already have credits, and the recruiters looking for them.

What it does not cover: It is built around people who are already in the database and the English-language film and television industries. It is not a mechanism for recording a mid-level crew member's work in a Malayalam or Kannada production, and it does not measure whether credits were accurate.

Professional listing

LetsFAME (opens in a new tab)

Indian professional listing service for film professionals, with a directory and a flow of paid job postings. Its own published pricing starts at ₹999 a year for premium access.

Who it is for: Film professionals across Indian languages who want to be found and to see openings.

What it does not cover: It is a listing and posting service, priced and designed for that purpose. It does not verify that the work described in a listing was actually done, and it does not carry evidence about the conditions of that work.

Professional listing

Talentrack (opens in a new tab)

Content marketplace where brands and agencies discover, hire, and collaborate with creators, influencers, and production talent. Talent build a portfolio and are discovered by industry recruiters.

Who it is for: Brands, agencies, and creators working in commercial and influencer content.

What it does not cover: Its marketplace is oriented towards commercial content production. It does not cover the operational, financial, and credit problems that arise inside a narrative production.

Casting and auditions

Castkro (opens in a new tab)

Casting and audition platform for actors, models, dancers, singers, and crew, with profiles and casting-call listings across Indian cities. Applying is free for talent.

Who it is for: Performers looking for auditions, and casting teams filling visible roles.

What it does not cover: It connects talent to open roles. It does not verify whether a person was actually credited after working, which is a separate and recurring failure.

Casting and auditions

AbhinayPath (opens in a new tab)

Audition platform for theatre and performing arts, curating listings from theatre companies, production houses, and independent directors, alongside workshops and mentorship.

Who it is for: Theatre and stage performers, and the producers casting them.

What it does not cover: It is scoped to auditions and creative development. It does not carry the downstream record of who did what, once a project is underway.

Casting and auditions

MyRangManch (opens in a new tab)

Casting platform for performers across India — actors, singers, dancers, and models — with profiles, auditions, and casting calls from verified hirers.

Who it is for: Regional and Marathi-language performers, and the teams hiring them.

What it does not cover: It solves discovery for open roles. It does not record working conditions, payment history, or credit accuracy for people already hired.

Market and box-office data

Box Office India (opens in a new tab)

Publishes daily, weekly, and yearly box-office collection figures for Indian films.

Who it is for: Fans, trade observers, and industry professionals tracking performance.

What it does not cover: It measures revenue at the title level. It does not measure the crew that made the film, the conditions they worked under, or how long the work took.

Audience measurement

Ormax Media (opens in a new tab)

Media measurement and analytics firm for the Indian market, publishing audience and platform research — including audience sizing for streaming — for advertisers and media buyers.

Who it is for: Advertisers, media planners, and the businesses that buy reach.

What it does not cover: Its audience is the buying audience. It does not measure the people who produce the content — the crew whose payment, credit, and working conditions are the subject of this project.

Audience measurement

BARC India (opens in a new tab)

Television audience measurement body for India, running the television viewing panel that underpins television ratings and advertising decisions.

Who it is for: Broadcasters, advertisers, and the television advertising market.

What it does not cover: It measures television viewing. It does not cover digital, regional-language production, or the production workforce at all.

Working institutions

FWICE — Federation of Western India Cine Employees (opens in a new tab)

One of the freelance film workers' federations — among them the body that represented the technicians owed money on the sets that halted production in 2026. The federations represent technicians, press for dues, and stop work to enforce payment.

Who it is for: Freelance technicians and the producers who owe them.

What it does not cover: They act, often successfully, on specific disputes at specific moments. They do not produce a cross-sector record of how problems recur, which is the thing that makes a dispute a structural problem rather than an incident.

Working practice

WhatsApp groups and personal networks

The actual working infrastructure of this industry: crew sourced through WhatsApp production groups, casting through personal introductions, and work found by who you know.

Who it is for: Everyone working in the ecosystem, most of the time.

What it does not cover: They work, which is exactly why they persist. What they cannot do is carry a lesson between two unrelated projects, or let someone outside the network see what the network has already solved.

What SolutionSynq is not a substitute for

The proposal is a layer above these services, not a replacement for any of them. If it ever displaced one of them, that would be a sign it had been built wrong — or that the incumbent had stopped working.

  • Not a substitute for the casting platforms. Finding a role is a job they do well, and better than anything proposed here.
  • Not a substitute for professional listings or contact databases. They are cheaper, faster, and already have the network.
  • Not a substitute for audience measurement or box-office reporting. Those figures are audited against their own methods, and this project would consume them rather than reproduce them.
  • Not a substitute for the craft federations. They hold leverage this project has no pretence of holding, and their ability to stop work is what makes payment enforceable.
  • Not a substitute for the WhatsApp group or the phone call. A structure that is slower than the informal channel will not be used, and should be discarded if it is not.
  • Not a substitute for a producer's own judgement about their project. Nothing here is a creative decision, and nothing here should be treated as one.

Every service named above was checked against its own public site before being listed, and each is described by what it actually does rather than by how it compares to this project. Where a service could not be verified, it was left off this list rather than named on a guess.

Accountability

Who is responsible, and for what

There is no named founder or registered entity behind this site yet, and it will not invent one. What follows is the scope of accountability that exists today — stated as plainly as the facts allow — along with the one channel that genuinely works.

What is accountable today

The project can be held to these, because they are things it has already done rather than things it intends to do.

  • Every claim on this site is traceable. Where a number appears, the source, its date, and a link appear with it, and the limits of what that source establishes are stated alongside it.
  • Every hypothesis states the evidence that would support it, the evidence that would weaken it, and the intervention it would imply — before any of it is treated as established.
  • The research method is written down, including the stages the project refuses to skip, and the reason for each refusal.
  • Submissions are recorded with a reference, a status, and a timestamp, and a contributor can retrieve and check what is held against their own submission at any time.
  • Where this site is wrong, the correction is made in public on the page where the claim sits, rather than quietly edited.

What is not established

Stated plainly so that nothing here has to be inferred, and so that no reader mistakes silence for a claim.

  • No individual is named as founder or operator. The project has not yet established a person or a registered entity behind it, and it will not name one before that is true.
  • No founding date, no funding history, and no operating history can be claimed, because none is established.
  • No institutional partner, client, member, or funder is named, because none is.
  • No credential, qualification, award, or prior affiliation is attributed to anyone.
  • No headcount, revenue, or adoption figure is claimed, because the site has no users to measure yet.

The channel that works today

This site has no mail server behind it, so it does not promise to reply by email — that promise could not be kept, and an unkept promise is worse than no promise. There is one channel here that is real and verifiable: the submission record.

  • Send a problem or an expression of interest, and you are given a reference on the page.
  • Use that reference with your email address at any time to retrieve what is recorded against your submission: when it arrived, what state it is in, and any amendment attached to it.
  • The record is the correspondence. It does not depend on anyone remembering to answer, and it does not expire quietly.
  • A wrong or unwanted record can be corrected or withdrawn through the same route — the form is the way back in, and the reference is what ties the correction to the original.

What changes when there is someone to name

  • When an accountable person or entity exists, this section will say so, state the scope of that accountability in one line, and link to a monitored channel — before the site is used to ask anyone for anything.
  • The privacy policy already states that submissions are not anonymous and not confidential. That constraint will remain in force and will be restated at the point the name appears, not after.
  • Nothing on this site will present a claim as more settled than it is because a name is attached to it.
Guiding principles

Ten rules that shape every decision

Each principle is written as a decision rather than a value, because a value only becomes real when it rules something out. The last line of each is the part that costs something.

  1. 01

    The ecosystem is the client

    We are not building for one part of the industry. We are building for the system.

    Every decision is tested against the whole: a solution that helps one group at the cost of another is not an improvement, it is a transfer. The unit of value is a more capable ecosystem, not a better quarter for any single participant.

    Out solutions that require one group's loss to be another group's gain, and out anything built to extract value from a segment rather than create it.

  2. 02

    Problems before products

    We start from a problem someone actually experiences, never from a feature.

    The first question is always what is happening and to whom. A solution arrives second, and only if the problem has been understood well enough to know what a solution would need to change — and what it would risk changing instead.

    Out feature-first thinking, out anything built because it is technically possible, and out tooling that produces records nobody can use.

  3. 03

    Evidence over assertion

    We show the reasoning, not only the conclusion.

    A conclusion without its evidence, limitations, and counterevidence is a claim, not intelligence. Every output carries what supports it, what does not, and what would change it — because a system that cannot be argued with cannot be improved.

    Out claims stated with more confidence than the evidence allows, and out conclusions that are published without their disconfirming material.

  4. 04

    Context is not optional

    A finding without its context is not a finding. It is a generalisation.

    Industry, region, language, role, scale, and timeframe travel with everything we hold, because they determine what a finding means and whether it can travel at all. Context is preserved even when preserving it makes a finding less impressive.

    Out universal claims drawn from one market, and out the practice of smoothing over differences in order to produce a cleaner answer.

  5. 05

    Intelligence comes to the work

    The system should reach people where they already are, not ask them to come to it.

    Value that requires a person to log in, learn a system, and re-enter what they already know is value most people will not collect. Coordination has to happen at the point where work happens — inside the workflows, meetings, and conversations that already exist.

    Out requiring the ecosystem to become researchers for our benefit, and out standing up an administrative layer on top of work that already works.

  6. 06

    The unseen matter

    We design deliberately for the people the record ignores.

    Attention, capital, and policy follow measured revenue and public profile. A system that only captures what is visible will describe the visible part of the ecosystem and call it the whole. Inclusion is designed in, audited, and reported — not hoped for.

    Out sampling strategies that would deepen existing blind spots, and out reporting an unrepresentative corpus as if it were the ecosystem.

  7. 07

    Failure is a result

    What did not work is retained, attributed, and as useful as what did.

    Most research disappears quietly: a finding is produced, a report is written, the report is filed, and the same question is asked again from scratch six months later. Failed interventions are first-class records, and the loop only closes when learning returns to listening.

    Out discarding failed attempts, out generalising a lesson beyond the context it was learned in, and out measuring the system by the volume of activity it generates.

  8. 08

    Consent is a relationship

    Consent is specific, informed, revocable, and visible to the person who gave it.

    People contribute because the exchange is worth something to them, and they stay because it continues to be. Contributors can see how their input was used, correct it, withdraw it, and contest conclusions drawn from it — and the system records the effect of doing so.

    Out collection that is broader than its stated purpose, out retention without a reason, and out promising a level of confidentiality that the infrastructure cannot deliver.

  9. 09

    Coordination, not control

    We help people act. We do not act on the industry's behalf.

    The system identifies who can responsibly do something, and makes the choice legible. Responsibility stays with the people who have the authority to act, and participation is never presented as endorsement of the system itself.

    Out acting on anyone's behalf, out presenting participation as endorsement, and out replacing judgement with a recommendation engine.

  10. 10

    Learn across boundaries

    Practice travels as a method to adapt, never as an answer to copy.

    One region's answer to one region's constraint is rarely another region's answer. When practice moves between contexts, the originating constraints travel with it, and the receiving context re-derives what actually applies.

    Out importing solutions that assume a different market, and out publishing a practice without the conditions that made it work.

India, specifically

A federation, not a market

Indian entertainment is multilingual, regionally distributed, economically uneven, and culturally specific. Treating it as one market is the most common analytical error in the industry — and the one that produces the most confident, well-intentioned, ineffective policy.

  1. 01

    Multilingual by design

    Language is not a translation layer applied after the fact. The research question, the framing, and the analysis are designed with the language in mind from the start.

  2. 02

    Regional context preserved

    Findings carry the context in which they were produced. A finding from one language economy is not presented as a finding about another.

  3. 03

    Different stakeholder groups represented

    The record is checked against the actual composition of the ecosystem, and the gaps are published rather than smoothed over.

  4. 04

    Solutions evaluated in their actual contexts

    An intervention that works in one production market is tested in the market it is meant for, with its constraints intact.

  5. 05

    Knowledge shared without erasing cultural difference

    Practice travels between regions as a method to adapt, not as an answer to copy. The originating context travels with it.

Data & privacy principles

What we ask for, what we keep, and what we will never do.

  • We ask only for what the stated purpose requires, and we do not request detail that serves no analytical purpose.
  • Collection is consent-based, purpose-bound, and revocable. Contributors can correct, withdraw, or restrict what they have contributed.
  • We will not sell identifiable complaints, and we do not build commercial products on the grievances of named individuals.
  • Information is held only as long as it remains useful and consented, and is then deleted rather than archived indefinitely.
  • We do not promise anonymity or a level of confidentiality that the underlying infrastructure and operating process cannot actually guarantee.