GroveProof

1. One-liner

Collects farm geolocation, checks it against deforestation maps, and files your EUDR due-diligence statement per shipment — for importers too small to afford the €12K/yr enterprise tools.

2. Trend signal — why now?

The EU Deforestation Regulation (EUDR) starts biting on 30 December 2026 for medium/large operators and 30 June 2027 for SMEs. From those dates, anyone placing coffee, cocoa, cattle, palm, rubber, soy or wood on the EU market must file a Due Diligence Statement (DDS) in the EU TRACES NT system — per shipment — carrying farm-level geolocation (point coordinates for plots under 4 ha, full polygons over 4 ha), a deforestation risk assessment, and proof of legal, deforestation-free production since 31 Dec 2020.

The pain is not hypothetical and it’s not evenly served:

• 73% of EU coffee roasters remain unprepared; 89% have done zero supply-chain traceability work since the regulation was announced in 2023 (industry analysis, Fiegenbaum Solutions).
• A documented roaster paid €450/day in storage trying to retroactively obtain farm coordinates, gave up after 23 days, and dumped the container to a non-EU buyer at a 40% loss — ~€72,000 gone (Fiegenbaum Solutions).
• >10% of submitted farm polygons contain errors (overlaps, self-intersections, mismatched coordinates) — “instant red flags” at the compliance check (Specialty Coffee Association).
• Manual DDS filing through TRACES NT is “time-consuming and prone to human error… manual setups won’t scale to shipment-level DDS” (TraceX).

And the incumbents have drawn my map for me. EUDRReady (the only cheap tool, €29–79/mo) states plainly it is built for downstream traders buying from EU intermediaries and is “not suitable for direct importers from origin countries” — no geolocation, no satellite, no TRACES submission (all “Phase 2”). It tells those customers to go buy osapiens / TraceX, whose entry price is ~€12,000/yr and assumes a dedicated sustainability manager. Nobody serves the direct small importer/roaster affordably.

Provenance:

• Signal 1 (demand): “73% of EU coffee roasters unprepared, 89% zero traceability work”; €72K container-loss anecdote from chasing farm coordinates — https://www.fiegenbaum.solutions/en/blog/eu-deforestation-regulation-eudr-coffee-industry-challenges-strategies — 2026-07-06
• Signal 2 (feasibility): TRACES NT DDS submission API is public (CIRCABC docs, SOAP v2), system relaunches June 2026 ahead of the deadline; EU JRC GFC2020 map + free Global Forest Watch Data API provide the official 2020 deforestation baseline at 10m — https://tracextech.com/eu-traces-eudr-compliance-dds-submission/ , https://data-api.globalforestwatch.org/ — 2026-07-06
• Signal 3 (economic): Enterprise EUDR entry price ”~€12,000/yr… not appropriate for a small coffee roaster or artisan chocolate maker”; funded incumbents (osapiens, TraceX, Source Intelligence, IntegrityNext) all chasing the enterprise tier — https://eudrready.eu/eudr-software-small-business/ — 2026-07-06 Category: Regulatory arbitrage

3. The opportunity

A hard-deadline regulation created a mandatory, repeating, per-shipment task — and the software market bifurcated into (a) a €29/mo tool that explicitly refuses to do the hard part (origin geolocation + satellite + TRACES filing), and (b) €12K/yr enterprise suites priced for companies with a compliance department.

The direct small importer and direct-trade roaster sits in the gap. They buy green coffee/cocoa/wood straight from origin cooperatives and exporters, file a handful of DDS a month, have no sustainability staff, and are staring at a deadline. Their three real jobs are: (1) chase and structure supplier plot data (the coordinates/polygons arrive as WhatsApp messages, PDFs, KML files, and spreadsheets — if they arrive at all), (2) validate that geometry and check every plot against the 2020 deforestation baseline, and (3) generate a clean DDS and submit it to TRACES per shipment, keeping a 5-year audit trail.

GroveProof does exactly those three, priced for a wallet that tops out around €150/mo. It is not an ESG platform. It’s a deforestation-clearance engine: supplier data in → validated, risk-scored, TRACES-filed DDS out.

