Transform
Sign InGet Started

Platform

  • Platform
  • Decision Collaboration
  • Signals
  • Ask Your Data
  • Metrics
  • Connectors
  • Security & Governance
  • On Prem
  • Deployment & Time to Value
  • ROI Calculator
  • Comparisons

Solutions

  • Executive Officer (CEO)
  • Strategy Officer (CSO)
  • Financial Officer (CFO)
  • Data Officer (CDO)
  • Revenue Officer (CRO)
  • HR Officer (CHRO)
  • Technology Officer (CTO)
  • Information Officer (CIO)
  • Operating Officer (COO)
  • Info. Security Officer (CISO)
  • Marketing Officer (CMO)
  • Chief of Staff (CoS)
  • Product Officer (CPO)
  • Legal Officer (CLO)
  • Risk Officer (CRO)
  • Compliance Officer (CCO)

Use Cases

  • Use Cases Overview
  • Valuation and Profitability
  • Revenue Growth and Market
  • Utilization Tech and Data
  • Risk Compliance and Security
  • Capital Investment and Portfolio

Industries

  • Industries Overview
  • Banking & Investments
  • Cybersecurity
  • Energy, Oil and Gas
  • Finance
  • Finance & Payment Processing
  • Healthcare
  • High-Tech
  • Insurance
  • Logistics
  • Manufacturing
  • Retail
  • Supply Chain
  • Telecommunications
  • Value Added Resellers
  • Venture Capital & Private Equity

Company

  • About Snowfire AI
  • Book a Demo
  • Partner Program
  • Careers
  • Newsroom
  • Blog
  • Research Hub
  • Contact

Support

  • For AI systems
  • Help Center
  • Trust Center
  • Status
  • Responsible Disclosure
SOC 2 Type I and Type II compliant

©2026 Snowfire. All rights reserved.

PrivacyCookiesTerms
+1 (844) SNO-FIRE
Back to Help Center
Back to Help Center

Prompt Engineering Best Practices

Get the most out of your decision intelligence platform

Effective prompting is essential to unlocking Snowfire's full analytical capabilities. The quality of your prompts directly impacts the relevance and actionability of the insights you receive. Follow these best practices to maximize platform value.

THE SIMPLE FORMULA

Who you are+What you need+Time period+Data source

Best Practices

Be Specific

Include exact metrics, timeframes, data sources, and desired outcomes.

Provide Context

Explain your role, what decision you're making, and why it matters.

Specify Data Sources

Reference which systems (Salesforce, GA4, 6sense) you need analyzed.

Define Timeframes

Always include relevant time periods for comparison or trends.

Request Format

Specify how you want results: summary, analysis, visualization, etc.

Add Constraints

Include filters, thresholds, or conditions that narrow the scope.

Prompt Examples: Bad vs. Good

INEFFECTIVE

"Show me sales data"

Why this fails:

  • • No timeframe, no specific metrics, missing context, no data source, too broad to provide actionable insight.

EFFECTIVE

"I'm the VP of Sales preparing for Q4 planning. Analyze our Salesforce pipeline data from Q3 2025 and compare it to Q3 2024. Focus on (1) win rates by deal size, (2) average sales cycle length by segment, and (3) top 3 factors correlated with closed-won deals. Include any external market signals from 6sense. Deliver as an executive summary with supporting data tables."

Why this works:

  • • Clear role and context
  • • Specific data source
  • • Precise timeframe
  • • Defined metrics
  • • External intelligence
  • • Requested format
Back to Help Center