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.

CategoryAgri
Effort (estimate)8 team-weeks
Unit BOM (estimate)€15–25
Price (estimate)€69–99
External market checkLikely
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: Young city trees die in dry summers because watering rounds are scheduled, not measured; the departments that have tried sensors pay for a platform per sensor per year, and the ones that have not, water by guesswork.
  • Customer: Municipal green-space departments (Grünflächenämter), their watering contractors, and housing associations; the department's climate-adaptation or tree-maintenance budget pays, often with regional funding.
  • Product: A stake with moisture at two depths and soil temperature, a sealed LoRaWAN head with a five-year cell, a soil-type wizard, open decoders for TTN and city networks, and a map plus a watering list, with no per-sensor platform fee. Target price €69–99 (estimate).
  • Why now: Cities already run funded tree-sensor programmes, the watering of young trees in dry summers is a line item every green department fights over, and the commercial sensors come with a platform fee the municipal IT would rather avoid.
  • The ask: ~€35–45k to certification and a first 1,000 stakes (estimate); three municipal pilots cover half.

External market check (November 2026): LIKELY. Already-funded municipal programmes exist (Vienna "Internet of Trees", Ludwigsburg, Jena, Pforzheim): live demand, not hypothetical. Treesense and FloraPulse exist as competitors but do not publish pricing. Main risk: Get a real competitor quote before claiming to be cheaper. 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.

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 3 cities' green departments order a 50-sensor paid pilot at €89 within one budget cycle? Pass = 3 purchase orders in 12 weeks.

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: Municipal green-space departments with climate-adaptation budgets (Vienna, Ludwigsburg, Jena and Pforzheim already run such programmes), tree-care contractors, housing associations with green space.

The problem as the pack states it: Young city trees die in dry summers because watering rounds are scheduled, not measured; the departments that have tried sensors pay for a platform per sensor per year, and the ones that have not, water by guesswork.

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 (€69–99, 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

Vienna's "Internet of Trees", Ludwigsburg, Jena and Pforzheim show the demand is live, funded and municipal: sensors in the root zone tell the watering crew which trees need the tanker today. The commercial sensors (Treesense, FloraPulse and others) do not publish prices, so the cost advantage must be confirmed with a quote; what they share is a platform fee, and municipal IT departments that run their own LoRaWAN would rather see the data in their own system.

Who pays, B2G: the green-space department, sometimes the city's smart-city or climate programme; watering contractors buy when the city asks for measured watering. Who uses: the watering crew (a list of trees to water today) and the arborist (trends per tree).

Market size (estimates — check)

  • TAM: young street trees in EU cities (planted within the last five years): estimate 10–20M; one sensor per 5–20 trees in a monitored scheme. Theoretical €100M+.
  • SAM: cities with a LoRaWAN network and a tree-watering programme: estimate 300 cities × 300 sensors → €8M.
  • SOM (3 yrs): 20,000–40,000 stakes; year-1: 1,500–3,000 across three pilots and their follow-ons.

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

AlternativeWhat it is / price foundWhy we still win
TreesenseTree sensors with platform (whitepaper found; no public pricing)No platform fee; open decoders; get a quote before claiming cheaper
FloraPulse, Agvolution, PlantcareAgricultural and tree sensors, quote-basedSame
City programmes (Vienna Internet of Trees, Ludwigsburg, Jena, Pforzheim)Already deployed sensor schemesDemand proof and reference customers to learn from
TTN community tree sensorsVolunteer-built stakesThe open precedent; we add a product, a cell life and a calibration

Wedge: no platform fee and open data into the city's own LoRaWAN, with a stake designed for a five-year life in a tree pit.

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
Vienna Internet of Trees; Ludwigsburg, Jena, Pforzheim programmesMunicipal tree-sensor deploymentsFunded demand exists
Treesense (whitepaper)Tree sensors + platform, no public priceIncumbent; quote needed
FloraPulsePlant water-status sensors, no public priceIncumbent; quote needed

Verdict as researched: LIKELY. Main risk: Get a real competitor quote before claiming to be cheaper.

Product & value proposition

  • Two capacitive probes (30 and 60 cm) and a temperature sensor in a glass-fibre stake; sealed head with the LoRa core and an AA-class lithium cell for five years (estimate at hourly uplinks).
  • Soil-type wizard (sandy, loam, clay, substrate) from a one-off reference reading; drift compensation.
  • Open decoders for TTN and the common city LoRaWAN servers; a small map with a "water today" list; CSV and API; no per-sensor fee.
  • Installer kit: pilot drill, depth guide, tree-ID tag.

Unit economics (estimates, EUR per unit)

Item1k units5k units
Electronics BOM (estimate, mid of €15–25)20.016.0
PCBA assembly + test3.02.0
Enclosure / mechanics (tooling amortised separately)6.04.2
Packaging, cable, leaflet2.01.5
Freight + duty to EU (air at 1k, sea at 5k; check the HS code)2.51.2
Certification amortised (€8k, estimate)8.01.6
Landed cost41.526.5
Channel cost (direct B2G and contractor channel, ~€10)10.010.0
Net price received (€84 incl. 19% VAT → €70.6 ex VAT)70.670.6
Gross margin per unit€19.1 (27%)€34.1 (48%)

Lesson: the stake and the sealed head are the cost, not the electronics; design for a five-year life or the city buys twice.

Go-to-market

First 100 customers:

  1. Three green departments found through the cities' smart-city teams and existing programmes, each with a 50-stake paid pilot.
  2. Two watering contractors who want to prove measured watering.
  3. Housing associations with new plantings.

Scale channels: municipal associations and climate-adaptation programmes, LoRaWAN integrators, tree nurseries that supply the trees.

12-month plan

QuarterMilestones
Q1Kill-question conversations with three departments; works-like stake on Stamp C6LoRa + Unit Earth; soil calibration method.
Q2Custom board and stake; EVT 50 in one city over a summer; map and watering list v0.
Q3DVT; certification; 1,000 stakes; two pilots shipped.
Q4Follow-on orders; contractor channel; 3,000 stakes.

Team: one embedded engineer, one developer for decoders and the map, one founder who speaks to municipalities; stake mechanics bought in.

Funding to first production (estimates): NRE €14k + certification €8k + first 1,000 stakes landed ~€25k ≈ €47k; minus pilots ~€13k ≈ €34k.

Top risks

RiskMitigation
Cheap capacitive probes drift and corrodeCoated probes, drift compensation, field test over a summer; reference reading at install
Cities already have a vendorNo fee and open data are the switch argument; integrate with their network, not against it
Procurement cyclesPilots under tender thresholds; regional funding calls
Vandalism / mowersFlush stake head, bright tag, replaceable head
4 · Start kit · boards, BOM, build plan, certification

Start kit

Boards to start from

The Stamp C6LoRa publishes PCB and schematic; the M5Stack and DFRobot moisture boards give three probe options for the prototype; the Seeed sensor board is the open temperature reference.

Block diagram

  TREE PIT: [capacitive probe 30 cm] [capacitive probe 60 cm] [soil temp] -> [ESP32-C6 + LoRa head, sealed] -> city LoRaWAN / TTN
                                                                    [AA lithium cell, 5 years]
  SERVER: open decoder -> map + 'water today' list -> watering crew

Starter BOM (estimates)

PartEst. € (1k)Note
Capacitive probes ×2 (coated)4.0
Temperature sensor1.0
ESP32-C6 + LoRa module6.0
Lithium AA-class cell2.5
Stake + sealed head + tag6.0
PCB, passives2.5

Firmware/software starting point

  • ESP-IDF; hourly uplink, daily temperature profile; soil-type model; LoRaWAN class A with ADR.
  • Decoders published for TTN, ChirpStack and the common municipal servers; map and list as a small open-source app.

12-week build plan

  1. Interviews with green departments; pilot proposal
  2. Prototype stake
  3. Soil calibration experiments
  4. Stake mechanics
  5. Custom board v1
  6. Decoders and map v0
  7. EVT 50 in one city
  8. Summer drift review
  9. Head sealing test
  10. DVT
  11. Pre-compliance
  12. Certification; pilot deliveries

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 3 cities' green departments order a 50-sensor paid pilot at €89 within one budget cycle? Pass = 3 purchase orders in 12 weeks.
  • Cheapest experiment: Ten prototype stakes in one city's new plantings for a summer, the watering list sent to the crew weekly; ask the department whether they would buy 50 at €89.
  • 5-question interview: 1) How do you decide which trees get watered this week? 2) Have you trialled sensors; what did the platform cost? 3) Who signs a €5k pilot and from which budget line? 4) Which LoRaWAN do you have? 5) At €89 per stake with no fee, how many trees?
  • Landing page: headline "Water the trees that are thirsty." Bullets: two depths, five years, your LoRaWAN, no platform fee, €89. Button: request a pilot (B2G).
  • Pass threshold: 3 purchase orders of 50 within 12 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: IP67 immersion test on heads; probe coating inspection.
