Concept, not a product. Concept generated by the GONGBANS inventor from the public catalogue, then expanded into a start pack. Not a product, not validated; every number (market, BOM, price, effort, certification cost) is a rough estimate to be checked, not a quote. Check each board's licence before commercial use. Not legal, tax or investment advice.

New here? Start here → explains what a gongban is, the four steps and the first-timer mistakes. Come back to this pack afterwards.

CategoryDisplays
Effort (estimate)14 team-weeks
Unit BOM (estimate)€120–180
Price (estimate)€599–899
External market checkUncertain · flagged
Boards referenced6 catalogue boards

Order of operations: read the summary, then validate demand (section 2) with real customers before you touch the start kit or e-mail anyone in Who to contact (section 5). New to hardware? The zero-experience founder playbook covers validation, samples, the first quote, CE/FCC, customs and fulfilment for all 50 ideas.

1 · Summary · the one-page version

Summary

  • Problem: Outside cities, a bus stop is a pole and a laminated sheet; when the bus is late nobody knows, and the agency displays that could tell them cost €2,000–5,000 each plus a service contract, so rural stops never get one.
  • Customer: Landkreise and regional transport associations (B2G) in regions whose operators publish GTFS and GTFS-Realtime; municipalities that co-fund stop furniture; dial-a-ride and community bus operators. The transport association's passenger-information budget pays.
  • Product: An A4-class e-paper sign in an IP65 housing with solar panel and buffer cell, Cat-M (or LoRaWAN where a town network exists), showing the scheduled departures from GTFS at all times and live times where GTFS-Realtime exists for that stop, with the source stated on screen. Target price €599–899 (estimate).
  • Why now: Rural stops have paper timetables and no information at all when a bus is late; agency displays cost €2,000–5,000 with service contracts; e-paper, Cat-M and solar make a €800 sign possible, and open GTFS data is spreading region by region.
  • The ask: ~€90–120k to certification and a first 200 signs (estimate); two paid pilots cover a third.

External market check (November 2026): UNCERTAIN. A real technical blocker: live GTFS-Realtime requires on-board vehicle equipment that rural and small-contractor bus fleets often lack (confirmed in a Südtirol example), so buses without it show only scheduled times, in exactly the rural markets targeted. Municipal e-paper stop displays (Meisenheim, Ludwigsburg) and regional GTFS-RT open data (VBN) exist. Main risk: The pitch was reworked before building: scheduled always, live where available, with the source labelled on screen; scope sales to regions that already publish GTFS-RT. As researched November 2026 by web search; verify before relying on it. Verdicts are a reading of the evidence found, not a forecast. Competitors and sources found: see the market check in the competition table.

Built with the research fix applied (November 2026). The research found that live departure data needs on-board equipment many rural fleets lack, so a sign promising live times everywhere would fail in its own target market. This pack is therefore scoped to "scheduled always, live where the operator broadcasts it", the sign labels which it shows, and the kill question only counts regions that already publish GTFS-Realtime for their stops. As researched November 2026 by web search; verify before relying on it.

2 · Validate demand · before anything else

Validate demand first

Do this before anything else in this pack: before the business plan, before you order a sample board, and long before you e-mail a factory (section 5). The classic first-time mistake is to source and build first and find out later that nobody wanted it. Hardware mistakes are slow and expensive to undo; 15–20 conversations are cheap.

The gate: this idea's kill question

Do 2 Landkreise or transport associations whose operators already publish GTFS-Realtime sign a paid 10-stop pilot at €799 per sign within 8 weeks? Pass = 2 signed pilots; a region without GTFS-RT at its stops does not count.

You pass this section when you can answer that question with evidence you collected yourself, not a guess: written answers from at least ten decision-makers who hold the budget, at least three of whom put something on paper: a signed letter of intent, a paid pilot, or a dated purchase order for the first units. Until then: no factory e-mail, no sample order, no firmware, no logo. If the answer is no, you have lost a few weeks and saved the rest.

Who you are looking for

The audience named in the idea: Landkreise and regional transport associations whose operators already publish GTFS-Realtime (for example VBN and other open-data regions), small municipalities, rural bus operators; B2G procurement.

The problem as the pack states it: Outside cities, a bus stop is a pole and a laminated sheet; when the bus is late nobody knows, and the agency displays that could tell them cost €2,000–5,000 each plus a service contract, so rural stops never get one.

Talk to the people who have the problem and the people who pay; in B2B they are often not the same person, and the one who pays decides.

Where to find them

Communities and associations where this audience actually talks, as far as we know them in November 2026. Confirm each is still active and read its rules on self-promotion before posting; most allow a genuine question about a problem and ban a pitch.

