Zeer
Zadig et Voltaire North AmericaZadig et Voltaire North America buying intent
5 tracked signals — top 4 topics below — Engineering is carrying most of it.
Attention by team
taxonomy_intent_rollup × social_profile.roleEvery tracked signal from a Zadig et Voltaire North America employee, placed by the team they sit in and the theme they engaged with. Darker means more concentrated attention.
Topics being researched
30-day windowAll tracked topics, ranked by signal volume. Confidence is the classifier's certainty that the signal belongs to this topic.
23d ago
23d ago
23d ago
23d ago
Need intent for a specific topic or industry?
We track the full taxonomy across every account in the graph — including themes not shown on this page.
Who to contact at Zadig et Voltaire North America
verified title on filePeople at Zadig et Voltaire North America whose own activity produced these signals. Names are withheld pending a consent decision; titles, seniority and topic are real and free to browse.
Top accounts researching Zadig et Voltaire North America
names withheld on the public pageCompanies whose people mention Zadig et Voltaire North America in their own activity. Account names are withheld here; not yet classified as implementation partner vs. genuine prospective buyer.
No buyer signal yet for this account
Nobody in the graph is currently discussing this company by name in a way we can attribute to a specific employer.
Buyer profile
company size · seniorityHow big those accounts are, and who inside them is senior enough to matter. Competitor products still not yet computed for this account.
What's been said
public posts mentioning Zadig et Voltaire North AmericaReal public activity that surfaced Zadig et Voltaire North America in a tracked topic. Not a sentiment score — just what people actually wrote.
I asked an AI to fix a bug. It rewrote three files and introduced two new ones. The code looked reasonable. The tests passed. The original bug was still there. This isn't a capability problem. It's a discipline problem. AI assistants default to doing things immediately — writing code, claiming fixes, expressing confidence — without the structure that makes those actions trustworthy. And it's not just bug fixes. The same pattern breaks requirements gathering, architecture decisions, code reviews, and release handoffs. That's why I built Devflow: a framework of skills and worker agents for Claude Code that enforces disciplined, sequenced workflows across the entire development lifecycle. The core idea: before any work begins, a router selects the right pipeline. Every worker knows its role and its hard limits. Nine pipelines. One for every stage: 0 ▸ Requirements — spec before design 1 ▸ Spike / POC — validate before committing 2 ▸ New API — research before building 3 ▸ Feature — plan → build → test → review 4 ▸ Bug fix — reproduce → test → fix → verify 5 ▸ Refactor — scope → simplify → confirm behavior preserved 6 ▸ Test coverage — fill gaps without touching production 7 ▸ Review — critique without rewriting 8 ▸ Docs — document what shipped, nothing more Each pipeline enforces the right sequence. Requirements before design. Tests before implementation. Evidence before completion claims. A retrospective before closing any investigation. 21 skills. 13 worker agents. Open source. The discipline doesn't come from the AI being smarter. It comes from the structure refusing to let it skip steps — at any stage. Pipeline 4 — Bug Fix