Audience: build-along attendees (customer-facing). Everything on this page is fictional: Copperline Equipment Finance, its people, its customers and every document were made up for the AppExchange Amplified build-along. The emails below are part of the exercise, not real correspondence.
This is the brief you build against: what Copperline needs, in its own words, and the documents to test with. Set up your org with the prerequisites page, then add the fields and sample records from the Build page.
Copperline Equipment Finance is a US asset finance company of about 150 staff. It lends to small businesses buying equipment: excavators, bakery ovens, CNC machines.
Copperline runs on Salesforce. An Account is a business they lend to, and those businesses come back three or four times a year. Each finance deal is an Opportunity. Whoever creates the Opportunity owns it, collects its documents and prepares the finance agreement.
From Rachel Moreno, Salesforce Administrator. Subject: "Notes from kickoff"
Thanks for yesterday. Writing down what I think we agreed so we are on the same page.
We need a folder for each customer in our storage, and inside it a folder for each deal. Right now everything for one customer sits in one pile, and when they come back for a fourth deal nobody can tell which invoice belonged to which machine.
Inside each deal folder we want the same subfolders every time: Application, Supplier Invoice, Identity, Agreement, and Others for anything that does not fit.
Our team lives in Salesforce and will not go hunting in another window. On the Account I want to see that customer's folder, and on the Opportunity I want to see that deal's folder, with everything in it. Uploads happen from the Opportunity, and we do not want anything sitting in Salesforce file storage.
Be realistic about how people will use it. Whoever owns the deal uploads documents as they come in, and they will drop every one of them into the deal folder itself. They will not put things in the right subfolder. So it needs to sort itself.
The supplier invoice is the one that costs us money. Somebody types out the supplier, the invoice number, the date, the amount and the payment terms, then what the machine actually is: make, model, serial number and year of manufacture. On every single deal. That is where our errors come from.
From James Whitfield, Head of Operations, two days later on the same thread
Rachel forwarded me the notes. One more thing, and it is the one I care about most.
Once the invoice is keyed in, somebody builds the finance agreement by hand in Word. They copy the borrower details from the Account and the asset details from the invoice, save it as a PDF, and send it out for signature. That is the same data typed a second time. Last quarter an agreement went out with the wrong serial number on it and we only caught it at delivery.
I want the agreement built from the invoice details we already have. One click on the Opportunity, and a branded PDF agreement lands in that deal's Agreement folder, ready to send. And nobody should be able to produce an agreement before the invoice details are in.
Salesforce Documents
└── Accounts
├── Granite Peak Excavation
│ ├── OPP-2041 Excavator purchase
│ │ ├── Application
│ │ ├── Supplier Invoice
│ │ ├── Identity
│ │ ├── Agreement
│ │ └── Others
│ └── OPP-2107 Skid steer purchase
│ ├── Application
│ ├── Supplier Invoice
│ ├── Identity
│ ├── Agreement
│ └── Others
└── Sweetwater Bakehouse
└── OPP-2118 Deck oven purchase
├── Application
├── Supplier Invoice
├── Identity
├── Agreement
└── Others
| Document | Where it belongs |
|---|---|
| Finance application form | Application |
| Supplier's invoice for the machine | Supplier Invoice |
| Driving licence | Identity |
| Utility bill, used as proof of address | Identity |
| Signed finance agreement | Agreement |
| Photo of the machine once delivered | Others |
| Anything else | Others |