--- title: "Sales" description: "How sales works at Langfuse when the product is meant to sell itself: where the team gets involved, and what it owns." --- # Sales Our company strategy is for our product to sell itself. Many of our customers can just come in and buy without speaking to us. For other customers, it is, however, imperative to have a counterpart in our sales team to adopt Langfuse successfully. We like to think that the decision of both user groups is primarily based on how we [build & market](/handbook) our product and that sales removes friction for any organization to onboard to Langfuse. Sales at Langfuse is one team with ProductEng and Customer Success. Sales owns the decision to onboard; CS owns long-term value; Product/Eng owns roadmap. Everyone shares the customer outcome. ## Principles - Sales helps customers adopt Langfuse and navigate friction. - We build processes to navigate common corporate challenges in learning about, procuring, and onboarding to Langfuse - We default to inbound, product-led and sales-assisted motions - We don't force calls; we are lightning-fast and technically credible when users want help - We experiment with outbound to product-qualified leads (PQLs), but we avoid broad cold outbound - We don’t contract deliverables for individual customers. We are a small and fast-moving team. This only works if we work 1:n as much as possible. - We walk away from deals that will add distraction to our organization. ## Processes ### Who do we work with & what do we sell? #### Segments - **Self-Serve / No Touch**: 0-10k ACV: support only, no sales involvement, no custom legal effort - Public Pricing → langfuse.com/pricing, month-to-month - Entirely self-serve – terms, DPA, security center, reports, etc. - Plans: Langfuse Hobby, Core, Pro - **Sales-Assisted / Low-Touch**: 10-50k ACV: sales owns relationship pre/post-signing, we can help based on established processes (e.g., minor edits to terms, DPA, pre-approved discount schedules, workshops, priority support through flags, etc.) - Suss out details (e.g., two accounts, one in each data region, sign additional NDA, answer questions about security) - Get on a call with prospect - Plans: Langfuse Teams (USD 500/month base fee \+ usage) & Enterprise: starting at \~3k/month spend commit, 12 months commit - **Sales-Led / High-Touch**: 50k+ ACV: Enterprise - Custom (e.g., custom legal terms, custom pricing, SLAs, we can do custom legal contracts) - Security Questionnaires (we commit to publishing reasonable items on our security center to be used in pro/teams) but Excel sheets, etc. only on enterprise - Edits to Langfuse Terms, DPA, BAA - Procurement tools (Coupa, Ariba, etc.) - Plans: Enterprise (50k+) #### What do we sell? - Our product & our [public roadmap](/roadmap) - See "[How do we make money](/handbook/chapters/monetization)" chapter of the handbook #### What don’t we sell? - Self-hosting - Licenses - Product support - Deployment support - Consulting - Solutions engineering - One-off product deliverables - We don’t participate in RFPs #### Excursus on self-hosting - We don’t have a self-hosted commercial offering - We would love for companies to use Langfuse. We want to build community & a funnel for cloud leads down the road. For this we commit to: - Make EE version available for them through a simple process - Make self-hosting Langfuse possible & as easy as possible - Provide [support](/support) through public forums ### How do we work with customers? #### We prioritize inbound - "Hand raisers" (PQLs), "Talk to Us", enterprise inbound, community/socials - Qualification - Leads qualified in HubSpot - Two weekly reviews (focus on active deals & focus on stale deals) #### Security & Legal - Make security reviews as self-servable as possible - Publicly available Security Center ([langfuse.com/security](/security)): SOC 2, ISO 27001, pen test, DPA, terms #### Handover to CS & Billing - Within 24h of close/upgrade - Intro: 3-way email + Slack, schedule kickoff, transfer open actions - Billing handover to Felix after contract closed/signed via #billing-invoicing Slack channel #### Other Processes ##### Discounting - For now, stay close to the spirit of: [https://posthog.com/handbook/growth/sales/contract-rules](https://posthog.com/handbook/growth/sales/contract-rules) - We operate a startup & research program: [langfuse.com/startups](/startups) + [langfuse.com/research](/research) - Additionally, we operate a deal for YC companies (10k Langfuse credits for the first year towards any plan - both current batch & alumni) --- ## Agent Instructions This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/handbook/sales-and-cs/sales.md`. ### Querying these docs If the answer is not on this page, query the documentation instead of guessing: - **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question: ```bash curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?" ``` - **Index of every page**: , with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt). ### Before writing Langfuse code - **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results. - **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application. - **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples. - **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .