Get AI summaries of any video or article — Sign up free
How To Build A Sales Pipeline From Scratch: Flotion Live Build [Template Linked] thumbnail

How To Build A Sales Pipeline From Scratch: Flotion Live Build [Template Linked]

Landmark Labs·
5 min read

Based on Landmark Labs's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Build the pipeline around connected databases and views: personas, organizations/contacts, pipeline stages, meetings, projects, objectives, feedback, emails/scripts, and actions.

Briefing

A no-code CRM-style workspace in Flotion can be built from scratch to manage every step of a sales pipeline—from buyer research and prospect tracking to meetings, proposals, follow-ups, scripts, and task execution. The core idea is to structure the system around a few key databases and views, then connect them with relations so updates in one place (like a contact’s status) automatically reshape what the team sees elsewhere.

The build starts by setting up workspace pages for the pipeline’s foundational inputs: buyer personas and prospect stages. Personas are created using a user persona template component, with fields for key use cases, pain points, expected actions, needs, plus demographics and psychographics. From there, the pipeline itself is organized around segments that matter to a branding agency—industries like brand identity projects, alcoholic beverages, accounting, tech startups, and e-commerce. Prospects are then grouped by pipeline status, beginning with “Not contacted,” moving through “In conversation,” “Proposal sent,” “Circle back,” “Idle,” and “Active,” with an optional archive for completed projects.

To make the pipeline usable as a CRM, the system adds views that combine organizations and contacts. An “Organizations” view lists companies with industry dropdowns and relationship types, while a contacts view can be filtered to show only prospects in a given stage (for example, only those “Not contacted”). The workflow is designed so teams can drag contacts into the right industry rows and track progress without losing context.

From there, the workspace expands into execution and supporting operations. A “Meetings” section uses meeting components and templates to log calls (including time entries that can surface in a calendar). A “Projects” timeline groups sales efforts and campaigns, with tags that can reflect stages like initial outreach or follow-up. For goal-setting, an objectives board uses SMART-style framing—specific metric, achievable, relevant, time-bound—to pressure-test targets before committing them to the plan.

The build also includes feedback capture, email and script management, and task tracking. A feedback view filters contacts where a “feedback” property is not empty, then groups results by segment. Email planning is handled through an emails database that tracks status and stores outreach scripts as templates; a separate scripts workspace supports brainstorming categories like cold outreach, warm outreach, call scripts, follow-ups, and icebreakers. Finally, an “Actions” board links tasks to projects and organizes them by status and priority, enabling teams to track concrete work like “browse LinkedIn and list first 20 candidates” for a specific segment.

To round it out, the workspace adds a “Favorite Tools” page—built from a tools database and filtered by tags such as prospecting—so the team can jump directly to resources like HubSpot, Gmail, Clutch, and LinkedIn. The result is a multi-page Flotion workspace that functions as a complete sales operating system: research, pipeline management, communications assets, and day-to-day execution all connected through consistent properties and relations.

Cornell Notes

The Flotion sales pipeline build organizes lead management around buyer personas, segmented prospecting, and pipeline stages (Not contacted → In conversation → Proposal sent → Circle back/Idle → Active, with archive for completed work). It pairs CRM-like views for organizations and contacts with execution tools: meetings, projects/timeline, SMART-style objectives, feedback capture, and an actions board that links tasks to projects. Outreach support is handled through an emails database and a scripts workspace, where scripts are brainstormed, categorized, and copied into email templates. A tools page with tag-based favorites keeps prospecting resources one click away. The system matters because it turns scattered sales activities into one connected workspace that teams can update and reuse.

How does the build turn buyer research into something actionable inside the pipeline?

It starts with a personas workspace using a user persona template component. Each persona includes key use cases, pain points, expected actions, needs, plus demographics and psychographics. Those personas then inform how the pipeline is segmented—so the team can group prospects by industry/use case (e.g., full brand identity projects, alcoholic beverages, accounting, tech startups, e-commerce) and route contacts into the right pipeline tracks.

What pipeline stages are used, and how do they shape day-to-day work?

The pipeline uses stages such as Not contacted, In conversation, Proposal sent, Circle back, Idle, and Active, with an archive option for completed projects. These statuses drive filtered views—like a prospecting view filtered to only show contacts where status is Not contacted—so the team always knows who needs outreach, who is mid-process, and who needs follow-up later.

How are organizations and contacts handled so the CRM stays navigable?

The build adds an Organizations view that lists companies with dropdowns for industry and relationship type, plus a way to select contacts belonging to those organizations. It also creates contacts views that can be filtered by pipeline status (e.g., only prospects not contacted yet) and grouped by relationship type or segment, making it easier to focus prospecting efforts.

What components support execution beyond tracking contacts?

Execution is covered with a Meetings section (meeting templates and time entries that can appear in a calendar), a Projects timeline (campaigns and internal sales efforts grouped by stage tags like initial outreach vs follow-up), and an Actions board (tasks linked to projects and organized by status and priority). This structure connects pipeline movement to concrete work items.

How does the system manage outreach content like scripts and emails?

It uses an emails database to track outreach status and store scripts as templates. A scripts workspace supports brainstorming and categorizing script types—such as cold outreach scripts, warm outreach, call scripts, follow-ups, and icebreakers. When a script is ready, it can be copied into an email template so new outreach messages can start from the same approved wording.

Why include a SMART-style objectives board and a feedback view?

The objectives board keeps targets disciplined using a SMART framework (specific metric, achievable, relevant, time-bound). The feedback view filters contacts where a feedback property is not empty and groups results by segment, giving a quick board for what prospects actually responded to—useful for refining outreach and proposals.

Review Questions

  1. Which pipeline stage would a contact move to after proposals are sent but no response arrives, and what view would likely surface them next?
  2. How does linking tasks to projects in the Actions board change how a team plans and tracks sales work?
  3. What fields and categories make the scripts workspace useful for turning brainstorming into repeatable outreach templates?

Key Points

  1. 1

    Build the pipeline around connected databases and views: personas, organizations/contacts, pipeline stages, meetings, projects, objectives, feedback, emails/scripts, and actions.

  2. 2

    Segment prospects by industry/use case so pipeline movement stays relevant to the branding agency’s target customers.

  3. 3

    Use pipeline statuses (Not contacted, In conversation, Proposal sent, Circle back, Idle, Active) to drive filtered prospecting and follow-up workflows.

  4. 4

    Log meetings with templates and time entries so calls become part of the sales record and calendar.

  5. 5

    Track campaigns as projects and tie tasks to projects in an actions board organized by status and priority.

  6. 6

    Store outreach scripts as templates inside an emails database, and brainstorm new scripts in a categorized scripts workspace.

  7. 7

    Add a tag-based “Favorite Tools” page so prospecting resources (e.g., HubSpot, Gmail, Clutch, LinkedIn) are quickly accessible.

Highlights

Prospecting becomes a filtered CRM view: contacts can be shown only when their status is “Not contacted,” keeping outreach focused.
Outreach content is operationalized: scripts are brainstormed, categorized, then copied into email templates for repeatable messaging.
Tasks don’t live in isolation—each action links to a project, letting teams track work by campaign stage and priority.
Feedback is captured as a property and surfaced through a board filtered to non-empty feedback, grouped by segment.
A single workspace ties together research (personas), pipeline tracking, communications assets, and execution (meetings, projects, actions).

Topics