Bob Vanderoulen

Why this dossier matters for NOTQIN

Bob is the closest analog in the world to what the future NOTQIN Agent is trying to be — UNS + Knowledge Graph + Claude / MCP, delivered as an Ignition module to industrial customers. Either he is our best partner (reseller / tech-partnership / cross-pollination) or our clearest competitive benchmark. Cannot know which without proper intelligence + a conversation. Email on file but never sent. High-priority disambiguation.

What we already know (don’t re-research)

  • Co-founder of ThreadCloud (New Zealand)
  • Co-founder named Hamish (last name unconfirmed in our memory)
  • Product: Ignition module + cloud knowledge graph + Claude/MCP integration
  • Pricing claim: ~$800/mo per factory (per MEMORY.md project_threadcloud_knowledge_graphs)
  • Public position: “UNS = 2D-for-humans, KG = 3D-for-agents” — quotable framing
  • Operating rule: “measure at control, relate at KG, reason at LLM”
  • Direct email: bob@threadcloud.com
  • Existing vault context: ThreadCloud — Vendor Intelligence 2026

📋 Deep Research Prompt — paste into Gemini Deep Research OR ChatGPT Deep Research

Today’s date is 2026-05-24. Copy everything between the --- markers below.


You are a senior research analyst producing a strategic intelligence dossier on Bob Vanderoulen, co-founder of ThreadCloud (a New Zealand based industrial knowledge-graph + agentic-AI startup), for a small Moroccan industrial-intelligence startup called NOTQIN. NOTQIN is building a comparable decision layer for Moroccan industrial customers and needs to understand whether ThreadCloud is a partner, a competitor, or both.

What I already know (do NOT re-research):

  • Bob is a co-founder of ThreadCloud, based in New Zealand
  • Co-founder named Hamish (full name uncertain — I need you to verify)
  • Product: an Ignition module + cloud knowledge graph + Claude / MCP integration
  • Approximate pricing: ~$800/month per factory (this number may be outdated — verify)
  • Public framing he uses: “UNS is 2D for humans; KG is 3D for agents” and “measure at control, relate at KG, reason at LLM”
  • Direct contact email: bob@threadcloud.com

What I need from you — a structured dossier covering ALL of the following, in this exact order. Use markdown headers. Cite every claim with a source URL.

1. Identity & founder background

  • Verified full name, current title(s), location (NZ city if public)
  • LinkedIn URL, X/Twitter, personal site
  • Prior career — companies he founded, worked at, exited; especially any pre-ThreadCloud industrial / OT / data background
  • Hamish co-founder: full name + LinkedIn + background
  • Any other ThreadCloud team members publicly identified (engineers, advisors)

2. ThreadCloud — the company

  • Founding year, registered entity, HQ
  • Funding history: any disclosed rounds, investors, amounts, dates
  • Team size (LinkedIn employee count)
  • Office/region focus
  • Any board members or advisors

3. ThreadCloud — the product

  • Architecture: confirm the Ignition module + KG + Claude/MCP stack with technical details
  • What problem does it actually solve at the customer site? (specific use cases, not marketing)
  • Deployment model — self-hosted / cloud-hosted / hybrid? Where does customer data live?
  • Pricing — verify or correct the $800/month per factory figure. Tier structure? Per-seat? Per-data-volume?
  • Integration points beyond Ignition (does it work with other SCADAs?)
  • Open-source vs proprietary components
  • Security posture — any public claims about cert, compliance, soc2, etc.

4. Customer base

  • Any named customers (logos on site, case studies, press releases, podcast mentions)
  • Industry verticals they serve
  • Geographic concentration (NZ + AU + EU + US?)
  • Any Morocco / Africa / MENA / Francophone-market presence or interest, ever
  • Approximate customer count if disclosed

5. Public positioning & content

  • ThreadCloud blog / content output — frequency, topics, key posts in 2024–2026
  • Bob’s personal content: LinkedIn posts (last 6 months), podcast appearances, conference talks
  • Bob’s key public framings, quoted verbatim (the “UNS=2D, KG=3D” quote is one example)
  • His position on competitors / alternatives (e.g., HighByte, Litmus, MaestroHub, plain UNS-only stacks)

