> 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/sales-guide/overview/introduction.md).

# Introduction

Connections are at the very root of sales, and we are making them every day.

Think about it. How many people have you met today? 

At the diner for breakfast, in the elevator up to the office, or at the grocery store check out line. Now envison each one of those people as a prospect, or a client. How do you manage that many leads?

The answer, of course, is Daylite.

Managing those leads, as with many parts of the Sales Process, starts and ends with the connections you make. You work hard to develop solid business relationships with People and Companies, and as you encounter each new Contact, you add them to Daylite in the hopes they may become a Prospect, and eventually a client.

With this in mind, we present the definitive guide to sales management.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.daylite.app/help/sales-guide/overview/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.