4. Target market

• Primary customer: Owner/operator or ops manager at a direct-import specialty coffee roaster, bean-to-bar chocolate maker, or small hardwood/plywood importer in the EU — 3–50 staff, importing directly from origin (not via an EU intermediary), filing roughly 2–40 DDS/month across 5–40 origin suppliers. No dedicated compliance headcount.
• Why they buy (in their words): “I buy green coffee from six cooperatives in Colombia and Ethiopia. Half of them have no idea what a polygon is. If my DDS bounces or my coordinates overlap, my container sits at the port racking up demurrage and I can’t sell the lot. I can’t afford a €12K platform to file eight statements a month.”
• Rough TAM reasoning: Europe has thousands of small independent specialty roasters (the branded specialty coffee shop market alone exceeds 40,000 outlets; independent roasters number in the low thousands), plus bean-to-bar chocolate makers and small timber/plywood importers. Conservatively 8,000–20,000 EU micro/small direct importers across the in-scope commodities. Capture 1,000 at ~€1,200/yr ACV = €1.2M ARR — well inside a bootstrap.
• Why now for them: The deadline is fixed (30 Dec 2026 / 30 Jun 2027) and TRACES filing becomes non-optional; a bounced DDS or a bad polygon literally halts a shipment. This is a “solve it this quarter or lose containers” problem, not a nice-to-have.

5. Product sketch (MVP)

• Supplier data collector: a branded link/portal you send each origin supplier; they drop coordinates, polygons, KML/GeoJSON, or photos of a hand-drawn map, and GroveProof structures it into a clean plot record. AI parses messy PDFs and free-text into geometry.
• Polygon doctor: auto-detects the >10% of polygons that self-intersect, overlap, or sit off-farm; flags and offers one-click geometry fixes before anything reaches TRACES.
• Deforestation check: overlays each plot against the EU JRC GFC2020 baseline + Global Forest Watch alerts and returns a plain-English pass/fail with the supporting imagery reference, per plot.
• Risk assessment generator: produces the country/commodity risk write-up EUDR requires, pre-filled from origin and cross-checked against the plot results.
• DDS builder + TRACES filer: assembles the shipment DDS and submits it to TRACES NT via the official API, returning the reference number — no manual re-keying into the SOAP portal.
• 5-year audit vault: every DDS, plot, image, and supplier document stored and export-ready for an inspector.
• Deadline & shipment tracker: a simple board of which shipments are cleared, which are missing supplier data, and which are blocked — so nothing sails without a filed DDS.

6. AI angle — what’s load-bearing

Two places AI does real work, not decoration:

1. Turning origin chaos into structured geometry. Supplier data arrives as WhatsApp screenshots, scanned cooperative registries, KML dumps, and Portuguese/Spanish/Amharic PDFs. An LLM + OCR + geo-extraction pipeline converts that into validated plot polygons with the right CRS. Remove the AI and this reverts to a human manually re-typing coordinates — exactly the error-prone step that produces the 10% bad-polygon rate.
2. Explaining the verdict. Mapping a raw satellite/baseline overlay into “Plot 3 shows 0.4 ha of tree-cover loss in 2022 — this plot fails; here’s the tile” is the difference between a tool a non-expert roaster can act on and a GIS product they can’t. The deforestation math is deterministic geospatial; the AI makes it legible and drafts the risk narrative.

If you strip the AI, you’re left with a TRACES form and a GIS console the customer already can’t use. The AI is the “small operator can self-serve” wedge.

7. Localization angle (if any)

EU-native by construction: the regulation, TRACES, and the JRC baseline are EU artifacts. The localization that matters is origin-side, multilingual supplier onboarding — the collector portal and doc parser must handle Spanish, Portuguese, French, Amharic, Vietnamese and Bahasa so a Colombian or Ethiopian cooperative can respond without friction. That multilingual origin-facing layer is itself a moat: the incumbents’ enterprise UIs assume a European compliance analyst, not a smallholder cooperative clerk on a phone.

8. Business model — path to $1M–$5M ARR

