For IT Consultants ·
What you'll accomplish
You just finished a network walkthrough at a new client and you have a page of scattered bullet points: aging switches, no offsite backup, three admin accounts without MFA. Turning that into a report a business owner will actually read normally eats a few hours. Claude can take those bullets and return a structured draft with a current-state summary, ranked risks, and recommendations, so your afternoon goes to editing and verifying instead of writing from a blank page.
What you'll need
Go to claude.ai and sign up with a work email, or log in if you already have an account. The free plan is enough for this task since file upload limits are the same on free and paid plans, only the number of messages per day changes.
What you should see: A chat window with a message box at the bottom and a "+" icon to its left.
Troubleshooting: If you already use Claude for personal projects, consider a separate account or workspace for client work so client files stay out of your personal chat history.
Before uploading anything, scrub it for real identifiers. Open your notes and swap real hostnames, IP ranges, and any admin usernames or passwords for generic labels like "Server-A" or "Firewall-1." Save this cleaned version as a plain text file, spreadsheet, or PDF.
What you should see: A findings document that reads clearly to a human but reveals nothing that would let a stranger log into the client's network.
Troubleshooting: If you're not sure whether a detail counts as sensitive, leave it out. You can always add specifics back into the final report yourself after Claude drafts the structure.
Click the "+" icon in the lower-left corner of the message box and choose "Add files or photos," or drag the file directly onto the chat window. Claude accepts PDF, DOCX, CSV, TXT, and several other common formats.
What you should see: A small file preview appears above the message box once the upload finishes.
Troubleshooting: Free and paid plans both cap uploads around 30MB per conversation. A findings list is almost always well under that, but if a scan report is huge, trim it to the sections you actually need summarized.
Type a prompt naming the report sections your practice uses. If you don't have a standard structure yet, ask Claude to propose one built around current state, risks, and recommendations, and keep that structure for future clients.
What you should see: Claude returns a full draft organized under clear headings, usually within a minute.
Read through the "Risks" or "Key Findings" section first. Claude will often rank items by severity based on what you described, but it has no way to know your client's actual risk tolerance or budget constraints.
What you should see: A list of findings, each with a short explanation of why it matters.
Troubleshooting: If the ranking feels off (a minor issue at the top, a serious one buried), reorder it yourself. You know the client and the stakes better than the draft does.
Once you've read the first draft, ask Claude to adjust tone, trim length, or add a section you noticed was missing, all in the same conversation so it keeps the earlier context.
What you should see: An updated draft that keeps the structure but reflects your edit request.
Copy the finished text into your practice's Word or Google Docs template, add your logo and any diagrams, and do a final read for tone before sending.
What you should see: A client-ready document that still needs your name and any diagrams added, since Claude only works with text and the files you gave it.
First draft from bullet findings:
Here are my raw findings from a technology assessment at [client type,
e.g., "a 15-person law firm"]. Draft a report with Current State, Key
Risks, and Recommendations sections. Rank risks by business impact,
not technical severity.
Executive summary only:
Summarize this assessment's key risks and recommendations in one
paragraph a non-technical business owner can read in under a minute.
Prioritization by cost tier:
Group these recommendations into three tiers: address in the next 30
days, address this quarter, and monitor for now. Don't include dollar
figures, just note the relative scope of effort for each tier.
Comparison to last year:
Here is this year's assessment and last year's summary (both attached).
Note what improved, what got worse, and what's unchanged.