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)8–12 team-weeks
Unit BOM (estimate)€30–45 (estimate)
Price (estimate)€149–199 per post (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: Wild boar destroy maize, cereals and grassland in a few nights, especially when maize is in the milk stage. Farmers and hunters don't know when and where the animals enter. Hunters sit for many nights in vain; camera traps need SD-card checks or expensive 4G plans, and cameras on field edges photograph walkers (privacy).
  • Customer: In Germany and several neighbouring countries the hunting-ground tenant often pays for game damage on farmland (the details depend on national/regional hunting law and the lease contract). That makes the hunter/hunting tenant a strong buyer, alongside arable and maize farmers, vineyards and orchards in DE, PL, FR, BE, AT.
  • Product: A solar post unit with a 5.8 GHz motion radar aimed along a game trail, night-only arming, a LoRa radio that sends "movement at trail 3, 23:41" to the farmer and the hunter, and a configurable output for a light/sound deterrent or relay. Several posts per field form a simple trail map; an event log shows when animals come.
  • Why now: Wild-boar populations and damage stay high; African swine fever pressure keeps authorities pushing for more effective boar hunting; LoRa radios and Doppler radars cost a few euros; no camera = no privacy problems with walkers.
  • The ask: About €120–160k (estimate) to the first 1,000 posts, via season pre-orders from hunting associations, an agri-innovation grant and one angel from the hunting/agri-supply trade.
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

Does a radar alert actually lead to less damage? Pilot with 3 farms and their hunting association for one season; without measurable damage reduction, it's a toy.

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: Arable and maize farmers, vineyards, orchards and hunting associations in DE, PL, FR, BE, AT where wild-boar damage is severe.

The problem as the pack states it: Wild boar destroy maize, cereals and grassland in a few nights, especially when maize is in the milk stage. Farmers and hunters don't know when and where the animals enter. Hunters sit for many nights in vain; camera traps need SD-card checks or expensive 4G plans, and cameras on field edges photograph walkers (privacy).

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.

  • DJV, Deutscher Jagdverband (DE) · jagdverband.de/ — German hunters' association; wild-boar damage on crops is a standing topic.
  • FACE · face.eu/ — European federation of hunting associations.
  • Landtreff (DE) · landtreff.de/ — German farmers' forum.
  • The Farming Forum (UK) · thefarmingforum.co.uk/ — UK farmers; machinery, arable, livestock, farm diversification.
  • r/farming · reddit.com/r/farming/ — working farmers.

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–199 per post (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

Primary buyer: the hunting-ground tenant (or a group of hunters sharing a district) who pays game-damage compensation and wants to sit at the right spot on the right night. Secondary: farmers with high-value crops (maize, vineyards, orchards, potatoes) who want proof and early warning. Third: hunting associations / district hunting groups for shared systems in ASF-related efforts.

User: whoever gets the alert — hunter on the phone, farmer in the morning summary.

Market size (estimates)

  • Germany alone has hundreds of thousands of licensed hunters and tens of thousands of hunting districts; similar structures exist in AT, PL, FR, BE. Assume ~150k hunting districts across the core countries with significant boar damage in maybe 30% → ~45k districts, 4 posts each.
  • TAM: 45k × 4 × €169 ≈ €30 M hardware + optional alert service.
  • SAM: districts with LoRaWAN coverage or willing to buy a gateway, DE/AT/PL first, ~30% → ~€9 M.
  • SOM (3 years): 3% of SAM → ~1,600 posts → ~€270k. A niche — but hunters spend money on equipment readily (thermal optics, cameras), and the season makes demand predictable.

Competition

AlternativePrice (estimate)Weakness we attack
4G trail cameras with app alerts€150–400 + SIM/subscriptionMonthly costs per camera, photograph walkers (privacy/legal issues on public paths), battery drain, no coverage in some fields
Acoustic/light wildlife scarers (e.g. randomised sound devices for crops)€100–500Habituation; no information for the hunter; neighbours complain about noise
Electric fencing around high-value fields€1–3 per metre + labourEffective but labour-intensive; not practical around every maize field
Thermal binoculars + sitting every night€1,500–5,000 + timeWorks when you are there; most nights you're there for nothing
Do nothing: pay the damage€100s–€1,000s per hectare damagedThat's what we reduce

Wedge: "know when they come, without a camera or a SIM": low-cost trail radars over LoRa, a nightly event log, and an instant alert so the hunter sits on the right nights. Deterrent output as an extra, randomised to slow habituation.

Product & value proposition

  • Sensor: Hi-Link HLK-LD016 — 5.725–5.875 GHz Doppler motion sensor, TX −5 dBm, 5 V / 20 mA, detection 6–10 m (adjustable), UART config, 2 GPIO, −30 to +80 °C, 20 × 20 × 12 mm. Mount low (0.6–1 m) along the trail, angled to reduce triggers from swaying crops. Test the false-alarm rate with maize moving in the wind — Doppler sensors see moving leaves.
  • Radio: HopeRF RFM95W (868 MHz LoRa) for LoRaWAN or direct to a small farm/hunter base station. For pilots: M5Stack Unit LoRaWAN-EU868.
  • Power: 2–3 W solar panel + LiFePO4; the radar draws ~20 mA continuously at night → ~0.25 Ah per night plus the deterrent; size for 5 dark days.
  • Logic: night-only arming (light sensor/clock), sensitivity per trail, "event" = sustained movement for N seconds (ignore single blips), daily summary, instant alert option, deterrent output (12 V switched: light bar, sound module) with random timing.
  • Optional: a second radar per post facing the other way; temperature for context; a "hunter mode" that suppresses the deterrent so the animals are not scared away while the hunter is coming.

Pricing (estimates): €169 per post (radar + LoRa + solar); €449 starter kit with 3 posts + gateway set-up help; deterrent add-on €49. Optional SMS alert service €3/post/month.

Unit economics (estimates per post, ex-VAT)

Item1k units5k units
BOM (LD016, RFM95W, MCU, light sensor, LiFePO4 + charger, 2–3 W panel, relay/MOSFET output, antenna, PCB)€30.00€23.00
Assembly & test€4.00€2.80
Enclosure (UV-stable, IP66) + post clamp€7.00€4.80
Packaging€1.50€1.00
Freight + duty to EU€2.20€1.50
Certification amortised (~€18k)€18.00€3.60
Landed cost€62.70€36.70
Net revenue (direct €142 ex-VAT; hunting-supply dealer €100)€142€100
Gross margin€79.30 (56%)€63.30 (63%)

Go-to-market

First 100 customers:

  • Hunting fairs (large ones in Germany and Austria each winter/spring): demo with a radar on a post and a phone showing the alert.
  • District hunting groups / hunting association chapters: offer a 3-district pilot in a known boar-damage region before the maize milk stage; publish the results in hunting magazines.
  • Farmer–hunter pairs: the farmer suffers the damage, the hunter pays it → they often want to cooperate. Sell the starter kit to the pair.
  • Hunting forums and online communities, plus the big hunting-equipment webshops' review sections.

Scale: hunting-supply retailers (online + stores), agri-merchants, and agricultural chambers' advisory services.

12-month plan

QuarterMilestones
Q1Works-like posts; false-alarm tests (wind, crops, rain, deer vs boar); 3 pilot districts signed
Q2EVT 30 posts installed before the maize milk stage; alert + log app; hunting-mode logic
Q3The pilot season itself: measure alerts → successful hunts → damage area vs previous year; DVT + RED testing in parallel
Q41,000 posts produced for next season; dealer listings; pilot report published

Team: founder with hunting/farming credibility, 1 embedded engineer (radar signal + LoRa + solar), part-time app developer (alerts, event log). A wildlife biologist as advisor for the pilot design.

Funding to the first 1,000 posts (estimates): NRE €45k (PCB + firmware €25k, enclosure/clamp tooling €10k, app €10k) + certification €18k + 1,000 posts landed ~€40k + pilot costs €10k + 12 months lean costs €40k ≈ €155k. Minus pre-orders for next season (300 × €150 ≈ €45k) and an agri/wildlife-management innovation grant (€20–50k) → ~€60–90k funding. Route: bootstrap + pre-orders + grant + hunting-trade angel.

Top risks

RiskMitigation
Technical: false alarms from moving crops, rain, foxes, deerLow mounting along trails, sustained-motion logic, per-post sensitivity; accept "animal" alerts and let the hunter judge
Technical: 6–10 m range only covers trails, not fieldsSell per trail; qualify a longer-range radar later; multiple posts per field
Market: no measurable damage reductionKill question: one-season pilot with damage measured vs previous year and vs control fields
Regulatory: hunting law (e.g. rules about electronic aids at night, feeding sites, protected periods), noise/animal-protection rules for deterrentsPosition as information device; check each country's hunting law with associations; deterrents optional and within noise limits
Theft/vandalism in open fieldsLow-profile housing, camouflage colours, cheap enough to lose occasionally
Supply: sole-source radarDoppler 5.8 GHz modules are widely available; keep the footprint generic
4 · Start kit · boards, BOM, build plan, certification

Start kit

Boards to start from

BoardLinkWhat it contributesFiles (catalogue)Licence note
Hi-Link HLK-LD016 5.8 GHz motion radargongbans.com/db/hilink-ld016.htmlNight motion detection on a trail (6–10 m, adjustable)Datasheet public, files via maker (no open schematic/PCB)Commercial module; ask Hi-Link for the UART config protocol and RED report
HopeRF RFM95/96/98(W) LoRa modulegongbans.com/db/hoperf-rfm95-96-98w.html · GitHub folder868 MHz LoRa/LoRaWAN alertsPCB footprint/library, datasheet, demo codeMIT (HopeRF GitHub repo)
M5Stack Unit LoRaWAN-EU868 (U184-EU868)gongbans.com/db/m5stack-unit-lorawan-eu868.htmlQuick LoRaWAN for the pilot unitsEnclosure/structure files only — main-board electronics not publishedPrototype only

Block diagram

[2-3 W solar] -> [LiFePO4 charger] -> [LiFePO4 cell] -> [3.3 V / 5 V rails]
                                                              |
[LD016 5.8 GHz radar] --GPIO/UART--> [low-power MCU] --SPI--> [RFM95W 868 MHz] ~~LoRaWAN~~> [gateway] -> [server] -> [hunter/farmer app + SMS]
[light sensor (night arming)] ----->        |
                                   [MOSFET/relay 12 V out] -> [optional light bar / sound module (random timing)]

Engineering gap: the false-alarm logic (the hardest part in fields), solar power budget with the radar on all night, the post clamp/enclosure, the alert app with hunter mode, and pilot methodology to prove damage reduction.

Starter BOM (estimates at 1k)

PartEst. costNotes
HLK-LD016€2.00–3.00Doppler radars are widely available; second-source easily
RFM95W-868€4.50
Low-power MCU€1.50
2–3 W solar panel (UV-stable)€5.00
LiFePO4 cell 3 Ah + charger€7.00Block charging below 0 °C
MOSFET/relay output + connector€1.50
Antenna, PCB, passives, light sensor€3.50
Enclosure + clamp€7.00Tooling ~€8–10k

Firmware/software starting point

  • LoRaWAN: LoRaMac-node (github.com/Lora-net/LoRaMac-node); for Arduino prototypes, search "MCCI LoRaWAN LMIC".
  • Network server: The Things Stack (community) for pilots; ChirpStack (open source) for a hunter's own gateway.
  • Alerts: webhook → push/SMS; a Node-RED flow is fine for the pilot season.
  • Radar config: Hi-Link's UART protocol (from the maker).

12-week build plan

WeeksPhaseExit criteria
1–2Validate10 interviews with hunters/farmers in a high-damage region; 3 districts sign a paid pilot (€100 deposit each); bench: LD016 detects a person walking at 8 m, logs wind-blown plant movement
3–5Works-like6 posts on real trails for 3 weeks; compare alerts with a borrowed trail camera (ground truth, on private land only); false alarms <2 per night per post
6–8Looks-like + EVTCustom PCB + enclosure + clamp; 30 posts; 5-dark-days power test; hunter-mode app
9–10DVT + pre-complianceRED pre-scan (5.8 GHz SRD + 868 MHz), EMC, IP66, −20 to +60 °C cycling
11–12Pilot batch50 posts in the 3 pilot districts with a damage-measurement protocol agreed with the farmers (ha damaged vs previous year/control fields)

Certification checklist (EU)

  • CE under RED: 5.8 GHz Doppler radar as SRD — confirm the harmonised standard used for the module (e.g. EN 300 440 for SRD in that band — confirm with the lab); 868 MHz: EN 300 220-1/-2 (duty cycle); EMC: EN 301 489-1/-3; safety EN 62368-1; EN 62479. Est. €10–15k.
  • RED delegated act (EN 18031-1): LoRaWAN node via gateway — assume it applies; self-assessment ~€2–5k.
  • CRA: reporting from 11 Sept 2026, full from 11 Dec 2027: update path, SBOM, vulnerability handling.
  • IP66 test (EN 60529); UV resistance.
  • RoHS, REACH, WEEE, packaging registration.
  • Battery Regulation (EU) 2023/1542: LiFePO4 cell labelling, removability, take-back; UN 38.3 for shipping.
  • Deterrents: noise limits (national/municipal), animal-protection rules; some countries restrict certain scaring devices — check per market.
  • Hunting law: use of electronic aids and alerts in hunting varies by country/state — get a written position from a hunting association before marketing "hunting support".
  • GDPR: no camera → low risk; hunter/farmer contact data and field locations are personal data → EU hosting, privacy notice.
  • Total estimate: €15–25k.

Validation toolkit

  • Kill question: Does a radar alert actually lead to less damage? One season with 3 farms and their hunters; without measurable damage reduction, it's a toy.
  • Cheapest experiment (~€500): 3 dev-kit posts (LD016 + LoRa + powerbank) on known trails for 3 weeks, alerts by SMS to one hunter; count alerts, confirmed sightings and hunts.
  • 5-question interview (hunter/farmer): 1) How much game damage did you pay or suffer last year, and on which crops? 2) How many nights did you sit without seeing boar? 3) What do you use now: cameras, scarers, fences? What failed? 4) Would an alert at 23:41 "trail 3" make you go out? 5) At €169 per post and no subscription, how many posts would you buy before the maize season?
  • Landing page headline: "Know when the boar come — without a camera or a SIM." Bullets: "Radar posts on game trails alert you the moment animals enter your field." / "Night log shows patterns so you sit on the right nights." / "Solar powered, LoRa, optional light/sound deterrent."
  • Pass threshold: 3 paid pilots + 30 pre-orders (€30 deposit) for next season from hunting fairs.