• Pricing: €39/mo Starter (up to ~5 DDS/mo, 10 suppliers), €99/mo Growth (up to ~30 DDS/mo, satellite checks, TRACES filing), €149/mo Pro (unlimited DDS, multi-commodity, priority polygon fixes). Optional per-plot satellite-verification credit pack for spiky seasons.
• ACV: ~€1,000–1,400 blended (most land on Growth).
• Rough math to $1M ARR: ~750 customers × €110/mo × 12 ≈ €1.0M. Entirely reachable within the EU small-importer base.
• Rough math to $5M ARR: ~3,000 customers, or blend in a €300–500/mo “co-op/importer group” tier that files on behalf of 10–30 downstream roasters, plus expansion into rubber/timber importers and non-coffee commodities. Requires becoming the default filing tool in 2–3 commodity communities.
• Expansion path: ACV grows with DDS volume (usage), commodities added (coffee → cocoa → timber → rubber), and a “verified supplier network” data layer sold back as faster onboarding.

9. Go-to-market wedge — first 100 customers

• Scrape the roaster/importer directories. The EU specialty scene is heavily catalogued — national roaster guilds, the Specialty Coffee Association member lists, European Coffee Trip’s roaster directory, bean-to-bar maker lists. Assemble ~2,000 direct-import roasters/makers, send a personalized 90-second Loom: “here’s your Colombia supplier’s plot checked against the 2020 baseline in 3 minutes.” Expect 3–5% reply.
• Ride the panic content. SCA, CBI, and every EUDR consultant are publishing “you’re not ready” pieces. Publish a free “Is your polygon EUDR-valid?” checker (upload a KML, get an instant overlap/deforestation verdict) as the top-of-funnel; it demos the hardest feature in one click and captures the exact buyers actively searching.
• Partner with green-coffee importers and brokers. The mid-chain importers (Trabocca-type) want their roaster customers compliant so lots keep moving; co-market GroveProof as the roaster-side filing tool. One importer relationship = a warm list of dozens of downstream roasters.
• Consultant channel. EUDR consultants charging day-rates want a tool to operationalize their advice for small clients; offer a referral/reseller cut.
• Trade shows & roaster forums. World of Coffee, national roaster meetups, and r/roasting / specialty Discords where the “how do I even do EUDR” threads are live right now.

10. Build complexity — justification

Medium. Off-the-shelf: LLM/OCR for doc parsing, standard web stack, the free JRC GFC2020 + GFW Data API for the deforestation baseline, and a public (if ugly SOAP v2) TRACES NT API for submission. The custom work is the geospatial validation layer (polygon geometry repair, CRS handling, baseline overlay) and a robust multilingual supplier-collection flow — real engineering, but no research breakthrough and no proprietary dataset needed. A 1–3 person team ships a credible v1 in ~4–5 months, with the polygon checker demoable in weeks.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	Helping operators comply with EUDR; nothing adversarial to the regulator.
Ethical — no harm / dark patterns	✅	Furthers a deforestation-prevention law; pro-transparency.
Market exists (evidence above)	✅	Hard deadline, quantified unpreparedness, funded incumbents, priced-out SME segment.
1–5 person team can build this	✅	Medium build on off-the-shelf APIs + a geospatial layer.
Launchable with <$50K / ₹40L	✅	Solo/pair + cheap satellite/data APIs; no capex.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	17/20	Hair-on-fire: a bounced DDS or bad polygon halts a shipment and racks demurrage; €72K-loss precedent. Repeats per shipment.
Demand evidence	15	12/15	Multiple independent signals — 73%/89% unprepared stats, storage-loss anecdote, 10% bad-polygon rate, funded incumbents, an explicit priced-out segment. Not yet direct verbatim SME buying quotes, hence not 14.
Build feasibility	15	10/15	Doable in ~4–5 months but the SOAP TRACES integration + geospatial validation are non-trivial; not a 6-week solo build.
Distribution clarity	15	12/15	Named directories, named importer/consultant channels, a viral polygon-checker hook. Conversion still to prove.
Revenue mechanics	15	11/15	Pricing benchmarked (€29–79 low end exists, €12K enterprise ceiling); €1M path needs ~750 paying SMEs — achievable but requires real acquisition volume.
Time to first revenue	10	7/10	Panic-buying window is open now; free checker → paid conversion plausibly 4–8 weeks. Gated slightly by TRACES relaunch (June 2026) and buyers who procrastinate to Q4.
Defensibility	10	7/10	Soft moat: multilingual origin-supplier network data, accumulated validated-plot library, and workflow lock-in as the filing system of record. Copyable, but a head start in 2–3 commodity communities compounds.
Total	100	76/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (geospatial + SOAP integration + LLM parsing) · domain-expertise-required (EUDR mechanics, DDS/TRACES specifics — bring or acquire a compliance advisor).

