Skip to content
IdeaScore

Built for the People Who Run the Call

Running a fair, well-documented selection is harder than it looks. Most institutions build the workaround in spreadsheets.

The team around a table at dusk, sketches and laptops open

A Platform for the Whole Life of a Call

IdeaScore takes an institution from opening applications to funding teams: a configurable multi-stage form collects submissions, a review workflow triages and flags them, evaluators score against a shared rubric across as many rounds as the programme needs, and an AI co-evaluator researches every application on the public web and shows its sources beside the human score. Live pitch days and committee-ready reports close out the call.

The same platform then tracks the teams a programme decides to fund, so a research park or accelerator can keep one record from first application to portfolio company. It runs either in our cloud or on an institution’s own server, because a public university and a private accelerator have different constraints and neither should be forced into the other’s answer.

From the first application to the funded cohort: forms, review, rubric scoring over as many rounds as you need, IdeaScore AI research with its sources, pitch days and committee reports. In our cloud or on your own server.

Stages in every call
4
Field types
11
Roles with their own access
5
Deployment options
2

Built for One Call, Then Generalised

CMS Group built the first version of IdeaScore to run a research park’s seed-fund call, self-hosted on the institute’s own server. Programme teams have run live calls on it since 2025.

The multi-tenant platform, the version that lets many institutions run independent, white-labelled programmes from one console, followed in 2026.

CMS Group built the first IdeaScore for one research park’s seed-fund call, on the institute’s own server. Live calls have run on it since 2025; the multi-tenant platform followed in 2026.

The Principles Behind Every Screen

Taken from the product's own design principles, written for people outside the team.

  • Operate first

    Every screen exists to help someone finish a task: triage a submission, score a pitch, make a decision. We design for clarity and speed under real deadlines, not for show.Every screen helps someone finish a task under a real deadline.

  • Evidence beside judgement

    Scores, AI research and sources sit next to each other on the same screen. Nothing about how a number was reached is hidden from the people who have to defend it.Scores, AI research and sources sit side by side, so every number can be defended.

  • Calm density

    A programme can run to hundreds of applications. The interface has to stay readable at that scale, so hierarchy comes from type and spacing, not boxes and colour.Readable at hundreds of applications: hierarchy from type and spacing, not boxes.

  • Built once, run by many institutions

    Every tenant gets its own branding and configuration, but the same underlying structure, so a committee can trust the process even when the logo on top changes.Each institution's own branding, on one structure a committee can trust.

Who We Are

IdeaScore is built by CMS Group in Dehradun, Uttarakhand, India. Product, engineering and support work side by side, so a question about the platform reaches the people who can answer it. Founded in 2024.

Open roles

See IdeaScore Run a Call with Your Own Rubric

A 30-minute walkthrough with a product specialist, using your programme's form and criteria.

IdeaScore