Claude Project: Build a Persistent Estimating Knowledge Base

What This Builds

A persistent AI assistant that knows your company's estimating standards: your standard scope inclusions and exclusions by trade, your preferred subcontractors, your historical unit costs, your company's project experience, and your typical bid assumptions. Instead of re-explaining your company's approach on every bid, the assistant already knows it. You query it like a knowledgeable senior estimator who's seen every project your firm has built.

Prerequisites

• Claude Pro subscription ({{tool:Claude.price}}; sign up at {{tool:Claude.url}})
• 5-20 historical project documents (bid summaries, scope letters, estimate workbooks, lessons learned)
• 2-3 hours for initial build; 15 minutes per project to maintain
• Comfortable with Claude's basic chat interface

The Concept

A Claude Project is like a shared office folder that stays open between conversations. Every file you add to it becomes part of Claude's permanent context for that project, unlike regular chats where Claude forgets everything when you close the window. Think of it like onboarding a new senior estimator: you spend a few hours showing them past projects and explaining how your firm works, and after that they can answer questions and help you work without constantly re-explaining the basics.

Build It Step by Step

Part 1: Set Up the Project and Write System Instructions

1. Create the Claude Project:

1. Log into Claude at {{tool:Claude.url}}
2. In the left sidebar, click Projects → New Project
3. Name it: "[Company Name] Estimating Knowledge Base"
4. You'll see a two-section project page: Instructions (top) and Files/Knowledge (bottom)

2. Write your system instructions: This is the most important step. It tells Claude how to behave as your estimating assistant. Customize this template:

You are the estimating assistant for [Company Name], a commercial general contractor specializing in [project types: healthcare, office, warehouse, etc.] in [region/markets].

YOUR ROLE:
- Help estimators retrieve historical cost data, scope language, and bidding standards
- Draft scope letters, bid cover letters, and PM handoff memos in our company's style
- Answer questions about how we typically handle scope inclusions, exclusions, and assumptions
- Help analyze specifications for cost-impacting requirements

HOW TO ANSWER:
- Always cite which historical project your cost data comes from
- When giving unit costs, provide a range based on multiple projects (not a single number)
- Flag when you're uncertain or when our historical data doesn't cover a specific scenario
- Use construction industry terminology (CSI divisions, trade names, unit measures)
- Keep scope language tight and defensible. Avoid vague language

OUR STANDARDS:
- We always exclude [your standard GC exclusions, e.g., "hazmat abatement, furniture, dewatering unless specifically shown on drawings"]
- We always include [your standard GC inclusions, e.g., "one mobilization, temporary fencing, job trailer, all required permits"]
- Our standard general conditions range: [X-Y%] depending on project complexity
- Our typical contingency for [type A] projects: [X%]; [type B] projects: [Y%]

COMPANY BACKGROUND:
[2-3 sentences about your firm: years in business, project types, markets served, any certifications]

Click Save after writing your instructions.

Part 2: Upload Historical Project Data

3. Collect your source files: Gather as many of these as you can find (quality matters more than quantity):

• Past estimate summary sheets (Excel or PDF)
• Winning bid proposals/cover letters
• Scope letters you've sent to subcontractors
• Project closeout cost summaries (actuals vs. budget)
• Lessons learned documents from past projects
• Your standard scope inclusion/exclusion lists (if documented)

4. Prepare files for upload: Clean up file names to be descriptive:

• 2024-Hospital-Wing-Addition-Bid-Summary.xlsx ✓
• Estimate Final.xlsx ✗

For Excel files with complex formulas, save as PDF or copy the data into a simple table format.

5. Upload to the project:

1. In your Claude Project, click Add files or the + in the Files section
2. Upload files one at a time (or drag multiple)
3. Wait for each to process. You'll see them listed when ready
4. Upload 5-15 files to start; add more over time

Part 3: Test and Refine

6. Test with your most common question: Start a conversation in your project and ask something you'd actually need:

What did we budget for mechanical scope per square foot on our recent hospital projects?

What good output looks like: "Based on [Project A] (2023) and [Project B] (2024), mechanical scope on our hospital projects has ranged from $28-$35/SF installed, depending on the complexity of the medical gas systems. [Project A] at $28/SF had standard exam room MEP; [Project B] at $35/SF included specialized OR suite systems."

7. Test scope letter drafting:

Write a scope letter to send to concrete subcontractors for a 3-story office building. Use our standard inclusions/exclusions and company style.

What you should see: A scope letter that reflects your firm's typical language, not generic ChatGPT boilerplate.

8. Refine based on the output: If the output doesn't match your firm's style or standards, update your system instructions with more specific guidance and test again. Common refinements:

• Add more specific scope language to the instructions
• Upload more example scope letters to demonstrate your preferred style
• Add specific notes about how you handle particular project types

Real Example: Healthcare Estimating Knowledge Base

Setup: A regional GC uploads 8 past hospital and medical office project summaries (bid amounts by division), 6 winning scope letters for major trades, their standard Division 01 general conditions template, and 3 lessons learned documents.

Input (query during active bid): "I'm estimating a 25,000 SF outpatient surgery center. What general conditions amount and mechanical scope cost should I use as a starting benchmark?"

Output: "Based on our 5 healthcare projects between 15,000-40,000 SF, general conditions have ranged from 8-12% of total project cost, with the higher end on phased occupied facility projects. For mechanical, our outpatient facilities have ranged from $32-$42/SF, driven primarily by the scope of medical gas and specialty HVAC. The [Surgery Center Project, 2023] at 22,000 SF was similar. We budgeted $38/SF mechanical and landed at $41/SF actual due to additional scope during construction."

Time saved: Instead of 30 minutes of spreadsheet archaeology, this query took 10 seconds.

What to Do When It Breaks

• Claude gives generic answers instead of citing your projects → Your uploaded files may not be in a format Claude can read well. Try uploading simpler text summaries alongside the Excel files.
• Claude doesn't remember past conversations → Make sure you're working inside the Claude Project (look for the project name in the header), not in a regular chat window
• System instructions not reflected in responses → Re-read your instructions for ambiguous language; make the rules more explicit and specific
• Cost data seems wrong → Ask Claude to cite exactly which file its answer came from; this lets you verify and correct the source

Variations

• Simpler version: Use only 3-5 project summaries and focus the instructions entirely on scope language drafting. Skip the historical cost lookup functionality
• Extended version: Add a separate Claude Project for each major project type (healthcare, office, warehouse) with specialized instructions and project data for each vertical

What to Do Next

• This week: Add the first 5 historical projects and test scope letter drafting
• This month: Add all completed projects from the past 3 years; refine instructions based on what's missing
• Advanced: Create sub-projects for specific project types (healthcare, education) with specialized knowledge for each

Advanced guide for Construction Cost Estimator professionals. Claude Pro subscription required. Claude interfaces may change. Visit {{tool:Claude.url}} for current documentation.