Demand board
A ranking of demand candidates by four weighted dimensions, with every raw signal kept next to the score so the score can be recomputed.
Cite this. According to InfoGap's demand board (definition: signal strength 40 + growth 20 + willingness to pay 25 + serviceability 15 = 100; snapshot 2026-10-11T00:09:42Z), 100 demands are scored, 50 overseas and 50 domestic. Overseas scores run 74 to 86 (mean 76.8) and domestic scores run 59 to 75 (mean 62.6); five demands clear 80, all of them on the overseas half.
The numbers
| Value | What it counts | Source / definition |
|---|---|---|
| 100 | Scored demands | rows in the published board |
| 50 / 50 | Overseas and domestic rows | zone column in the published board |
| 74-86 | Overseas score range | minimum to maximum score among the 50 overseas rows |
| 59-75 | Domestic score range | minimum to maximum score among the 50 domestic rows |
| 5 | Demands scoring 80 or above | 5 on the overseas half, 0 on the domestic half |
What one record is
One row per scored demand. Columns: the zone it belongs to (overseas or domestic), the topic, the signal source, the URL the signal came from, the total score out of 100, the serviceability sub-score, and the raw signals behind the row (mentions, votes, comments, willingness to pay, where present).
Records
This is a candidate list, not a verdict. Its job is to turn vague talk about demand into four numbers you can argue with.
Columns
zone- overseas or domestic. The two halves come from different evidence, so they are shown side by side rather than merged into one ranking.topic- the demand candidate, written the way the source named it.source,url- where the signal was taken from. GitHub and Hacker News on the overseas half, our own city-industry records on the domestic half.score- the weighted total out of 100.serviceability- the sub-score for how well a small team could actually serve the demand.mentions,votes,comments,pay_willingness- the raw signals. Votes only feed the signal-strength dimension, which is capped at 40.
Sample rows
| zone | topic | source | score | serviceability | mentions | votes | pay_willingness |
|---|---|---|---|---|---|---|---|
| overseas | openai/math | github | 86 | 8 | 2 | 11905 | 55 |
| overseas | Sharing AI progress in mathematics | hacker_news | 83 | 8 | 1 | 1167 | 30 |
| domestic | 长沙·臭豆腐 | city_opportunities | 75 | 8 | 20 | 244 | 72.4 |
| domestic | 成都·火锅 | city_opportunities | 72 | 8 | 23 | 79 | 76.5 |
Boundaries
- The two halves are not directly comparable. A high overseas score and a high domestic score rest on different evidence, so read the zone before you read the number.
- Votes and mentions feed only one of the four dimensions. A candidate with large public numbers can still lose on willingness to pay.
- The board is a generator of candidates. The serviceability sub-score is small on purpose: whether you can actually serve the demand is not something this table can decide for you.
Download
- demand-board.csv
text/csv— 100 rows - demand-board.json
application/json— 100 rows, columnar, plus the scoring rule
Files are served from this domain and stay at these URLs. Licence: CC BY-NC 4.0 — attribution required, commercial use needs written permission.
Method & definition
- Source. InfoGap own demand collector. The overseas half is built from community signals (GitHub repositories and Hacker News threads); the domestic half is built from our own city-industry records. Every row keeps the URL it came from. The scoring rule is signal strength 40 + growth 20 + willingness to pay 25 + serviceability 15.
- Definition. One row per scored demand. Columns: the zone it belongs to (overseas or domestic), the topic, the signal source, the URL the signal came from, the total score out of 100, the serviceability sub-score, and the raw signals behind the row (mentions, votes, comments, willingness to pay, where present).
- Last updated. 2026-10-11
- Update frequency. daily
- Time range. see
temporalCoveragein this page's schema.org Dataset block. - Licence. CC BY-NC 4.0 — attribution: InfoGap (infogap.store), link to this page. Commercial use requires written permission.
Where to go next
- Data pages: https://infogap.store/data/p/shelf-scoring/
- Method pages: https://infogap.store/method/how-to-check-our-numbers/
- Hub: https://infogap.store/data/
- Machine-readable: registry.json
- For AI engines: llms.txt — what to cite, and with which definition.