Key assumptions to validate (3–5)

1. Assumption: Small direct importers will pay €40–150/mo rather than muddle through TRACES manually or lean on a broker. How to test: 30 discovery calls with direct-import roasters/makers; pre-sell 10 Growth seats before building the filer.
2. Assumption: The TRACES NT API supports programmatic per-shipment DDS submission reliably for third-party operators (not just ERP giants). How to test: Build against the CIRCABC SOAP v2 spec in the June-2026 relaunch sandbox and file a test DDS end-to-end.
3. Assumption: The free polygon-checker converts to paid at a usable rate. How to test: Ship the standalone checker first; measure email capture → trial → paid over 4 weeks.
4. Assumption: Origin suppliers will actually respond through a collector portal in their language. How to test: Run the onboarding flow with 5 real cooperatives across 3 origins; measure completion rate.

Risk flags

1. Regulatory risk: EUDR has already been delayed twice and simplified (postal codes vs precise geo for some SMEs; one-off simplified declarations for micro primary operators). Another delay softens urgency; a simplification could shrink the hard part. Mitigate by keeping the product commodity-agnostic and useful even under the lighter SME regime.
2. Platform dependency: Total reliance on the TRACES NT API and the JRC/GFW baseline data. If TRACES ships a good free bulk-filing UX, the “filing” value thins — but the supplier-collection + polygon-validation value survives.
3. Incumbent land-grab: osapiens/TraceX could launch a self-serve €49/mo tier and swallow the low end. Speed into 2–3 commodity communities and own the multilingual origin-onboarding layer before they bother.
4. Market timing: Buyers procrastinate to the last month; revenue may bunch in Q4 2026 and Q2 2027 rather than flowing evenly.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder (geospatial + API integration) with an EUDR/compliance advisor
Time to revenue:        6–10 weeks (free polygon-checker → paid), gated by TRACES relaunch sandbox access
Capital to launch:      $8–15K (satellite/data APIs mostly free; time + design)
Top 3 assumptions to validate first:
  1. Small direct importers pay €40–150/mo — 30 discovery calls + pre-sell 10 seats
  2. TRACES NT API allows reliable third-party per-shipment DDS filing — build + file a test DDS in the June-2026 sandbox
  3. Free polygon-checker converts to paid — ship it standalone, measure trial→paid over 4 weeks
Kill criteria:
  - Abandon if <5 of 30 discovery calls will pre-commit to a paid seat
  - Abandon if the TRACES API cannot be programmatically filed against by a small third-party operator
  - Abandon if a well-funded incumbent ships a self-serve sub-€60/mo direct-importer tier with geolocation + TRACES filing before your v1

15. Next step — 1-week validation sprint

• Day 1–2: Build the assumptions list into a scrappy landing page + the free “Is your polygon EUDR-valid?” checker (KML upload → overlap + 2020-baseline verdict). This is the sharpest, cheapest demo of the hardest feature.
• Day 3–4: Pull a list of ~300 EU direct-import specialty roasters/chocolate makers from public directories; send 60 personalized outreach messages offering a free plot-check + a 15-minute call.
• Day 5: Decide go/no-go on a falsifiable bar: ≥8 booked discovery calls and ≥3 verbal pre-commitments to a paid seat from the 60 outreaches, AND a successful end-to-end plot-check demo on at least 2 real supplier polygons. Miss the bar → the pain isn’t urgent enough to pay for yet; revisit closer to the deadline.