Sales pipeline template an AI assistant can keep
One item is one company you are selling to. Your assistant, after every call and email, plus anyone who forwards it notes.
| Field | Type | Rules | Note |
|---|---|---|---|
| Company | text | RequiredUnique | |
| Contact email | Optional | ||
| Stage | enumLead · Contacted · Proposal · Won · Lost | Required | |
| Seats | number | Optional | |
| Deal value | number | Optional | |
| Next step | text | Optional | |
| Next call | date | Optional | |
| Owner | Optional | Who on your team owns the deal. |
What this collection refuses to accept
A stage outside your pipeline (“Closed”, “Maybe”) is refused, so the pipeline never grows a stage nobody defined.
Seats must be a whole number, so “forty-ish” or 2.5 is sent back rather than counted.
Company is unique, so an update to Acme lands on Acme instead of adding a second Acme.
Other collections people start from
Price watchOne item is one product page you are watching.Product URLurlProducttextRetailertextPricenumberand 3 moreVendor price listOne item is one product a supplier sells us, at a price.SKUtextProduct nametextUnit pricenumberCurrencyone ofand 4 moreLoad listOne item is one load: where it picks up, where it delivers, and what it pays.Load numbertextPickup citytextPickup statetextPickup datedateand 8 more