# What is Fluid CRM Fluid has the structure of a CRM with the simplicity of a spreadsheet. If you outgrew Google Sheets but find HubSpot and Pipedrive feel like a second job, Fluid is built for you. *** ### Who Fluid CRM is for Fluid CRM is built for: * B2B founders and solopreneurs * Consultants and freelancers selling services * Small sales and marketing teams * Outbound agencies running multiple conversations in parallel Common to all of them: * A real sales process with deals moving through stages * A need to see the whole pipeline at a glance * Reminders and follow-ups that cannot slip * Zero patience for bloated, slow CRM systems *** ### The problem with traditional CRMs Most CRMs are built to do everything. As a result, they: * Bury your pipeline behind tabs, filters and menus * Require too many clicks for simple actions * Create mental overhead instead of clarity * Force you to learn enterprise features you will never use * Push constant upgrades for basic features like API access This leads to a common outcome. The CRM becomes a second job. Data entry replaces selling. Pipeline visibility disappears behind a wall of configuration. Deals quietly die because you cannot see them. *** ### What Fluid CRM does differently Fluid CRM is intentionally narrow in scope. Instead of trying to be a full business system, it focuses on one thing: giving you a clear visual pipeline that makes selling faster. Key principles behind Fluid: * Visual pipeline over list view * Drag and drop over data entry * Calm UX, dark themes, zero clutter * Spreadsheet simplicity with CRM structure * Unlimited contacts, deals and pipelines on every plan * One flat price, no upgrade traps, no enterprise sales call The goal is not to manage data. The goal is to keep deals moving forward. *** ### How Fluid CRM works at a high level * You track deals as cards on a kanban-style pipeline * Drag and drop deals between stages as they progress * Each deal stores contact info, company, value, notes and activity history * Set reminders so follow-ups never slip * Forecast revenue based on your actual pipeline, not gut feel * Run automations that handle the busy work in the background * Connect Fluid to your stack through a real REST API on every plan Fluid stays out of your way and supports your daily selling rhythm. *** ### What Fluid CRM is not Fluid CRM is not: * An enterprise CRM with 200 custom fields * A marketing automation suite with email campaigns and drip sequences * A reporting-heavy system designed for sales managers, not sales people * A tool for large hierarchical sales orgs with 50+ reps * A place to store unused features "just in case" It is intentionally simple, fast and focused. *** ### Why Fluid exists Fluid was built out of frustration. After years running B2B outbound at Fenixtal, traditional CRMs felt slow, bulky and mentally draining. Google Sheets broke at 30 deals. HubSpot felt like a second job. Pipedrive capped deals per seat and threatened to delete overflow data after 12 months. Fluid removes the fluff, cuts unnecessary clicks and keeps only what helps you close deals. If Fluid helps you recover even one deal that would otherwise go cold, it is doing its job. *** ### What to read next * Onboarding, how to get set up in 5 minutes * Your daily workflow, how to use Fluid every day * Visual pipeline, how Fluid structures your sales conversations --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fluid-crm.gitbook.io/fluid-crm-docs/getting-started/what-is-fluid-crm.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.