First production checklist

  • Samples: radar modules from 2 suppliers compared on the same trail.
  • Golden sample: with radar sensitivity setting, firmware version and false-alarm test results recorded.
  • DFM review: radar window (no metal paint), drainage, condensation vent, clamp for wooden and metal posts, camouflage colour.
  • MOQ talk: solar panel custom size, LiFePO4 cells, enclosure colour.
  • QC/AQL: AQL II 1.0/2.5; 100% radar trigger test (moving target jig), 100% LoRa join, 100% charge test.
  • Packaging: compact box, clamp hardware, quick-start with QR onboarding, trail-placement guide.
  • Incoterms: FOB Shenzhen; ship before the season (Q1) — sea freight takes 5–7 weeks.
5 · Who to contact · from gongban.db

Who to contact

On file: 3 board publishers (Hi-Link (海凌科) and HopeRF (华普微) and M5Stack). 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)

  • 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-LD016 5.8 GHz long-range motion-detection radar module (adjustable distance) (5.8 GHz long-range motion radar (adjustable distance)). 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.
  • HopeRF (华普微) (深圳市华普微电子股份有限公司, hoperf.com) — chip house; 122 boards in the catalogue; files via HopeRF Product Portfolio (GitHub, MIT) · github.com/HOPE-MICROELECTRONICS/Product_Portfolio. Directory entry: RF chip house + module maker: Sub-GHz transmitter/receiver/transceiver ICs (CMT2xxx) and RFM modules; LoRa modules (RFM9x, RFM6601); BLE SoCs + modules; Matter-over-Thread / Wi-Fi modules; digital isolators. HopeRF publishes datasheets and, for some products, schematic and PCB files in its public GitHub portfolio (MIT licence). Boards used here: HopeRF RFM95 / 96 / 98(W) Low-power long-range LoRa transceiver module (LoRa transceiver for alerts to the farm). 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.
  • 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 LoRaWAN-EU868 (U184-EU868) (LoRaWAN unit for pilots). 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 Hi-Link (海凌科) and HopeRF (华普微) and M5Stack 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. Order 5 LD016 samples and 3 RFM95W modules; test detection range and wind false alarms in a garden hedge.
  2. Call 5 hunters in a known boar-damage district and ask who paid how much damage last year.
  3. Ask a regional hunting association whether they would co-run a measured pilot next season.
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 field-edge-wildlife-alarm · 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 →