Beyond the named ones, the same four methods work for every idea on this site:

  • Search for communities around the problem, not the product: forums, Facebook groups, Discord servers and newsletters in your own country for the terms in the audience line above. Many of the best groups are national and in the local language; a Dutch or German group beats a global English one for an EU launch.
  • Trade associations and their regional meetings for the B2B audiences: one meeting puts twenty buyers in a room, and the association newsletter will often run a short survey for a member.
  • LinkedIn: search people by the job titles in the audience line, message ten a day with one question (not a pitch), and ask for twenty minutes. Expect one in five to say yes.
  • Your deposit list from the kill question and anyone who replied to the fake door: those are the first interviews, not the last.

The plan: 15–20 conversations, then a fake door

  1. 15–20 real conversations (ten budget-holders and ten users), fifteen minutes each, using the script below. Before writing a line of code or ordering a board. Write up each one the same day: the problem in their words, what they do today, what it costs them, what they said when you named the price.
  2. A fake door. One page: the pitch as the headline, a rendered image or a photo of a cardboard mock-up, the price (€599–899, the pack's estimate), and one button. For a business buyer the button is "request a pilot" that leads to a short form and a letter of intent.
  3. Send it to everyone you interviewed and post it, with the problem question first, in the communities above. Run it for two to four weeks.
  4. Count against the kill question. Then decide: go, change the idea, or stop.

Interview script (fifteen minutes, problem first)

Ask, then be quiet. Do not describe the product until question 5; if you pitch first you will only hear politeness.

Pre-order / pilot message (forum post or direct message)

Reading the signal

Real signalFalse positive
A refundable deposit, a signed LOI, a paid pilot, a calendar invite for the prototype"Sounds cool", "I would totally buy that", likes and upvotes
They describe the problem unprompted and in detail, with numbersThey agree with your description of the problem
They have already paid for a workaround (a product, a service, their own time)They have never tried anything and are not bothered
Landing-page conversion to deposit or form above the pack's pass mark, from cold trafficConversion from friends, family and your own network
A named budget and a named decision-maker (B2B)An enthusiastic user who cannot buy

Go / no-go

  • Go to section 3 (business plan) and section 4 (start kit) when the kill question above is met by your own numbers, you have 15–20 written-up conversations, and at least one real signal from the left column per segment you plan to sell to. Only then does section 5 (Who to contact) apply.
  • Change the idea when the problem is real but the price, the buyer or the form factor in the pitch is wrong: the interviews will tell you which. Rewrite the pitch and run the fake door again; this is normal and costs a week.
  • Stop when the kill question fails on honest numbers, or when nobody you talked to has paid for a workaround. Pick another idea on this site; the boards in the start kit are not wasted, only unused.

The full worksheet, with how to define the segment and run the fake door, is in the playbook → validate demand.

3 · Business plan · estimates, not a forecast

Business plan

Problem & customer

Research for this pack confirmed the catch: live departure data needs on-board equipment in the vehicle, and rural or small-contractor fleets often lack it, so a sign that promises "live" everywhere lies in exactly the places that need it most. The product is therefore scoped: timetable always, live where the operator broadcasts it, and the sign says which. Even the scheduled-only mode replaces a laminated sheet that is often out of date, and the live overlay arrives as operators equip their fleets (regions such as VBN already publish GTFS-Realtime as open data).

Who pays, B2G (primary): transport associations and Landkreise from passenger-information and stop-furniture budgets, often with regional or EU funding for rural mobility. Who uses: passengers, including older people without a smartphone, which is the political argument for the sign.

Market size (estimates — check)

  • TAM: ~300,000 bus stops in Germany, the large majority without any display; similar density in AT/CH/NL/FR. Theoretical €200M+ at €800.
  • SAM: stops in regions with open GTFS feeds and a rural-mobility programme: estimate 30,000 stops → €25M.
  • SOM (3 yrs): 1,500–3,000 signs across 10–20 regions. Year-1: 100–200 signs in two pilots and two follow-on orders.

Competition (4 searches, incl. the November 2026 external market check)

AlternativeWhat it is / price foundWhy we still win
Papercast, Luminator, ConnectPointAgency-grade e-paper and LED stop displays, €2,000–5,000 per sign plus service (quote-based)A third to a fifth of the price, no service contract, open data in
Paper timetableFree, out of dateWe show the same timetable, always current, plus live where it exists
Municipal pilot displays (Meisenheim, Ludwigsburg examples)Individual municipalities already trial e-paper stop displaysDemand signal and a procurement precedent
DIY e-paper transit boards (the hallway-board family)Hobby buildsProof of the display idea; not an outdoor product

Wedge: price and honesty: a quarter of the agency display, no service contract, and a sign that says "scheduled" or "live" so the passenger can trust it.

External market check

Competitors, demand signals and price comparables found by web search in November 2026. Sources are named as found and not linked; as researched November 2026 by web search; verify before relying on it. Verdicts are a reading of the evidence found, not a forecast.

Who / sourceWhat it isWhat it tells us
Südtirol real-time caveatBuses without on-board equipment do not report live positionsThe 'live' promise cannot hold everywhere; pitch reworked
Meisenheim, Ludwigsburg municipal display examplesMunicipalities trialling e-paper stop displaysDemand and procurement precedent
VBN GTFS-Realtime open dataRegional live feed published openlyTarget regions exist
Papercast, Luminator, ConnectPointAgency displays, quote-based €2–5kIncumbents at a multiple of the target

Verdict as researched: UNCERTAIN. Main risk: The pitch was reworked before building: scheduled always, live where available, with the source labelled on screen; scope sales to regions that already publish GTFS-RT.

Product & value proposition

  • 7.5–13.3 inch e-paper, readable in sunlight, backlight for night, in a vandal-resistant IP65 housing on a standard pole clamp.
  • Solar panel and buffer cell sized for a northern winter at ten refreshes an hour (estimate; validate in December).
  • Cat-M modem with an operator SIM or the region's IoT SIM; LoRaWAN variant where a town network exists.
  • Firmware: GTFS static for the stop, GTFS-Realtime overlay when the feed carries that stop's trips, a "scheduled / live" label, disruption text, QR to the operator's app.
  • Fleet dashboard for the association: battery, last refresh, uptime; open API; no per-sign licence.

Unit economics (estimates, EUR per unit)

Item1k units5k units
Electronics BOM (estimate, mid of €120–180)150.0120.0
PCBA assembly + test15.09.8
Enclosure / mechanics (tooling amortised separately)60.042.0
Packaging, cable, leaflet8.06.0
Freight + duty to EU (air at 1k, sea at 5k; check the HS code)12.06.0
Certification amortised (€15k, estimate)15.03.0
Landed cost260.0186.8
Channel cost (direct B2G, tender support and installation partner, ~€60)60.060.0
Net price received (€749 incl. 19% VAT → €629.4 ex VAT)629.4629.4
Gross margin per unit€309.4 (49%)€382.7 (61%)

Lesson: the housing and the pole mount cost as much as the electronics; design one housing for two display sizes. Procurement support time is the hidden cost; price it into the pilot.

Go-to-market

First 100 customers:

  1. Two transport associations with open GTFS-Realtime, found through their open-data portals, offered a paid ten-stop pilot.
  2. Municipalities that already trialled e-paper stop displays, offered the cheaper second generation.
  3. Dial-a-ride and community-bus operators that need a sign at a handful of stops.

Scale channels: regional mobility programmes and funding calls, stop-furniture suppliers, the association's own roll-out plans.

12-month plan

QuarterMilestones
Q1Kill-question conversations with four associations; works-like sign on PaperS3 + Unit CatM reading one region's GTFS and GTFS-RT; December solar test.
Q2Custom board, housing, pole mount; EVT 5 signs at real stops with one association.
Q3DVT; certification; 50 signs; first paid pilot shipped and installed.
Q4Second pilot; fleet dashboard; 200 signs; funding-call partnerships.

Team: one embedded engineer, one backend developer (GTFS, dashboard), one founder for B2G sales; housing design and installation partner bought in.

Funding to first production (estimates): NRE €40k (board, housing tooling, mount) + certification €15k + first 200 signs landed ~€50k ≈ €105k; minus two pilots ~€16k ≈ €90k.

Top risks

RiskMitigation
Regions without GTFS-Realtime at their stopsScope to regions that publish it; scheduled-only mode is honest and still useful; say which mode on screen
Winter solar budgetMeasure in December before DVT; larger panel or mains option
Vandalism and weatherPolycarbonate window, tamper alert, replaceable front; warranty terms
Procurement cycles of 6–18 monthsPaid pilots under tender thresholds first; partner with a stop-furniture supplier
4 · Start kit · boards, BOM, build plan, certification

Start kit

Boards to start from

The PaperS3 and PaperColor give the display path; the SIMCom A7672X hardware design is the openly mirrored reference for the cellular section; the DFRobot solar power manager covers the off-grid power path for prototypes.

Block diagram

  [solar panel] -> [solar power manager + LiFePO4 cell] -> [ESP32-S3]
                                                            |  SPI
  [Cat-M modem (A767x)] <-- GTFS / GTFS-RT every 6 min --> [e-paper 7.5–13.3"]
  [temp sensor] [tamper switch]        label on screen: SCHEDULED | LIVE

Starter BOM (estimates)

PartEst. € (1k)Note
E-paper 7.5–13.3 inch + driver45.0size per stop
ESP32-S3 module3.0
Cat-M modem + antenna + SIM holder15.0
Solar panel 10–20 W + power manager20.0
LiFePO4 cell12.0
IP65 housing + pole clamp + polycarbonate window60.0two display sizes, one housing family
PCB, sensors, passives8.0

Firmware/software starting point

  • ESP-IDF; GTFS static parsed server-side per stop and pushed as a compact schedule; GTFS-RT polled server-side and pushed only when the stop's trips are in the feed.
  • Partial e-paper refresh; deep sleep between refreshes; battery and temperature telemetry.
  • Server: small open-source service per region (GTFS ingest, per-stop API, fleet dashboard); no per-sign licence.

12-week build plan

  1. Interviews with associations; fake door for B2G
  2. Prototype on PaperS3 + CatM with one region's GTFS
  3. GTFS-RT overlay and the scheduled/live label
  4. Solar budget measurement
  5. Custom board v1
  6. Housing and mount design
  7. EVT 5 at real stops
  8. Association feedback; dashboard v0
  9. Housing tooling decision
  10. DVT signs
  11. Pre-compliance
  12. Certification; pilot contract

Certification checklist (EU)

  • RED via the module's own radio reports (EN 300 328 / EN 300 220 as applicable, EN 301 489 EMC), EN 18031 cybersecurity for the connected variant, EN 62368-1 safety (USB-powered, no mains inside), RoHS/REACH, WEEE registration per country, CRA vulnerability-handling process.
  • Test with the DVT build in the real enclosure; budget a re-spin for EMC.
  • Lab cost: a few thousand euros for a USB-powered device with a pre-certified module, more with battery or multiple radios (estimate; get two quotes).
  • Battery Regulation (EU) 2023/1542 and UN 38.3 for the lithium cell; user-replaceable or documented removal.

Validation toolkit

  • Kill question: Do 2 Landkreise or transport associations whose operators already publish GTFS-Realtime sign a paid 10-stop pilot at €799 per sign within 8 weeks? Pass = 2 signed pilots; a region without GTFS-RT at its stops does not count.
  • Cheapest experiment: One PaperS3 in a weatherproof box at one rural stop for a month with the association's blessing, showing scheduled times; count the passengers who ask for it to stay.
  • 5-question interview: 1) Which of your stops have any display today and what did it cost per stop? 2) Does your GTFS-Realtime feed cover rural lines; which operators are equipped? 3) Who decides on stop furniture and from which budget? 4) What would a sign need to do for you to put ten on poles? 5) At €799 per sign without a service contract, how many stops in a pilot?
  • Landing page: headline "A departure sign every stop can afford." Bullets: timetable always, live where your buses report, solar, €799, no service contract. Button: request a pilot (B2G form).
  • Pass threshold: 2 signed ten-stop pilots in regions with GTFS-RT within 8 weeks.

