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.

Effort (estimate)10–12 team-weeks
Unit BOM (estimate)€30–40 (estimate)
Price (estimate)€149 + €4/month (estimate)
Boards referenced3 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 100 ideas.

1 · Summary · the one-page version

Summary

  • Problem: One loud night costs a short-stay host far more than a cleaning fee: neighbour complaints, building-association fights, platform penalties and, in cities like Amsterdam, Barcelona, Lisbon, Paris and Berlin, fines or a lost permit. Hosts find out the next morning.
  • Customer: Professional short-stay hosts and management companies with 5–200 units in strict EU cities. They pay. Guests are "users" only in the sense that they see the warning light.
  • Product: A small mains-powered box: on-device dB(A) metering from a PDM microphone (level only, audio never stored or sent), a 24 GHz multi-target radar (Hi-Link LD2452) for a rough "how many people are moving in this room" signal, and an LTE-M uplink that doesn't depend on the guest Wi-Fi. Escalation: an in-room light and short voice/beep nudge to the guests first, then a message to the host.
  • Why now: Cities are tightening short-stay rules and revoking permits over nuisance; platforms push hosts towards noise monitoring and have banned indoor cameras. The incumbents are subscription-first (around €10–15 per unit per month) and infer occupancy from Wi-Fi devices rather than people.
  • The ask: About €130–160k (estimate) to the first 1,000 units. Route: pre-orders from management companies + a small angel round. Revenue: €149 device + an optional €4/month plan (or no plan, with local alerts only).
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

Will 30 hosts pay €149 + monthly when incumbent noise monitors exist? Differentiator must be people-count + no-subscription option; test with a host forum survey and 10 pre-orders.

You pass this section when you can answer that question with evidence you collected yourself, not a guess: a measured conversion on a fake-door landing page for the consumer side and, for the business side, at least three decision-makers who put something on paper: a letter of intent, a paid pilot or a purchase order. 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: Short-stay hosts and management companies in Amsterdam, Barcelona, Lisbon, Berlin, Paris where nuisance rules and permits are strict.

The problem as the pack states it: One loud night costs a short-stay host far more than a cleaning fee: neighbour complaints, building-association fights, platform penalties and, in cities like Amsterdam, Barcelona, Lisbon, Paris and Berlin, fines or a lost permit. Hosts find out the next morning.

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 buyers from the business side and ten from the consumer side), 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 (€149 + €4/month (estimate), the pack's estimate), and one button. Two buttons: a refundable deposit or waitlist for consumers, "request a pilot" for businesses.
  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

Hosts don't want to spy on guests. They want early warning and a record that they acted, because that's what a city inspector, a building association or a platform asks for after a complaint. The guest-first escalation matters: most groups turn it down when a light goes amber; a host call at 01:00 is the second step, not the first.

Who pays: management companies (10–200 units) first. They buy in batches, handle installation during cleaning turnovers, and have a nuisance-compliance problem with their city. Then: individual pro hosts with 2–10 units, through host communities.

Who doesn't buy: hosts renting a room in their own home (they're there), and the big hotel-like operators (they have night staff).

Market size (estimates)

  • Short-stay listings in the EU are in the low millions; assume ~1.5 M entire-home listings in cities with active nuisance enforcement (estimate, check current platform/Eurostat short-stay data).
  • TAM: 1.5 M × (€149 + 3 years × €48) ≈ €440 M over a 3-year device life.
  • SAM: professionally managed units in NL, ES, PT, FR, DE, IT big cities, ~30% → ~450k units ≈ €130 M.
  • SOM (3 years): 1.5% of SAM → ~7,000 units ≈ €1 M device revenue + ~€330k/yr recurring.

Competition

