Your Team’s Existing AI Skills Already Transfer to Claude

If your people have spent time with ChatGPT or any other AI tool, they have built up something genuinely useful. For a start, they know how to write a clear instruction. They can also give background before asking for an answer. Above all, they know how to look at a weak first draft and push for something better.

None of that is wasted. Indeed, the core skill of working with AI is the same across tools:

• Being specific about what you want
• Giving enough context to work from
• Reviewing the output critically rather than accepting the first attempt
• Refining through follow-up rather than expecting perfection in one go

All of this carries directly across to Claude. In other words, your team is not starting from zero. Instead, they are moving a skill they already have to a tool that happens to be very good at construction-relevant writing, reasoning and document work.

There is really only one thing that does not transfer automatically, and it is worth understanding properly before we fix it.

The One Thing That Does Not Transfer: Your Stored Context

When a person switches tools, their prompting habits come with them. What does not come with them is any accumulated understanding the previous tool had built up about the business.

This is where a lot of people get caught out, because the situation has recently changed and there is some confusion about it. So let us be accurate.

“But doesn’t Claude have a memory now?”

Yes, it does, and this is worth getting right because plenty of older guides still say otherwise.

Anthropic rolled out persistent memory to all Claude users during 2026, across free and paid plans. Claude now quietly builds a picture of you across conversations, synthesising details such as your role, your preferences and how you like responses formatted, then carrying that forward so you are not re-explaining yourself constantly. You can view and adjust this in Settings under Memory.

Here is the important distinction for a business, though. That automatic memory is:

That is genuinely helpful for an individual. It is not the same as giving your whole team a single, deliberate, accurate description of the business and the exact documents you want the AI to work from. For that, you want something structured, shareable and under your control.

That is exactly what Claude Projects are for.

What Claude Projects Actually Is

Claude Projects is a feature inside claude.ai. Think of it as a dedicated workspace that holds your business context, your instructions and your key documents in one place.

The practical effect is simple. Every conversation you start inside a Project already has access to everything you have loaded into it. No re-briefing. No pasting the company overview at the top of every chat. Your estimator opens the Project, types the actual task, and gets an answer that already understands the business.

“The automatic memory learns about a person. A Project is where you deliberately load everything the AI needs to know about your business, once, so every conversation starts fully briefed.”

A useful way to picture it: Project Instructions are the job description you hand a new starter, and the uploaded documents are the reference folder on the shared drive. Once both are in place, anyone can walk in and get productive immediately.

Projects also keep their own separate memory space, so what happens inside your company Project stays scoped to that Project rather than bleeding into unrelated personal chats.

How to Set Up a Project for Your Construction Business

You can have a working Project running in under fifteen minutes. Here is the process.

1. Open claude.ai and find Projects in the left-hand sidebar. This is your list of workspaces.
2. Click New Project and give it a clear name. Use your company name, or name it by department or function, for example “Estimating” or “Client Comms,” if you want tighter, purpose-built workspaces.
3. Add your Project Instructions. This is the standing brief. Paste in a detailed description of the business: what you do, who your clients are, your tone, and what a good output looks like. There is a ready-made template below.
4. Upload your key documents. Add the reference material Claude will need regularly, such as contract templates, a company overview and typical scopes of works.
5. Start working. Every conversation inside that Project now has all of it available automatically.

If you run several distinct types of work, it is often better to create a few focused Projects rather than one enormous general one. An estimating Project loaded with rate references and standard scopes will outperform a catch-all workspace, because the context is tighter and more relevant to the task.

What to Put in Your Project Instructions

This is the part that decides how good your results are. The more specific and accurate the instructions, the more consistent Claude will be across every conversation your team runs.

Here is a template you can adapt straight away. Fill in the brackets with your own details.

Extra details that lift quality further

In addition, a few details tend to lift quality further for construction firms:

• Name the standards and terminology you use, for example JCT or NEC contract families, so language stays correct.
• State your non-negotiables, such as never inventing figures, always flagging assumptions, and asking for missing information rather than guessing.
• Describe your clients’ priorities, because a housing association values something different from a private developer, and the writing should reflect that.

Upload your most-used documents alongside these instructions. Claude will reference them automatically when a task calls for them, which means a client update can be written in your voice and a scope can follow your usual structure without anyone pasting examples in every time.

A Worked Example: An Estimator’s Project

Picture a mid-sized commercial fit-out contractor. The estimating team sets up a Project called “Estimating,” loads the Project Instructions above, and uploads their standard scope-of-works template, a recent example tender response, and their preliminaries checklist.

From that point on, when an estimator needs to draft a qualifications-and-exclusions list for a new enquiry, they do not explain the business or paste in examples. They describe the specific job, and Claude produces a first draft that already follows the company’s structure, tone and standard exclusions. The estimator reviews and adjusts, which is where their judgement belongs, rather than spending that time on set-up.

The saving is not dramatic on any single task. However, across a week of enquiries, it adds up to real hours back.

Common Mistakes Construction Businesses Make

• Vague Project Instructions. “We are a building company” tells Claude almost nothing. Thin instructions produce generic output, and generic output is exactly what wastes people’s time.
• Uploading everything, unfiltered. Loading hundreds of unrelated files makes the context noisy. Curate a small set of genuinely useful reference documents instead.
• Assuming the automatic memory replaces a Project. The personal memory is helpful, but it is not a controlled business brief and it is not shared. For team use, the Project is what you want.
• One giant Project for everything. Mixing estimating, marketing and HR in a single workspace dilutes relevance. Separate Projects keep each one sharp.
• Never updating the instructions. Turnover changes, services expand, tone preferences shift. A Project set up once and forgotten slowly drifts out of date.
• Trusting figures without checking. Claude is excellent at structure and language. It is not a substitute for verifying numbers, rates or contractual detail. Always check the facts before anything leaves the building.

Best Practices

• Write instructions as if briefing a capable new employee. Clear, specific, and honest about how the business actually works.
• Keep uploaded documents current. Replace outdated templates so Claude is not working from last year’s version.
• Build role-specific Projects for the teams that will get the most from them, typically estimating, contract management and client communications.
• Set explicit guardrails in the instructions: no invented figures, flag assumptions, ask when information is missing.
• Review each Project monthly. A five-minute check keeps the context accurate as the business changes.
• Standardise across the team. A shared, well-built Project means everyone gets consistent output, not a different result depending on who is typing.

Actionable Tips You Can Apply Today

• Create one Project this week for the team that does the most repetitive writing.
• Fill in the Project Instructions template with your real details, not placeholders.
• Upload three to five of your most-used documents, no more to begin with.
• Run a real task through it and compare the first draft to what you would normally get cold.
• Note anything the output got wrong about the business, and tighten the instructions accordingly.
• Once it works, show one colleague how to open and use it. Consistency comes from shared setup.

Key Takeaways

Frequently Asked Questions

Brief Once, Work Faster All Year

The reason AI so often fails to save time in construction businesses is rarely the tool itself. It is the constant rebuilding of context: explaining the business again, pasting the same examples again, starting cold every morning. Claude Projects removes that friction. You brief the business once, load the documents once, and from then on your team opens the Project and goes straight to the work.

Set one up this week for whichever team does the most repetitive writing. A focused fifteen minutes now will change how the rest of the year feels for that team.

In the next issue we tackle the question we get asked more than any other: Claude vs ChatGPT: An Honest Comparison for Construction Businesses. No hype and no loyalty, just a straight look at where each one earns its place on a construction business.

If you would like help building this properly across your business, Construct Virtual designs and implements AI systems specifically for construction and trade firms. Explore our AI implementation services for construction firms to see how a structured setup could work for your team.