POLR AIBook a Meeting
Client Resource · Free

Getting started with Claude, without the busywork.

A practical walkthrough for your team. Set up Claude, hold your first useful conversation, and get to real work inside your business within an afternoon.

Five short modules. About a 25 minute read. Mirrors the structure of Anthropic's Claude 101, translated for a built environment operator.

Start the walkthroughHave us run it for your team
Reading time · ~25 minBeginner friendlyMirrors Anthropic Claude 101
What you will cover
Module 01 · The basics

Meet Claude.

Before you automate anything, you need a working understanding of what Claude is, where you can talk to it, and how to ask for what you want.

What is Claude?

Claude is an AI assistant built by Anthropic. Think of it as an extremely capable colleague who has read most of the public internet, can hold a long conversation, write, analyze, and use tools you give it. It does not browse autonomously, store private memories about you between sessions unless you turn that on, or take real world actions without your permission.

For your team, that translates into four practical jobs Claude does well right now: drafting and rewriting, summarizing and extracting, analyzing structured information like spreadsheets and PDFs, and walking you through unfamiliar work step by step.

Your first conversation

The fastest way to feel productive is to give Claude a real task you would have done yourself in the next hour. Open Claude in your browser or desktop app and try this:

claude.ai · new conversation
# Step 1. Tell Claude who you are and what you want.
you ▸I run operations at a Phoenix general contractor. Draft a polite
follow-up email to a subcontractor who is two days late on a
submittal. Keep it short. Professional, not stiff.
# Step 2. Read the draft. Then iterate, do not start over.
you ▸Make it warmer. Add a sentence offering to hop on a 10 minute call.
# Step 3. Lock in the version you like.
you ▸Perfect. Save this style as a template I can reuse for late submittals.
POLR tipThe first message sets the tone for the entire conversation. Spend ten extra seconds on context (your role, the audience, the format you want) and you will save five minutes of cleanup.

Getting better results

Most people undersell themselves to Claude. Better prompts share four things: who you are, what you want produced, who it is for, and what good looks like. You do not need to be formal about it.

prompt-pattern.txt
ROLEI am a [your role] at a [your company / industry].
TASKI need you to [verb + deliverable].
AUDIENCEThe reader is [who will see this].
SHAPEFormat it as [length / structure / tone].
CONTEXTHere is the relevant background: [paste or attach].
# Use this as a mental checklist, not a rigid template.
# If the output is not right, tell Claude what to change. Do not retype.

From helper to thought partner

The pattern above gets you clean drafts. The pattern below gets you a sparring partner. This is the CRIT framework from Geoff Woods (author of The AI-Driven Leader): Context, Role, Interview, Task. The move that changes everything is the Interview step. Instead of giving Claude every detail up front, you let Claude ask you the questions a sharp consultant would ask before forming a recommendation.

crit-framework.txt
CONTEXTHere is what is going on: [the situation, the stakes,
what you have tried, the constraints].
ROLEAct as [a senior strategy consultant / a CFO who has
closed 50 deals / a head of operations at a $50M GC].
INTERVIEWBefore you give me an answer, interview me. Ask me one
question at a time, up to three questions, to gain more
context. Wait for my answer before asking the next.
TASKOnce you have what you need, I need you to [verb +
deliverable]. Format it as [length / structure / tone].
Why the Interview step mattersThe questions Claude asks you are usually more valuable than the answer Claude gives you. They surface the assumptions you were carrying without naming them. You will start finishing the conversation with a better question than the one you walked in with.

A worked example. You are about to renegotiate a vendor contract and you want a thought partner, not a draft email.

vendor-renegotiation.example
you ▸CONTEXTOur cleaning vendor on the Butler project is over budget
and behind on punch list items. Three months left on the contract.
I want to renegotiate without losing them. They are good when they show up.
ROLEAct as a head of operations at a $50M general contractor
who has renegotiated dozens of underperforming subs.
INTERVIEWBefore you advise me, interview me. One question at
a time, up to three, to gain more context. Wait for my answer.
TASKOnce you have what you need, I need you to give me a
one page negotiation plan. Format it as: opening move, two
fallback positions, walk-away line.
# Claude will now ask you one question, wait, ask the next, and only
# then deliver the plan. The plan will be sharper because you were sharper.

Chat, Cowork, Code

Claude lives in three places once you install the desktop app. Pick the right surface for the work in front of you.

  • Chat. A blank conversation. Best for thinking, drafting, and quick analysis. This is where most people spend most of their time.
  • Cowork. Claude with access to a folder on your computer. It can read your files, build outputs, and save them back. Best when the work involves real documents you have on disk.
  • Code. A developer-focused mode that sits inside a code editor and works on software. You can ignore this unless you write or maintain code.
install.sh
01Go to claude.com/download and install the desktop app.
02Sign in with your work email. Use the same account on web and desktop.
03Pick Chat for thinking, Cowork for files, Code if you write software.
04Pin the app to your dock. You will use it more than you expect.
Module 02 · Leverage

Organizing your work and your knowledge.

One off conversations are useful. The leverage shows up when you stop starting from scratch. Projects, Artifacts, and Skills are the three tools that turn Claude into a system.

Projects

A Project is a dedicated workspace inside Claude with its own instructions, its own files, and its own conversation history. Use one Project per recurring lane of work: a customer, a service line, an ongoing initiative.

