Welcome to FlowZap dear Business Process Maniacs!

Explorer les demandes courantes de cartographie de workflows aux principaux LLMs : insights pour l’optimisation business

31/08/2025

Tags: LLMs, workflow, cartographie des processus, FlowZap

Jules Kovac

Jules Kovac

Business Analyst, Founder

Explorer les demandes courantes de cartographie de workflows aux principaux LLMs : insights pour l’optimisation business

En tant que CEO de Flowzap.xyz, je cherche en permanence des moyens d’aider les entreprises à rationaliser leurs opérations et à stimuler la croissance. Un angle intéressant consiste à analyser comment les utilisateurs sollicitent les grands modèles de langage (LLMs) pour cartographier workflows et processus. En observant les requêtes faites à Claude, DeepSeek, ChatGPT, QWEN, Gemini et Z.ai, on identifie des schémas récurrents et des zones de friction, et on voit comment Flowzap.xyz les convertit en cartes visuelles exploitables qui améliorent l’efficacité et l’engagement.

Principales demandes par LLM

Bien que les classements varient, des thèmes communs se dégagent : l’onboarding client, la gestion du pipeline de vente, l’onboarding/recrutement RH, l’approbation de contenu et l’escalade support/incident.

Top requêtes de Claude

  1. Onboarding client
  2. Recrutement
  3. Cycle de développement produit
  4. Escalade support client
  5. Pipeline de vente
  6. Facturation/paiement
  7. Approbation de projet
  8. Réponse à incident
  9. Migration de données
  10. Assurance qualité

Top requêtes de DeepSeek

  1. SDLC / CI‑CD
  2. Onboarding client
  3. Lead‑to‑Cash / pipeline de vente
  4. Support & ticketing
  5. Création & approbation de contenu
  6. Traitement de données / ETL
  7. Réponse et résolution d’incident IT
  8. Onboarding employé
  9. Achats & gestion fournisseurs
  10. Social media management

Thèmes communs et implications

  • Onboarding client : réduit le churn et accélère les revenus.
  • Pipeline de vente : convertit les leads.
  • Onboarding/Recrutement : essentiel pour l’échelle.
  • Création & approbation de contenu : traction marketing.
  • Support & incidents : satisfaction et fidélisation.

Flowzap.xyz transforme ces demandes en diagrammes interactifs collaboratifs, pour passer des idées à l’exécution.

FlowZap Code pour l’onboarding client (exemples)

1) Code et diagramme générés par Claude Opus

sales { # sales
n1: circle label="Lead Qualified"
n2: rectangle label="Initial Contact"
n3: rectangle label="Discovery Call"
n4: diamond label="Good Fit?"
n5: rectangle label="Prepare Proposal"
n6: rectangle label="Present Proposal"
n7: diamond label="Accepted?"
n8: rectangle label="Send Contract"
n9: circle label="Deal Lost"
n1.handle(right) -> n2.handle(left)
n2.handle(right) -> n3.handle(left)
n3.handle(right) -> n4.handle(left)
n4.handle(right) -> n5.handle(left) [label="Yes"]
n5.handle(right) -> n6.handle(left)
n6.handle(right) -> n7.handle(left)
n7.handle(right) -> n8.handle(left) [label="Yes"]
n8.handle(bottom) -> legal.n10.handle(top) [label="Review"]
n7.handle(top) -> n9.handle(top) [label="No"]
n4.handle(top) -> n9.handle(top) [label="No"]
}

legal { # legal
n10: rectangle label="Contract Review"
n11: diamond label="Terms OK?"
n12: rectangle label="Request Changes"
n13: rectangle label="Finalize Contract"
n14: rectangle label="Contract Signed"
n10.handle(right) -> n11.handle(left)
n12.handle(top) -> sales.n6.handle(bottom) [label="Negotiate"]
n13.handle(right) -> n14.handle(left)
n14.handle(bottom) -> finance.n15.handle(top) [label="Process"]
n11.handle(bottom) -> n13.handle(bottom) [label="Yes"]
n11.handle(right) -> n12.handle(left) [label="No"]
}

