> For the complete documentation index, see [llms.txt](https://guide.givewise.ca/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.givewise.ca/for-financial-professionals/for-financial-advisors-getting-started/compare-cash-vs.-securities-client-tool.md).

# Compare Cash vs. Securities (Client Tool)

## Show Clients the Tax Impact of Cash vs. Securities: Donation Tax Calculator

***

When charitable giving comes up, one of the easiest ways to add value is to show—not just explain—the difference between giving cash and appreciated assets.

This is especially useful in conversations around capital gains, business sales, or year-end planning.

Use this tool to:

* compare after-tax outcomes in real time
* demonstrate the benefit of donating securities
* guide more strategic giving conversations

👉 [**Try the Tax Calculator in Your Next Client Conversation**](https://taxcalc.givewise.ca/)

***

#### Contact Us

For additional support or to request resources, contact:

* **Dan Kyte**, Director of Finance and Investments: <dan.kyte@givewise.ca>
* **General Inquiries:** <donations@givewise.ca> | 604-302-1760


---

# 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://guide.givewise.ca/for-financial-professionals/for-financial-advisors-getting-started/compare-cash-vs.-securities-client-tool.md?ask=<question>&goal=<user_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.
