> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/ai/mcp/mcp-use-case-library/advisory-and-deliverables.md).

# Advisory and Deliverables

MCP prompts for client-facing work: flux and cash flow analysis, owner summaries, client follow-up messages, 1099 prep, and multi-entity comparisons.

Use these prompts to turn clean books into something you send or discuss with a client. They're all read-only: the assistant drafts, and you decide what reaches the client.

### Walkthroughs

<details>

<summary><strong>Trailing 12 Months Flux Analysis</strong></summary>

Ask the model to pull financial reports and compare changes across a trailing 12-month window. Use this to spot unusual movement, identify categories that need explanation, and turn report review into a focused follow-up list.

{% embed url="<https://player.mux.com/zUQ3ONeDWYQT3R2smDkyWgfVa5ghCQGkOQjEfPdIJdE>" %}

</details>

<details>

<summary><strong>Cash Flow Forecasting and Analysis</strong></summary>

Combine recent activity, account balances, and expected inflows or outflows to build a cash flow view you can discuss with a client. This is useful for planning conversations, runway checks, and highlighting timing risks.

{% embed url="<https://player.mux.com/G2dzoX81j2pUa62ywTIKZA7lywdc302Vqiy4LuTlL2mU>" %}

</details>

### Prompts

<details>

<summary><strong>Prepare client follow-up</strong> <em>(read-only)</em></summary>

{% code overflow="wrap" %}

```
Review the open transaction questions and draft a client-friendly message. Do not change any Kick data. Include transaction dates, amounts, and short context for each question.
```

{% endcode %}

This is a strong read-only workflow: the assistant gathers context while the accountant stays in control of the client message.

</details>

<details>

<summary><strong>Owner-facing monthly summary</strong> <em>(read-only)</em></summary>

{% code overflow="wrap" %}

```
For entity 123 and January 2026, draft a short owner summary: cash in/out, top 5 expenses, largest unusual transactions, and three plain-English questions. Do not change any data.
```

{% endcode %}

</details>

<details>

<summary><strong>Vendor spend / 1099 prep</strong> <em>(read-only)</em></summary>

{% code overflow="wrap" %}

```
Pull expenses by vendor for entity 123 for 2025. Flag vendors over $600 with missing or inconsistent counterparty names. List the top 10 vendors by spend with totals.
```

{% endcode %}

Then drill into one vendor:

{% code overflow="wrap" %}

```
For vendor Stripe, drill into account transactions and list payments missing 1099-relevant detail.
```

{% endcode %}

</details>

<details>

<summary><strong>Multi-entity comparison</strong> <em>(read-only)</em></summary>

{% code overflow="wrap" %}

```
Compare Acme LLC and Beta Co for Q1 2026: revenue, top expense categories, uncategorized count, and unmatched-transfer count (categorized Transfer or Credit Card Payment, with no match). Call out material differences.
```

{% endcode %}

</details>


---

# 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.kick.co/ai/mcp/mcp-use-case-library/advisory-and-deliverables.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.