AlternativePrice (published/listings, estimate)Weakness we attack
Minut (Swedish, sensor + platform)Subscription per unit, roughly $10/unit/month for add-on plans or ~£120/yr core plan per property (published, varies by market)Subscription-heavy; occupancy estimate is not a people count
NoiseAwareStarter ~$15/month per property; outdoor sensor $99 one-time (published, US-centric)US focus, no EU pricing published; relies on Wi-Fi
Roomonitor, Alertify and similarDevice + monthlySimilar model; Wi-Fi-dependent
Building/smart-home sound sensors (DIY with a sound meter + home automation)€30–100 + timeNot practical across 20 units; no audit trail
Do nothing; deal with complaintsFree until the finePermit risk, bad reviews from neighbours, platform penalties

Wedge: (1) people count from radar, not "number of phones on Wi-Fi" (guests can turn Wi-Fi off; radar doesn't care), (2) LTE-M uplink so the guest can't "unplug the router" to blind it (but see power: unplugging the box itself still needs a tamper alert), (3) no-subscription option with local nudges and an SMS to the host, (4) a ready-made disclosure kit (listing text, sticker, house rules) for GDPR and platform policies.

Honest limitation: the LD2452 tracks up to three targets per sensor (per Hi-Link's datasheet), within ~6 m. So the "people count" saturates at 3+ per room. That's still a useful party signal ("3+ people moving in the living room at 01:30 with 78 dB(A)") but it isn't a headcount. A second sensor in the large room or a combined dB + motion-density heuristic gets you further. Don't market "counts guests".

Product & value proposition

  • Noise: on-device A-weighted level (Leq over 1 min, peak, and "time above threshold"), using a PDM MEMS mic. Firmware never stores or transmits samples: only levels leave the chip. Publish the firmware audit or the relevant source to prove it.
  • Occupancy: LD2452 in the main living area, wall-mounted horizontally (as the datasheet specifies), gives 0–3+ moving targets.
  • Escalation: quiet-hours schedule per unit (e.g. 22:00–07:00), thresholds per building. Step 1: in-room amber light + a short chime. Step 2 after 10 min: host alert (app push / SMS / webhook into the property-management system). Step 3: log entry "host contacted guest at 01:12" for the record.
  • Connectivity: LTE-M (Cat-M) so it works without guest Wi-Fi; a Wi-Fi-only SKU for cheaper deployments.
  • Tamper: "device offline/unplugged" alert; mains-powered with a small backup capacitor or cell to send the last-gasp message.

Pricing (estimates): €149 device (LTE-M), €119 Wi-Fi only. Plans: €0 (local nudge + SMS to host, limited), €4/unit/month (dashboard, PMS integration, history export for authorities). Management-company bundle: 10 units for €1,290.

Unit economics (estimates per unit, ex-VAT)

Item1k units5k units
BOM (MCU/Wi-Fi module, PDM mic, LD2452, LTE-M module + SIM holder, LED ring, buzzer, AC-DC, PCB)€36.00€29.00
Assembly & test (radar + mic level calibration with a reference source, LTE-M attach test)€3.50€2.50
Enclosure (wall-mount, light-pipe ring)€2.50€1.50
Packaging + disclosure sticker kit€1.50€1.00
Freight + duty to EU€1.20€0.80
Certification amortised (~€35k: RED incl. cellular, EMC, LVD for mains, EN 18031)€35.00€7.00
Landed cost€79.70€41.80
Net price ex-VAT: direct ~€125 (from €149 incl. VAT) / via reseller or PMS partner ~€90€125 / €90€125 / €90
Gross margin (device)€45 (36%) direct / €10 (11%) reseller€83 (67%) / €48 (54%)

Recurring: cellular data at ~€0.50–1/unit/month (IoT SIM, estimate) means the €4 plan nets ~€3; the free plan costs you ~€0.50–1/month per unit forever. Fix that before launch: either include 24 months of connectivity in the device price and charge after, or make the free tier Wi-Fi-only. At 1k units the device margin is thin through resellers: sell direct for the first batch.

Go-to-market

First 100 customers:

  • Host associations and short-stay management meetups in Amsterdam, Barcelona, Lisbon, Berlin, Paris. Management companies show up there.
  • Host forums and Facebook/LinkedIn groups for professional short-stay hosts: run the kill-question survey there.
  • Property-management system (PMS) marketplaces: an integration listing is a sales channel in itself.
  • Building associations / owner associations with nuisance problems: they can recommend (or require) it for units rented short-stay.

Scale channels: PMS and channel-manager partners, insurers that cover short-stay damage (discount for monitored units), city "good host" programmes.

12-month plan

QuarterMilestones
Q1Host survey + 10 pre-orders (kill question); works-like box on devkits in 5 friendly units; legal check on in-dwelling monitoring in 3 target countries
Q2Custom PCB with LTE-M; firmware with level-only audio pipeline; dashboard v1; EVT 50 units with 2 management companies
Q3DVT, RED/EMC/LVD/EN 18031 testing; PMS integration #1; launch at a host event
Q41,000 units shipped; paid plan live; insurer/PMS partnership conversation

Team: founder (sales into host/management companies), 1 embedded engineer (audio DSP for dB(A), radar, LTE-M), 1 full-stack developer (dashboard, alerts, PMS integration), part-time privacy/legal adviser.

Funding to the first 1,000 units (estimates): NRE €70k (electronics €15k, firmware €25k, dashboard/alerts €20k, enclosure + soft tooling €10k) + certification €35k + 1,000 units landed ex-cert ~€45k + connectivity year 1 ~€8k + 9 months lean costs €40k ≈ €198k; minus pre-orders (~300 units × €125 ≈ €37k) → ~€160k. Route: management-company pre-orders, then an angel from the proptech/hospitality space.

Top risks

RiskMitigation
Market: incumbents are established and platform-endorsedDon't fight on features; fight on "people, not phones", LTE-M and the no-subscription option. Validate with 10 pre-orders before building
Legal/privacy: monitoring inside a dwellingLevel-only audio, no images; mandatory disclosure in the listing and on the device; DPIA template; legal check per country (DE is strictest); never market as surveillance
Technical: dB(A) accuracyCalibrate each unit against a reference source at end of line; specify "indicative, not a class-1/2 sound level meter"
Technical: radar count saturates at 3 targetsCommunicate honestly; optional second sensor; use motion density + noise over time
Platform policy changesTrack platform host policies for noise monitors; disclosure kit updated
Recurring cost of the free plan (cellular)Wi-Fi-only free tier or a time-limited bundled data plan
Supply: LD2452 single sourceAbstract the radar protocol layer; qualify an alternative multi-target radar module
4 · Start kit · boards, BOM, build plan, certification

Start kit

Boards to start from

BoardLinkWhat it contributesFiles (catalogue)Licence note
M5Stack Unit Mini PDM (U089)gongbans.com/db/m5stack-unit-mini-pdm.htmlPDM MEMS microphone for dB level metering in the works-like prototypeEnclosure/structure files only (main-board electronics not published)Dev unit; production uses your own mic layout
Hi-Link HLK-LD2452 multi-target radargongbans.com/db/hilink-ld2452.htmlTracks up to 3 targets, 6 m, ±60° H / ±30° V, UART, 5 V avg 126 mA (per datasheet)Datasheet public; schematics/files via maker (contact Hi-Link)Commercial module, no open design files
M5Stack Unit CatM (U128)gongbans.com/db/m5stack-unit-catm.htmlLTE-M uplink independent of guest Wi-Fi, for prototypingEnclosure/structure files onlyDev unit; production uses a pre-certified LTE-M module

Block diagram

[PDM mic] --PDM--> [MCU (ESP32-class)] -- dB(A) Leq/peak only, no samples leave the chip
[LD2452 radar] --UART-->     |
                             |-- amber LED ring + chime (guest nudge)
                             |-- LTE-M module --> [cloud: alerts, dashboard, PMS webhook]
                             `-- Wi-Fi (optional SKU)
[mains] -> [isolated AC-DC] -> [5 V / 3.3 V] + last-gasp capacitor for the "unplugged" alert

Engineering gap: A-weighting filter and Leq computation on the MCU (with a provable "no audio leaves" pipeline), radar mounting and zone tuning for living rooms, escalation logic and quiet-hours schedules, LTE-M power and provisioning, tamper/offline detection, the host dashboard and PMS integration.

Starter BOM (estimates at 1k)

PartEst. costNotes
ESP32-S3 or -C3 module€2.50Enough DSP for A-weighting at 16 kHz
PDM MEMS microphone€0.60Pick one with a published sensitivity tolerance
HLK-LD2452 radar€7–9Sole source (Hi-Link); confirm price and MOQ
LTE-M module (pre-certified) + SIM holder/eSIM€9–12Long-lead risk; cellular operator certification can take weeks
IoT SIM (per unit, first year)€6–10Recurring
Isolated AC-DC 5 W€2.50Or USB-C wall adapter version (avoids LVD on the device)
LED ring, buzzer, button, passives, PCB€3.00

Firmware/software starting point

  • ESP-IDF with the I2S/PDM driver; A-weighting filters are standard IIR biquads (search "A-weighting IIR biquad coefficients 16 kHz").
  • Radar: Hi-Link's LD2452 serial protocol from the datasheet; ESPHome has community components for related Hi-Link radars (search "ESPHome LD2450") that show the frame format style.
  • Cellular: the LTE-M module vendor's AT command set; M5Stack's Unit CatM examples for the prototype (search the M5Stack docs).
  • Backend: any EU-hosted stack; alerts via SMS gateway and push; webhooks for PMS systems.

12-week build plan

WeeksPhaseExit criteria
1–2ValidateKill question: host-forum survey (≥80 answers) + 10 pre-orders/deposits from hosts or management companies. Pass: ≥10 deposits and ≥40% of surveyed pros rate "people count without cameras" as a top-2 reason
3–5Works-likeDevkits in 5 real units: dB(A) within ±2 dB of a reference meter; radar 0/1/2/3+ classification correct ≥85% of 5-min windows; host alert end-to-end over LTE-M
6–8Looks-like + EVTCustom PCB, wall-mount enclosure, LED ring; 30 units at 2 management companies; guest nudge resolves ≥60% of events without host contact
9–10DVT + pre-complianceRED pre-scan (24 GHz, LTE-M, 2.4 GHz), EMC, safety; EN 18031 gap analysis; privacy review of the audio pipeline
11–12Pilot batch50 units deployed; < 1 false host alert per unit per month; 2 management companies ask for a quote for all units

Certification checklist (EU)

  • CE under RED: 24 GHz radar (EN 300 440), LTE-M (EN 301 908-1/-13; use a pre-certified module to reuse its reports), 2.4 GHz (EN 300 328), EMC (EN 301 489 series), safety EN 62368-1, RF exposure. Mains-powered device: the safety assessment covers LVD-type risks; a USB-adapter version simplifies this. Est. €15–22k.
  • RED delegated act cybersecurity: EN 18031-1, -2 (processes personal data: noise level + presence inside a home) and -3 if any payment features (no). Est. €8–12k.
  • CRA: reporting from 11 Sept 2026, full from 11 Dec 2027: signed OTA, SBOM, vulnerability handling, support period.
  • RoHS, REACH, WEEE, packaging registration.
  • GDPR (big one): noise levels and presence in a rented dwelling are personal data about guests. Legal basis = the host's legitimate interest, with transparency: disclosure in the listing, in the house rules and on the device. DPIA template for management companies. Data minimisation: store levels/counts, delete raw timelines after e.g. 30 days. Check national rules on monitoring inside dwellings (and ePrivacy if anything touches communications).
  • Platform policies: check each short-stay platform's current rules on noise monitors (typically allowed if disclosed, decibel-only; cameras inside banned).
  • Total estimate: €25–35k.

Validation toolkit

  • Kill question: Will 30 hosts pay €149 + monthly when incumbent noise monitors exist? The differentiator must be people count + a no-subscription option; test with a host forum survey and 10 pre-orders.
  • Cheapest experiment (~€0–200): a landing page with the €149 offer and a €20 refundable deposit, posted in 5 host communities, plus 10 calls with management companies. No hardware needed yet.
  • 5-question interview (host / management company): 1. How many nuisance complaints did your units get last year, and what did each one cost you? 2. What do you use today to know about a party before the neighbours call? What's wrong with it? 3. How do you disclose monitoring to guests today? Ever had a guest complain about it? 4. Would you pay more for "how many people are there" versus "how loud"? How much more? 5. Device €149 with no subscription, or €49 + €10/month: which, and for how many units?
  • Landing-page headline: "Know about the party before the neighbours do."
  • Measures noise and people. Never records sound or images.
  • Warns the guests first, then you, over its own mobile link.
  • No subscription needed. Disclosure kit included.
  • Pass threshold: ≥10 paid deposits (≥3 from management companies) within 4 weeks, or one management company signing a 50-unit letter of intent.

First production checklist

  • Samples: mic sensitivity spread across 20 samples (decides whether per-unit calibration is needed); radar modules from the production lot.
  • Golden sample: calibrated dB reading at 94 dB(A) reference, radar target test, LTE-M attach; firmware hash recorded.
  • DFM review: mic port acoustic path (sealing gasket, no cavity resonance), radar window material and thickness, LED light-pipe, mains creepage distances if AC-DC inside.
  • MOQ talk: LTE-M module (operator variants), radar module, LED ring parts.
  • QC/AQL: AQL II 1.0/2.5; 100%: mic level at reference tone ±1 dB, radar detects a reference target, LTE-M registers, LED/buzzer check, firmware audio pipeline locked (debug ports disabled).
  • Packaging: device, mounting kit, disclosure sticker for the door and the device, listing-text card with QR code to the privacy notice.
  • Incoterms: FCA Shenzhen; air for the pilot; consider DDP for the first batch so customs (radio + cellular) isn't your problem.
5 · Who to contact · from gongban.db

Who to contact

On file: 2 board publishers (M5Stack and Hi-Link (海凌科)). 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 Unit Mini PDM (U089) (PDM microphone used only for dB level, no audio stored); M5Stack Unit CatM (U128) (Cat-M uplink independent of the guest Wi-Fi). 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.
  • Hi-Link (海凌科) (深圳市海凌科电子有限公司, hlktech.com) — module maker; 155 boards in the catalogue; files via Hi-Link (Shenzhen Hi-Link Electronic) product catalogue · hlktech.com. Directory entry: WiFi / BLE / radar sensor / power module maker: WiFi & router modules (MT7688/MT7628/WiFi6); BLE modules; 5.8/10/24/60/79 GHz mmWave radar sensors; AC-DC & DC-DC power modules; face / fingerprint recognition modules. Datasheets are public on hlktech.com (download centre); anything beyond the public datasheets has to be asked from Hi-Link directly. Boards used here: HLK-LD2452 24 GHz multi-target positioning and tracking radar module (multi-target radar for a rough people count). 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.

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 Hi-Link (海凌科) 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. Put up the landing page with a €20 refundable deposit and post it in 5 host communities and 2 management-company networks.
  2. Order 5 LD2452 modules, 5 PDM mic units and an LTE-M dev unit; get a dB(A) reading within ±2 dB of a cheap reference meter on the bench.
  3. Ask a privacy lawyer for a one-hour check on "level-only noise + radar presence in a short-stay rental" in DE, NL and ES; turn the answer into the disclosure kit.
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 party-noise-guard · 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 100 start packs →