finance { # finance
n15: rectangle label="Setup Billing"
n16: rectangle label="Process Payment"
n17: diamond label="Payment OK?"
n18: rectangle label="Payment Issue"
n19: rectangle label="Account Active"
n15.handle(right) -> n16.handle(left)
n16.handle(right) -> n17.handle(left)
n19.handle(bottom) -> operations.n20.handle(top) [label="Activate"]
n17.handle(top) -> n19.handle(top) [label="Yes"]
n18.handle(bottom) -> n16.handle(bottom) [label="Retry"]
n17.handle(right) -> n18.handle(left) [label="No"]
}

operations { # operations
n20: rectangle label="Create Account"
n21: rectangle label="Setup Environment"
n22: rectangle label="Configure Settings"
n23: rectangle label="Assign Team"
n24: rectangle label="Schedule Training"
n20.handle(right) -> n21.handle(left)
n21.handle(right) -> n22.handle(left)
n22.handle(right) -> n23.handle(left)
n23.handle(right) -> n24.handle(left)
n24.handle(bottom) -> customersuccess.n25.handle(top) [label="Handoff"]
}

customersuccess { # customersuccess
n25: rectangle label="Welcome Call"
n26: rectangle label="Product Training"
n27: rectangle label="Implementation Support"
n28: diamond label="Ready to Launch?"
n29: rectangle label="Additional Training"
n30: rectangle label="Go Live"
n31: rectangle label="30-Day Check-in"
n32: circle label="Onboarding Complete"
n25.handle(right) -> n26.handle(left)
n26.handle(right) -> n27.handle(left)
n27.handle(right) -> n28.handle(left)
n28.handle(right) -> n30.handle(left) [label="Yes"]
n30.handle(right) -> n31.handle(left)
n31.handle(right) -> n32.handle(left)
n28.handle(top) -> n29.handle(top) [label="No"]
n29.handle(bottom) -> n27.handle(bottom) [label="Continue"]
}

Claude Opus Customer Onboarding

2) Code et diagramme générés par DeepSeek

sales { # Sales Team
n1: circle label="Start"
n2: rectangle label="Send Welcome Email & Contract"
n3: rectangle label="Receive Signed Contract"
n4: rectangle label="Create Internal Ticket"
n5: circle label="Handoff"
n1.handle(right) -> n2.handle(left)
n2.handle(right) -> n3.handle(left)
n3.handle(right) -> n4.handle(left)
n4.handle(right) -> n5.handle(left)
n5.handle(bottom) -> onboarding.n6.handle(top) [label="Ticket Created"]
}

onboarding { # Onboarding Specialist
n6: rectangle label="Review Client Info & Goals"
n7: rectangle label="Schedule Kickoff Call"
n8: rectangle label="Conduct Kickoff Meeting"
n9: rectangle label="Configure Account"
n10: rectangle label="Prepare Training Materials"
n11: rectangle label="Grant System Access"
n12: circle label="Complete"
n6.handle(right) -> n7.handle(left)
n7.handle(right) -> n8.handle(left)
n8.handle(right) -> n9.handle(left)
n9.handle(right) -> n10.handle(left)
n10.handle(right) -> n11.handle(left)
n11.handle(right) -> n12.handle(left)
n7.handle(bottom) -> customer.n13.handle(top) [label="Sends Invite"]
n8.handle(bottom) -> customer.n14.handle(top) [label="Holds Meeting"]
n11.handle(bottom) -> customer.n15.handle(top) [label="Sends Credentials"]
}

customer { # Customer
n13: rectangle label="Receive Meeting Invite"
n14: rectangle label="Attend Kickoff Meeting"
n15: rectangle label="Receive Login & Materials"
n16: diamond label="First Login Successful?"
n17: rectangle label="Complete Setup Tasks"
n18: rectangle label="Confirm Go-Live"
n19: circle label="Onboarded!"
n13.handle(right) -> n14.handle(left)
n14.handle(right) -> n15.handle(left)
n15.handle(right) -> n16.handle(left)
n16.handle(right) -> n17.handle(left) [label="Yes"]
n17.handle(right) -> n18.handle(left)
n18.handle(right) -> n19.handle(left)
n16.handle(top) -> onboarding.n11.handle(bottom) [label="No - Needs help"]
n18.handle(top) -> onboarding.n12.handle(bottom) [label="Notify Success"]
}

DeepSeek Customer Onboarding

What do you think your favorite LLM will generate as your FlowZap Code ? I’ll give you a hint: Copilot sucks.

Retour à tous les articles du blogue