First production checklist

  • 10 golden samples measured and photographed; one per enclosure colour.
  • DFM review with the PCBA house: test pads, programming jig, serial/MAC provisioning, who holds the signing keys (you).
  • MOQ talk: module, enclosure, packaging; get the next price break in writing.
  • QC: AQL II 2.5/4.0; 100% functional test incl. radio; burn-in sample.
  • Packaging and label: CE, WEEE bin, responsible-person address, model/serial; manual with safety and disposal text.
  • Incoterm and shipping: DDP by courier for the first run; forwarder quote for the second.
  • Outdoor: IP65 ingress test on samples, UV-stable window, salt-spray on the clamp if coastal.
5 · Who to contact · from gongban.db

Who to contact

On file: 3 board publishers (M5Stack and SIMCom and DFRobot). Only useful once section 2 (validate demand) has passed. Everything below comes from gongban.db, the directory behind this site. It names the companies that publish the boards this idea is built from, the manufacturers on file, and directory entries in the same product category. None of it is a verified supplier relationship for this specific idea: nobody has quoted it yet. Company websites only; no personal contacts are published.

Board publishers (direct)

  • M5Stack — community / maker brand; 274 boards in the catalogue; files via M5Stack M5_Hardware repo · github.com/m5stack/M5_Hardware. Boards used here: M5Stack PaperS3 (C139) (ESP32-S3 e-paper device for the prototype sign); M5Stack PaperColor (C151) (colour e-paper variant for line colours); M5Stack Unit CatM (U128) (Cat-M unit for the prototype); M5Stack Stamp C6LoRa (S012) (LoRaWAN backhaul where a town network exists). What to ask for: sample units of the SKUs above, unit pricing at 100 / 500 / 1,000, whether a customised variant is possible (and its NRE and MOQ), and the module's radio test reports if any.
  • SIMCom — solution house; 3 boards in the catalogue; files via SIMCom module hardware designs · simcom.com/technical_files-p110.html. Boards used here: SIMCom A7672X/A7670X Series Hardware Design (Cat-1/Cat-M cellular module hardware design for the backhaul). What to ask for: sample units of the SKUs above, unit pricing at 100 / 500 / 1,000, whether a customised variant is possible (and its NRE and MOQ), and the module's radio test reports if any.
  • DFRobot — community / maker brand; 250 boards in the catalogue; files via DFRobot wiki catalog · wiki.dfrobot.com/. Boards used here: DFRobot DFR0535 (solar power manager for the off-grid post). What to ask for: sample units of the SKUs above, unit pricing at 100 / 500 / 1,000, whether a customised variant is possible (and its NRE and MOQ), and the module's radio test reports if any.

