Cowork vs Code
You have a Silverado repossession decision. Do you paste the Dealertrack + RouteOne + Excel data into the chat, or attach the files to a Project?
The answer depends on whether this is the first time or something you will run again.
The operating rule
Recurring with the same questions? Use a Project with files attached.
Most people at Car-Mart waste time by treating every decision as new. The difference is whether Claude has to re-learn the context every time or whether the context stays in the room.
The two flows
Cowork (Chat)
- Open a fresh chat
- Paste the relevant account data (redacted)
- Ask the specific question you need answered
- Review the output, then copy the recommendation into your ticket or escalation
Best when you're seeing the situation for the first time or when the details are truly unusual.
Code (Project + Files)
- Create a Project
- Attach the stable pieces: redacted sample accounts, prior similar cases, regional policy document, standard checklist
- Each new instance, attach only the fresh data
- Ask Claude to apply the same logic to the new inputs
Best when you will run this same type of decision three or more times.
Four Car-Mart examples
You’ve never worked a Silverado repo at this store before. The account has mixed signals on RouteOne and the customer’s payment history is irregular. Paste the three files into a fresh chat, ask Claude to walk through the decision factors, then copy the recommendation into the ticket. You are learning the pattern while solving the case.
You have already done this exact type of decision multiple times. Create a Project called “Silverado Repo – Store 47.” Attach the last three redacted cases that were approved, the store’s current repossession guideline, and the standard Dealertrack export format. Now each new account only needs the fresh data attached. Claude already knows the store’s typical exposure and what the regional manager usually wants to see.
A store manager called with a one-off situation involving a collector and a customer who is also a relative of a local elected official. No one has seen this exact combination before. Open a chat, paste the relevant notes and account history, and ask for a clear escalation memo draft. Once it is sent, the chat ends. There is no need to carry this context forward.
Every Monday you receive the same set of inputs: new delinquency lists from 11 stores, current collector capacity, and the prior week’s recovery rates. Build a Project called “Weekly Collector Assignments – Region 3.” Attach the master assignment rules document, a redacted sample of last month’s output, and the standard format you want the list returned in. Each week you only drop the new delinquency files and ask for the updated assignments.
T3+ stretch goal
Pick one workflow you actually run on a regular cadence. Run it once as a pure Cowork chat. Then build the Project version with the same files and run it again.
Compare two things: how long it took you to get a usable answer, and how much you had to re-explain the second time. Most people are surprised by the difference once the context lives in the Project instead of having to be re-typed every week.
What you leave with
If this decision only happens once or you are still figuring out the pattern, open a chat and paste the data. If you will see this same type of account or request again next week or next month, attach the stable files to a Project and let the context stay there.
Apply it Monday morning. The rule is the same whether you are a store manager, regional, or payment ops.