Snowflake Software / SaaS California, USA, Israel

Tipalti

Enterprise Knowledge Search · Sales Automation

Tipalti needed a secure way to give internal teams timely, consistent AI-backed business insights without moving data into external inference services or depending on specialist prompt engineers.

$75 billion in payments managed yearly
5x more queries run simultaneously
more than 600 ad-hoc analyses
more than ten new features have been deployed to over 50 users

Reported impact

Business outcome

Tipalti democratized internal insight generation, shipped more than ten new AI features to over 50 users, enabled more than 600 ad hoc analyses, and avoided building separate external AI infrastructure while supporting a $75 billion payments business.

  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

Tipalti built an internal AI prompt store on Snowflake so sales and marketing teams can explore enterprise data through reusable, governed LLM workflows. Because its warehouse already runs on Snowflake on AWS, the team kept data in place and layered Cortex AI directly into the platform instead of introducing separate inference infrastructure. Predefined business questions are executed through AI_COMPLETE and TRY_COMPLETE, which return structured results inside SQL workflows and isolate single-row failures. Tipalti also used Snowpark to build a custom parallelization function so multiple prompt executions can run simultaneously and deliver faster answers. Outputs surface in tools such as Salesforce, giving nontechnical users consistent insights without manual prompt engineering or data wrangling. The design reduces overhead today and leaves Tipalti ready for future semantic-model, search, and RAG capabilities on the same governed data foundation.

Data flow

Internal business and finance data remains in Snowflake on AWS, where predefined prompts call Cortex AI through AI_COMPLETE and TRY_COMPLETE. Snowpark parallelizes execution, and structured answers are surfaced in Salesforce and other daily tools for sales and marketing teams.

Solution architecture

5 components · 3 layers
  1. Compute
    • Cortex AI Provides in-platform LLM capabilities for prompt execution and structured insight generation.
    • AI_COMPLETE Embeds LLM calls directly into SQL workflows so prompts can return structured business answers without extra infrastructure.
    • Snowpark Runs the custom parallelization logic that increases prompt throughput and responsiveness for business users.
  2. Storage
    • Snowflake Hosts Tipalti's governed data warehouse and serves as the platform where AI insight workflows run.
  3. Orchestration
    • TRY_COMPLETE Prevents single prompt failures from breaking whole batch workflows, improving reliability at scale.

Architecture clues

  • Future plans include semantic models, Cortex Search, and RAG with embeddings on the same foundation.
  • Prompt execution stays inside Snowflake instead of relying on external inference services.
  • The AI prompt store centralizes reusable prompt patterns for internal teams.

Evidence from the source

AI_COMPLETE integrates LLM capabilities from Cortex directly into SQL workflows
TRY_COMPLETE ensures that any single failure won't cause an entire batch process to fail
The solution enables Tipalti to integrate AI insights into the platforms its teams use every day, such as Salesforce
built an AI-prompt store on Cortex AI
multiple queries can run in parallel
Transparency Evidence & methodology 86/100 reference value · 82% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value86/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Snowflake

    Tipalti customer story

    First-party
    https://www.snowflake.com/en/customers/all-customers/case-study/tipalti/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
  2. LinkedIn

    Tipalti | LinkedIn

    Independent secondary
    https://www.linkedin.com/company/tipalti/

    LinkedIn's Organization JSON-LD lists addressLocality "Foster City", addressCountry "US", and numberOfEmployees value 1084.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • First archived Mar 19, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Jul 7, 2026 · Snowflake · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.