> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/learn/close-more-deals/streamline-sales.md). # Streamlining Your Sales Process Turn your sales process into a Pipeline that your team follows the same way every time, with each Stage's next steps ready when a deal reaches it. A good sales process is simple to follow, repeatable, and something new team members can learn quickly, and you can refine it over time. In Daylite, an Opportunity Pipeline holds that process. It defines each step a deal goes through and shows how far along each Opportunity is, so everyone on your team knows what needs to happen next and who is doing it. ## Map Your Sales Process Before You Build It Start with the high-level steps every lead moves through, such as Inquiry, Proposal, and Negotiation. Each step becomes a Stage in your Pipeline. Your whole team shares the same Pipelines, so a new hire follows the same process as your most experienced salesperson. If you sell products or services that follow different steps, plan a separate Pipeline for each one. ## Set Up Your Sales Pipeline You build Pipelines on Mac. After you save a Pipeline, you can use it on Mac, iPhone, and iPad. 1. **Build the Pipeline.** Choose **Daylite** > **Settings** > **Pipelines**, create a Pipeline for Opportunities, and add a Stage for each step of your process. If you already have a similar Pipeline, duplicate it and update the copy. See [How Do I Build a Pipeline?](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/pipelines#how-do-i-build-a-pipeline) 2. **Add the Tasks and Appointments each Stage needs.** Add the follow-ups a Stage always calls for, such as sending a quote. When a deal reaches the Stage, they're waiting for you, with due dates set from when the Stage starts or ends. See [Add Tasks and Appointments to a Stage](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/pipelines#add-tasks-and-appointments-to-a-stage). 3. **Assign the Pipeline to each Opportunity.** An Opportunity needs a Pipeline before it can move through Stages or appear on the Opportunities Board. See [How Do I Assign or Change a Pipeline?](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/pipelines#how-do-i-assign-or-change-a-pipeline) To keep new Opportunities from being created without one, set your most-used Pipeline as the default. ## Move Each Deal Through Its Stages Keep each Opportunity's Stage up to date, so anyone on your team can check a deal and see how it's progressing. Stages also let you build filters and Smart Lists to report on your Opportunities. 1. **Advance the deal on the Opportunities Board.** Drag its card to the next Stage. Drop it on the Stage's title to open the **Advance Stage** window, where you can check the Start Date, create the Stage's Tasks and Appointments, and add a Note. See [How Do I Change a Pipeline Stage?](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/pipelines#how-do-i-change-a-pipeline-stage) You can also change the Stage from the Opportunity itself. See [From the Record](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/pipelines#from-the-record). 2. **Watch for deals that stall.** The Board shows how many days each Opportunity has been in its current Stage, so you can spot the ones that are bottlenecked and focus on moving them along. See [Moving Stages](https://docs.daylite.app/help/mac-fundamentals/opportunities/opportunities-boards#moving-stages). 3. **Close the deal.** Drop the card on **Won**, **Lost**, **Abandoned**, or **Suspended** at the bottom of the Board, then confirm the State and choose a reason. The Opportunity leaves the Board but stays in **All Opportunities**. See [Updating Stages](https://docs.daylite.app/help/mac-fundamentals/opportunities/opportunities-boards#updating-stages). ## Choose Between Stage Tasks and an Activity Set * **To create follow-ups only when a deal reaches a certain Stage,** [add Tasks and Appointments to that Stage](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/pipelines#add-tasks-and-appointments-to-a-stage). A Stage's activities are created as the deal reaches it, so the deal arrives with its next steps. * **To create a batch of dated activities in one step,** such as a sales follow-up sequence, [apply an Activity Set](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/activity-sets#how-to-apply-an-activity-set). Every Task and Appointment is created at once, dated from the start or end date you enter. * **To run a repeatable process for a Person, Company, or Group,** apply an Activity Set. Pipelines apply only to Opportunities and Projects. You can use both on the same Opportunity. Activity Sets can be created and applied only on Mac. See [Activity Sets vs Pipelines](https://docs.daylite.app/help/mac-fundamentals/tools-and-utilities/activity-sets#activity-sets-vs-pipelines). ## Hand Off Won Deals to Delivery Winning an Opportunity doesn't create a Project. When you close the deal, create a Project from the Opportunity on Mac. The Project gets the Opportunity's name and linked Contacts, Notes, and emails, and the Opportunity stays in place, linked to it. You keep the sales record next to the delivery work. See [New Project From Opportunity](https://docs.daylite.app/help/mac-fundamentals/projects/creating-and-configuring-projects#new-project-from-opportunity). Projects move through their own Pipelines on the Projects Board. See [Project Boards](https://docs.daylite.app/help/mac-fundamentals/projects/projects-board). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.daylite.app/help/learn/close-more-deals/streamline-sales.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.