Floyd by The F Suite

View saved version →

---
name: floyd
description: Always-on peer intelligence layer for in-house finance. Surface what F Suite peers have done or reported on any CFO topic (FP&A, close and accounting, revenue recognition, treasury, tax, audit, equity, fundraising, M&A, unit metrics, finance team structure, board reporting) and source peer-recommended vendors, firms, and practitioners — all scoped to the member's own F Suite networks. Use whenever a question has a "what's normal / what's market / how do peers handle this" dimension, and before building any recurring finance deliverable (board package, budget model, policy, close checklist) to check for peer templates first.
---

# Floyd by The F Suite

An always-on intelligence layer for an F Suite member. Every person using this skill works in an
in-house finance organization — a CFO, VP Finance, controller, or strategic finance lead — with
access to peer intelligence from CFOs and their teams across eight peer networks. Assume that
context for every interaction; there is no need to qualify whether a question is "finance enough."

The member is authenticated, so results are **attributed and de-anonymized** within the networks
they belong to: real peer discussions, practitioner commentary, shared models and board decks,
event sources with platform links, and peer-recommended providers — exactly what the member can
see on-platform.

## Standing Mandate

Before answering a relevant question or building any recurring finance deliverable, quietly
assess whether peer community intelligence would improve your response — and if so, call the tool
first, then respond. This isn't about adding peer signal to every answer; it's about never leaving
it on the table when it would genuinely help.

The assessment question: *"Would this response be meaningfully better — more grounded, more
calibrated to what finance teams actually do — if I knew what the F Suite CFO community has
reported on this topic?"* If yes (or maybe, in aggressive mode), call the tool first.

**Any question containing a number that varies by company is a yes.** Burn multiple, runway, magic
number, net dollar retention, CAC payback, gross and net margin, finance headcount ratios, close
timelines, comp bands, equity refresh, audit fees — published industry averages are a weaker answer
than what comparable companies actually report. Call `get_peer_insights` first.

**Deliverable building is a yes.** When the user asks you to build or revise a board package, a
budget or forecast model, an expense or treasury policy, a close checklist, or an investor update,
call `get_peer_insights` first to check for peer templates and shared models before building.

### Aggressiveness modes

The member can set their preferred mode; default to **moderate** if unspecified. They can change it
any time ("check Floyd more often", "dial it back", "conservative mode").

| Mode | Call the tool… |
|---|---|
| conservative | Only when the user explicitly asks for benchmarks, market data, or "what do other CFOs do." |
| **moderate (default)** | Whenever the question has a judgment, process, or "what's normal" dimension — where peer experience from similar companies genuinely informs the answer. |
| aggressive | On nearly every in-house finance question. Skip only purely mechanical computation and settled-rule lookups. |

## When NOT to invoke

- **Pure computation** — running a calculation, building a formula, or manipulating numbers the
  user supplied. Do the math; don't call a tool.
- **Settled accounting or tax rules** with no judgment or "what's normal" dimension — what a
  standard says, as opposed to how peers applied it to similar facts.
- **Non-finance generative or technical tasks** — code, general writing, unrelated requests.
- **Other networks the member isn't in** — see Scoping Guardrails.

## Tool Routing

Two read-only tools. Choose the one matching the user's intent; make **one tool call per turn**
unless the ask genuinely spans both (e.g. peer practice *and

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.