6. Partnership posture — the central question for NOTQIN

  • Does ThreadCloud have a partner program (resellers, system integrators, regional partners)? Public terms?
  • Does ThreadCloud have a technology partner program (other product companies that integrate)?
  • Has Bob publicly discussed openness to partnerships in MENA / Africa / emerging markets?
  • Any history of partnering with smaller / earlier-stage companies?
  • Pattern in how ThreadCloud picks design partners or early customers

7. Network — amplification map

  • Top 10 people in the industrial-AI / UNS / KG community Bob most engages with publicly
  • Companies and people who amplify ThreadCloud’s content
  • Any tension with adjacent companies (HighByte, MaestroHub, Inductive Automation direct competitors)
  • Connection to Walker Reynolds, Arlen Nipper, Travis Cox, the broader UNS community

8. Recent activity (last 6 months from today’s date, 2026-05-24)

  • His last 10 LinkedIn posts (date + 1-line + engagement)
  • His last 5 podcast appearances or talks
  • ThreadCloud product / pricing / funding announcements in the window
  • Any pivot, controversy, or material change in narrative

9. Strategic read for NOTQIN

  • Partner or compete? Honest assessment given NOTQIN’s stage (pre-paying-customer, 5-person Moroccan team) and ThreadCloud’s stage
  • If partner: what concrete first conversation should NOTQIN propose to Bob? (Single specific ask, not “let’s chat”)
  • If compete: where is ThreadCloud’s blind spot that NOTQIN can wedge into?
  • The 1-line outreach Bob would actually reply to (vs the 100 fan emails he gets)
  • Best non-Bob entry point — anyone in his orbit who could warm-intro

10. Sources used

  • Complete URL list, grouped by category

Constraints:

  • DO NOT include marketing puff or vendor-supplied bios
  • DO NOT speculate beyond what sources support — mark uncertainty as [uncertain: source weak]
  • DO NOT skip §4 geography just because there may be no Morocco/MENA presence — say so explicitly if true
  • Treat anything from the ThreadCloud sales site with mild skepticism — find independent corroboration where possible (customer LinkedIn posts, podcast verbatim, third-party coverage)

Output as a single markdown document. Target length: 2500–4000 words plus source list.


📥 Paste research results here

1. Identity & founder background

(pending research)

2. ThreadCloud — the company

(pending research)

3. ThreadCloud — the product

(pending research)

4. Customer base

(pending research)

5. Public positioning & content

(pending research)

6. Partnership posture

(pending research)

7. Network — amplification map

(pending research)

8. Recent activity (last 6 months)

(pending research)

9. Strategic read for NOTQIN

(pending research)

10. Sources used

(pending research)


What to do once filled

  1. Update status: frontmatter from stub-pending-research to populated-v1 + today’s date
  2. Update People Map §7 row — change status icon
  3. Update MEMORY.md project_threadcloud_knowledge_graphs entry with corrections
  4. Update ThreadCloud — Vendor Intelligence 2026 with the new partnership-posture intelligence
  5. Decision gate: based on §9, write the partner-or-compete decision into Decision Log
  6. If partner posture is real → draft outreach email per §9 single-ask. Add to Imrane’s WS-D outreach review.
  7. Re-run prompt every 6 months (ThreadCloud is a moving target — funding rounds and pricing change)

See also

  • People Map §7 (industry thought leaders), §9 (vendors / partners)
  • ThreadCloud — Vendor Intelligence 2026
  • ThreadCloud + Knowledge Graphs (memory: project_threadcloud_knowledge_graphs)
  • Knowledge Graphs
  • MCP
  • Walker Reynolds · Travis Cox — sibling thought-leader dossiers
  • NOTQIN Agent — the future NOTQIN module that’s most analogous to ThreadCloud’s offering
  • Smartex Deep Research Playbook — research methodology