Stop guessing prices because you forgot what you quoted last time. Ten minutes to set up a quote log means you never price a job from memory again.
| Setup time | About 10 minutes |
|---|---|
| Review cadence | Once a month |
| Core tools needed | Google Doc, Notion page, or an AI project workspace |
| Not recommended for | One off annual quotes or legally binding contract terms |
1. Create one quote log file
Make a single running file, a Google Doc, Notion page, or a project file in whichever AI tool you use, that stays with your assistant across chats. Name it something plain like ‘Quote Log 2026’. This is the one place every quote you ever send will live.
2. Log every quote right after you send it
Paste the finished quote to your assistant and say, log this: client type, scope, price, date. It writes one line, for example ‘Oct 3 – 5 page business site plus SEO – 1500 USD – TechStart Solutions’. In a few weeks this becomes real pricing history.
3. Ask it to check the log before every new quote
Before you price a new job, say: check the quote log for anything similar before we price this. It surfaces the closest match, like ‘Jan 12, similar 5 page site, you charged 1500’. Now you’re deciding with precedent instead of a gut number.
4. Let the precedent set the price
Use that match to hold your price, justify a fair increase, or catch yourself about to undercharge. Example: you were about to say 900, the log shows 1500 for less scope in January, so you quote 1550 instead.
5. Review the whole log once a month
Ask: summarise my quote log, price range, most common scope, any client who negotiated hard. This catches pricing drift early, before it becomes a habit you didn’t notice.
A worked example
A freelance web designer is about to quote a new small business for a 5 page website with basic SEO.
Before
Hi, happy to build your 5 page site with basic SEO, I would price that at 900.
After
Your quote log shows: Jan 12, a very similar 5 page site with SEO went for 1500, client paid without pushback. Suggest 1500 to 1600 for this one unless the scope is smaller. Final quote sent: Happy to build your 5 page site with basic SEO, the investment for this scope is 1550.
Three ways to bend it
Sales reps on quota
Log every discount given against deal size, so the assistant flags ‘you have never gone past 10 percent off for a deal this size’ before another exception gets approved.
Agencies quoting retainers
Keep a shared log of monthly retainer scopes and rates by client size, so new retainer proposals start from real numbers instead of each account lead guessing on their own.
Procurement reviewing vendor quotes
On the buying side, log what vendors quoted before for similar work, so the assistant flags when a new quote looks unusually high or low against that history.
When it goes wrong
The assistant forgets the log between chats
Use a tool with a persistent file or project, like a linked Google Doc or a project workspace, rather than a one off chat, or paste the log back in at the start of each new conversation.
The log is getting too long to be useful
Ask the assistant to collapse it into one summary line per client or scope type instead of every raw quote, and archive older entries every few months.
When not to use this
If you only send one or two quotes a year, or every job is so different that nothing is comparable, a log is more setup than it is worth, just price each one on its own merits. Do not lean on it for contracts where legal terms matter more than a past number either, a log tells you pricing history, not what you are legally bound to.
What you can now do
You price from evidence instead of memory, so you stop undercharging clients who would have paid more and overcharging the ones who would have walked.
Part of Making Life Easier With AI, a weekly walk-through of one small thing AI can take off your plate.
Take this further
Act as a blunt hiring manager who has read ten thousand resumes, not a career coach. I will paste my full resume and the job description I want. Rewrite the whole resume for that role, section by section, in this order: summary, experience, skills, education. Rules: every experience line leads with impact, not duty. Use bracketed placeholders like [8 percent] for any number I did not give you, and list at the end every placeholder I need to replace with a real figure. Keep it to one page of text. Plain formatting only, no tables or columns, so screening software can parse it. After the rewrite, tell me the three weakest claims that need evidence before I send this anywhere. My resume: [paste resume]. The role: [paste job description].
Takeaways
- Create one dedicated, persistent quote log file today, a Google Doc, Notion page, or a Claude or ChatGPT project, rather than relying on scattered chat history.
- Right after sending any quote, paste it to your assistant and have it add a single line with client type, scope, price, and date.
- Before pricing the next job, explicitly ask the assistant to check the log for a comparable past quote before you say a number out loud.
- Once a month, ask for a summary of your price range, most common scope, and any client who negotiated hard, so drift gets caught early.
- When the log gets long, ask the assistant to collapse old entries into one summary line per client or scope type and archive the rest.
Questions people actually ask
How do I get an AI assistant to remember quotes I’ve sent before?
Keep one persistent file, like a Google Doc, Notion page, or a project inside Claude or ChatGPT, that stays linked to your assistant across chats. Paste each finished quote into it and ask the assistant to log the client type, scope, price, and date as a single line, so the history builds up automatically over time.
Which AI tools actually keep memory between separate chats?
Claude Projects keeps a knowledge base of files that every chat inside that project can read, though it does not carry over chat transcripts automatically. ChatGPT has a memory feature that can reference facts from past conversations. Notion pages work with any connected AI tool since the memory lives in the document, not the chat session.
What should I write down for each quote so the log is actually useful?
Four things in one line: who the client is or what type of client they are, the scope of the work, the price you quoted, and the date you sent it. That is enough detail for an assistant to later surface a close match when you are pricing something similar, without the log turning into a messy wall of text.
When is a quote log not worth setting up?
Skip it if you only send one or two quotes a year, since there is nothing to compare against. It also is not worth it when every job is so different that no past quote is comparable, and it should not be used for anything involving legal contract terms, since a log only tracks pricing history, not binding obligations.
How often should I check in on the whole log instead of just one entry?
Once a month. Ask the assistant to summarize the price range, the most common scope of work, and whether any client pushed back hard on price. That catches pricing drift early, before undercharging or inconsistent pricing turns into a habit you did not notice forming.
Sources
- How can I create and manage projects?Anthropic (Claude Support)
- Set up Notion for your agentNotion
- OpenAI updates ChatGPT to reference your other chatsTechCrunch
What happens next
Expect persistent memory and project style features to keep expanding across Claude, ChatGPT, and Notion, making it easier to keep a running log linked to an assistant without repasting it each session. Worth watching is how these tools handle long logs, since retrieval quality can degrade as entries pile up without periodic summarizing. Freelancers and agencies adopting this early will likely build pricing consistency faster than those still pricing from memory.