Manufacturing (PCBA / EMS) on file

  • Kingbrother / King Brother Technology · global.kingbrother.com/ — PCB fab + EMS; see the Kingbrother SOM page on this site.
  • Foxlink (SZ) (正崴精密工业(深圳)有限公司) · foxconn.com — PCBA + cable assembly EMS: Cable assembly; PCBA; connector; OEM for major electronics brands.

Also in the directory (category match, not idea-specific)

Companies in the gongban.db solution-house directory whose product category overlaps this idea. They were matched on the idea's tags, not on this design; none has seen it.

  • iDisc Technology (深圳市艾迪思科技有限公司) · no website on file — E-ink display module / e-reader OEM: E-ink display module; e-reader gongban; retail price tag; OEM/ODM. (E-ink display modules)
  • GREPOW (深圳格瑞普电池有限公司) · grepow.com — High-rate Li-Po / NiMH battery OEM: High-drain Li-Po; shaped/custom battery; NiMH; UAV battery. (Custom Li-Po / NiMH batteries)
  • Luat (Air105/Air780) (深圳市合宙通信有限公司) · openluat.com — LTE Cat-1 / NB-IoT module OEM: Air780E Cat-1 bis module; Air105 MCU; MQTT/TLS; OEM/ODM. (Cellular (Cat-1 / NB-IoT) modules)
  • LILYGO (深圳市合宙通信有限公司) · lilygo.cc — ESP32 / LoRa / cellular dev module OEM: T-SIM7670 / T-Watch / TTGO LoRa boards; OEM module supply. (Cellular (Cat-1 / NB-IoT) modules)