setup-project.txt
01In Claude, click Projects ▸ New Project.
02Name it after the lane of work, not the task. Example: "Butler Account".
03Paste a one paragraph brief into Project instructions.
Who the client is, how you write to them, what they care about.
04Upload reference files: master service agreement, brand voice
notes, past correspondence, anything Claude should know by default.
05From now on, every new conversation in this Project starts smart.
Where it pays offWhen a teammate joins a Project, they inherit the institutional context. No more onboarding conversations that start with "let me catch you up on this client."

Artifacts

An Artifact is a finished thing Claude builds in a side panel: a document, a one pager, an interactive calculator, a small web page. You can edit, download, and reuse it. It is how you turn a conversation into a deliverable.

  • Ask for a "one page brief" or "scoring rubric" or "interactive checklist" and Claude will spin one up.
  • Iterate by telling Claude what to change. The Artifact updates in place.
  • Share the link with a teammate or download as a file when you are done.

Skills

A Skill is a reusable instruction set Claude loads on demand. Anthropic ships skills for working with PDFs, spreadsheets, slide decks, and more. You can write your own, or have your coach write them, to capture how your firm wants specific work done.

skills-in-practice.md
# A Skill is just a folder with a SKILL.md file and any helpers.
# Claude reads the instructions when the task matches the skill description.
EXAMPLEA "submittal-review" skill that knows your spec format,
the questions you always ask, and the sign-off sheet template.
EXAMPLEA "weekly-update" skill that produces your status report
in the exact layout your owner wants every Friday.
Module 03 · Reach

Connecting to where work lives.

So far Claude has been working with what you paste in. The next step is connecting the tools where your real work lives, so Claude can pull the right context without you copying anything.

Connecting your tools

Connectors let Claude reach into apps you already use: Google Drive, Gmail, Calendar, HubSpot, QuickBooks, Slack, Notion, and many more. You authorize each connection once. Claude only uses it when the task asks for it.

connect.sh
01Open Settings ▸ Connectors in the Claude desktop app.
02Pick the tool you want Claude to reach: Gmail, Calendar, Drive, etc.
03Sign in with the same account you use at work. Approve the scopes.
04Now ask Claude something that crosses the connection. Examples:
# "Pull my last two emails with Wespac and summarize where we left off."
# "What is on my calendar tomorrow and what should I prep for?"
POLR tipStart with one connector. Use it for a week. Add the next one only when you hit a wall. You will be amazed how much Gmail plus Calendar alone changes your morning.

Enterprise search

Once a few connectors are live, you can ask Claude questions that span them. "Where did we land on pricing for the Suntec project?" Claude will search the right inbox thread, the right Drive folder, and the right Slack channel and bring you the answer with sources.

Treat it like having an assistant who can read everything you can read, just much faster.

Research mode

Research mode is for the deeper questions. You give Claude a topic, it goes out and reads broadly, and returns a structured brief with citations. Use it when the work justifies an actual report, not a quick reply.

  • "Who are the top three commercial GCs hiring superintendents in metro Phoenix right now, and what are they paying?"
  • "What does the new Maricopa County permitting workflow look like, and where do most projects get stuck?"
  • "Brief me on the AIA Arizona convention agenda and which sessions matter for an ops audience."
Module 04 · Application

Putting it all together.

The pieces are simple. The compound effect comes from picking one workflow, building it well, and then doing it again next week. A few patterns we see working in the field.

Use cases by role

Where Claude pays back its first hour, sorted by who is sitting at the keyboard. Pick the row that looks most like your week and start there.

01
Owner / Principal

Daily brief, decision memos, board prep

Market scans and executive summaries of long documents. The thing you wish a chief of staff did.

02
Operations

Submittal review, RFIs, weekly status

Schedule narratives, vendor follow-ups, the routine outbound that piles up.

03
Estimating / Precon

Bid summaries and scope comparisons

Qualification letters, takeoff sanity checks, anything that lives in long PDFs.

04
Project Management

Meeting minutes, action items, change orders

Turn a transcript into a clean PM artifact in under two minutes.

05
Marketing / BD

Case studies, proposals, follow-up sequences

LinkedIn posts that sound like you. Not like everyone else using AI.

06
Office / Admin

Inbox triage, calendar prep, policy drafts

Document formatting, handbook revisions, the work that gets pushed to Friday.

Other ways to work with Claude

Once your team is comfortable, the surface area opens up. A few directions worth knowing about, even if they are not your first move:

  • Voice and mobile. The Claude mobile app handles dictation well. Useful for windshield time and jobsite walks.
  • Browser use. Claude in Chrome can drive a browser for you on tasks like form filling and research. Treat it like a junior assistant: useful, supervised.
  • Custom agents. When a workflow is stable enough to repeat, POLR can package it as a dedicated agent that runs the same playbook every time.
Module 05 · Momentum

The next ninety days.

You have the foundation. The next 90 days is about turning these tools into one or two repeatable workflows your team uses every week.

Your week one homework

week-1.txt
DAY 1Install the Claude desktop app. Have one real conversation.
DAY 2Spin up a Project for your most active client.
DAY 3Connect Gmail and Calendar. Run a "what should I prep today" query.
DAY 4Take one recurring task you do every week. Document it for Claude.
DAY 5Run that task with Claude. Note where it sped you up. Note where it stuck.
DAY 6Share the wins with one teammate. Get them set up.
DAY 7Decide what you want to be doing differently in 30 days.

Going deeper

The next move

Want this rolled out across your team in 90 days?

POLR AI runs Coaching engagements that take a built environment firm from "we tried ChatGPT once" to a real working rhythm with Claude. Coaching, retainers, and custom development for AEC operators.

Book a discovery callSee our services

This guide mirrors the structure of Anthropic's Claude 101. POLR AI is an independent partner; we are not affiliated with Anthropic.