> For the complete documentation index, see [llms.txt](https://docs.allshore.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allshore.ai/clients-and-pipeline.md).

# Clients & pipeline

Everything about who you sell to and who you place, across three screens: **Clients & contracts**, **Pipeline**, and **Client sign-offs**.

## In this section

* [Managing clients](/clients-and-pipeline/managing-clients.md) — active clients and prospects, firmographics, the commitment gate, archiving.
* Client contacts & portal invitations — portal roles, invitations, self-service, troubleshooting.
* *More pages are being added — contracts & rates, documents, pre-sale, pipeline, and sign-offs (Linear M30).*

## Clients

A client is **active** (billable) or a **prospect** (being pursued — no invoicing, placements, or portal until you win the deal). A client's records — firmographics, contacts, commercial contracts and their documents, estimates, credential requirements — live on its detail page; budgets and your document-type taxonomy sit on the top-level Clients & contracts screen.

## Commercial contracts & rates

Contracts hold the commercial terms: currency, payment terms, and **effective-dated bill rates** per role (change a rate and history is preserved — invoicing always prices time against the rate in force on the day). Contracts can be **ended, extended, or renewed**; renewals are linked so you can follow the chain. **Budgets** cap fees or hours per contract, with burn-down projections and entry-time warnings.

## The document ledger

Signed paperwork lives on the client, typed by your **contract types** (NDA/MSA/SoW plus your own): draft → active → expired/terminated, and void-with-reason — never hard-deleted. Generate drafts from your **document templates** (merge fields fill from client + deal data into a PDF), **send** them by email behind a confirmation step, then upload the countersigned PDF and activate it. Allshore deliberately has **no e-signature** — it records and tracks; signing happens outside.

## Pre-sale

**Rate cards** feed a **pricing estimator**: role mix × rates × duration → a saved estimate, sendable as a **proposal** (cover + estimate + collateral attachments) with delivery tracked. Every outbound send is recorded — who, what, when, and what happened.

## Recruiting pipeline

**Job requisitions** per client hold role, rate band, and openings. **Candidates** move sourced → submitted → interview → offer (each move is recorded); submitted candidates appear in your client's portal. **Offers** are real records — terms snapshot, expiry, accept/decline trail — with offer letters generated and sent from the platform. **Hire** is one atomic step: it consumes the accepted offer and creates the consultant, their agreement and pay rate, the placement, and the onboarding checklist together.

## Client sign-offs

The partner-side view of timesheet approval: which submitted weeks await a client decision, the per-sheet approval activity timeline, and your override/reopen controls. (The client's side of this flow is covered in [Your clients' portal & trust](/your-clients-portal-and-trust.md).)


---

# 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.allshore.ai/clients-and-pipeline.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.