MOQ and landed cost

gongban.db holds no MOQ, unit-price or tariff data for these companies, so none is shown. Get the numbers from the quote (the e-mail below asks for them) and run them through the landed-cost worksheet in the playbook. The starter BOM in the start kit section is an estimate, not a quote.

Outreach e-mail, ready to send

Fill in the [brackets], keep it short, and send it to the sales or "contact us" address on the company's own website. The Chinese version is the same letter; sending both in one mail is normal. How to read the reply: playbook → the first quote.

A. To a board publisher — samples and volume price (send to the sales / "contact us" address on the M5Stack and SIMCom and DFRobot websites)

A. 中文版

B. To a PCBA / EMS house — quote from the open design files (send to Kingbrother, Foxlink or any assembler you vet; see the playbook)

B. 中文版

6 · Next steps · this week

Next steps (this week)

  1. Run section 2 (validate demand): book the first ten conversations and put the fake door up before touching a board.
  2. Order the sample boards in the start kit (three of each) and build the works-like prototype on the desk.
  3. Send e-mail A to the board publisher and e-mail B to one PCBA house (section on who to contact) to learn the real numbers behind the estimates above.
Get this built

Want this built?

Get sourcing and manufacturing help from a team in Shenzhen and Europe.

Never built hardware? Start with the zero-experience founder playbook: samples, the first quote, CE/FCC, customs, logistics and the kill question, in order. Board facts come from the catalogue; everything else in this pack is an estimate.

Get this built →

Start pack village-stop-display · written by the GONGBANS inventor from the public catalogue and public sources. Concept generated by the GONGBANS inventor from the public catalogue, then expanded into a start pack. Not a product, not validated; every number (market, BOM, price, effort, certification cost) is a rough estimate to be checked, not a quote. Check each board's licence before commercial use. Not legal, tax or investment advice. Idea page · Download as Markdown · All 50 start packs →