5 · Who to contact · from gongban.db

Who to contact

On file: 3 board publishers (M5Stack and DFRobot and Seeed Studio). 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 Earth (U019) (soil moisture unit for the first prototype); M5Stack Unit Watering (U101) (capacitive soil moisture + pump reference); M5Stack Stamp C6LoRa (S012) (open ESP32-C6 + LoRa core). 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 SEN0114 (soil moisture sensor, second source). 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.
  • Seeed Studio (矽递科技(深圳)有限公司, seeedstudio.com) — community / maker brand; 183 boards in the catalogue; files via Seeed Studio wiki catalog · github.com/Seeed-Studio/wiki-documents. Directory entry: IoT module + open hardware OEM: XIAO ESP32S3; Grove modules; LoRa gateway; Jetson carrier; OEM PCBA. Boards used here: Seeed Grove-TemperatureAndHumidity Sensor-HDC1000 (soil / air temperature reference circuit). 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.
  • ManThink · manthink.cn/ — open-source LoRaWAN gateway (direct supplier submission): ManThink GD6 open-source LoRaWAN gateway. Supplier reference price (Nov 2026, GD61 indoor, 8 channels): basic Ethernet/Wi-Fi US$50; 4G+PoE US$70; global 4G+PoE US$87; power kit +US$5. MOQ and lead time on request.

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.

  • RAK Wireless (深圳锐凌无线技术有限公司) · rakwireless.com — LoRaWAN gateway / module OEM: RAK2245 / RAK4630 LoRaWAN; Helium compatible; CE/FCC; OEM. (LoRaWAN gateways / modules)
  • Dragino Technology (创联技术(深圳)有限公司) · dragino.com — LoRaWAN gateway / sensor OEM: LG308 LoRa gateway; LHT65 temp/humidity sensor; open-source firmware OEM. (LoRaWAN gateways / 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)

MOQ and landed cost

Apart from the ManThink reference price above, 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 DFRobot and Seeed Studio 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 tree-thirst-sensor · 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 →