Basecamp holds your to-dos, message boards, and check-ins. It won’t do the thinking for you, though. You still have to turn a vague Slack message into a real ticket. You still have to read every thread to figure out what’s blocked. A Basecamp AI integration with HotBot handles that part.
Once you’re signed in as a member, you connect Basecamp inside HotBot and the assistant works with your Basecamp data directly. No copy-paste marathon. This guide covers the setup and five workflows — better tickets, sprint summaries, stakeholder updates, and spotting blocked work — with example prompts and the right model tier for each.
It’s AI project management with Basecamp that saves you time instead of adding another dashboard to babysit.
What You’ll Need
A short list before you start:
- A HotBot membership. Connectors are a members-only feature. You can sign in or subscribe here.
- An active Basecamp account with access to the projects you want to work with.
- A few real examples. A messy request, a project mid-sprint, a stakeholder who wants an update. Bring your actual work and the prompts land better.
- Five minutes to connect the app the first time.
No MCP server to host, no OAuth tokens to juggle, no command line. If you’ve tried wiring Basecamp into other chat tools through community MCP servers, you already know that’s not always a one-click setup.
Estimated Time: 10–15 minutes to connect and run your first workflow Difficulty Level: Beginner — if you can type a sentence, you can do this
Step 1: Sign In and Connect Basecamp Inside HotBot
HotBot connectors are members-only, so start by signing in. Go to the HotBot login page and sign in, or subscribe if you’re new. Pricing is straightforward: a free tier, then $7.95/week or $39.95/quarter for full access (details on the pricing page).
After you sign in, connect Basecamp from inside HotBot. The assistant then works with your Basecamp data directly, reading projects, to-do lists, and message boards so you don’t have to paste anything in.
I won’t walk you through screens I can’t see. Connect it from inside HotBot once you’re a member, and the rest of this guide assumes that connection is live. If you’re on the free tier and can’t connect yet, skip to the “Without the Connector” section below. You can still get most of this done.
Step 2: Turn Vague Requests Into Clear Tickets
This is the workflow I reach for most. Someone drops half a sentence in a message board — “the export thing is broken again” — and you’re supposed to make a ticket out of it.
With Basecamp connected, point HotBot at the thread and have it draft a real, structured to-do.
Example prompt:
Read the latest messages in the "Billing Portal" project.
Turn the export bug discussion into a clear Basecamp to-do with:
a one-line title, steps to reproduce, expected vs actual behavior,
and a suggested owner based on who's been replying.
Model tier: Use HotBot Chat for this. It’s fast, and ticket-writing is a well-defined task that doesn’t need deep reasoning. This is the kind of everyday job HotBot Chat is built for.
One thing I’ve noticed: the more raw context you give it, the less generic the ticket. Let it read the actual thread. Vague in, vague out.
Step 3: Summarize Sprint Status in One Shot
Instead of scrolling through to-do lists and check-ins to figure out where the sprint stands, ask HotBot to sweep the project and report back. This is where the connector earns its keep.
Example prompt:
Summarize the current sprint for the "Mobile Redesign" project.
Group by: done this week, in progress, not started, and blocked.
Flag anything overdue and note who owns it.
Keep it under 200 words.
Model tier: This is a job for HotBot Chat Plus. Summarizing across multiple lists and check-ins benefits from step-by-step thinking. Plus works through the structure instead of skimming, and when a sprint spans dozens of to-dos, that reasoning is the difference between a real status and a vague vibe.
The “group by status” instruction matters more than anything else in that prompt. Left to its own devices, the model hands you a wall of text. Give it buckets and you get a scannable report.
Step 4: Draft Stakeholder Updates People Actually Read
Project leads spend an absurd amount of time translating “what the team did” into “what the client cares about.” These are two different documents, and HotBot can bridge them.
Example prompt:
Using the "Website Launch" project's activity from the past two weeks,
draft a stakeholder update for a non-technical client.
Lead with progress and outcomes, not task names.
Include: what shipped, what's next, one risk, and no jargon.
Friendly but professional tone.
Model tier: For a routine weekly recap, Chat Plus is plenty. When the update is high-stakes — a board summary, a contract-renewal moment, a project that’s behind and needs honest framing without spooking anyone — move up to HotBot Chat Pro. Pro’s deeper reasoning and 1M-token context let it hold the whole project history and produce something more considered.
Most status updates read like a task list with dates. A good one tells a story. Ask for outcomes instead of activity and the difference shows up in the first draft.
Step 5: Spot Blocked and Stale Work Before It Bites You
Blocked work is sneaky. Nobody flags it. It sits there quietly until the deadline. This workflow has saved me from more than one awkward Monday.
Example prompt:
Scan the "Q3 Launch" project. Find to-dos that are:
overdue, assigned but untouched for over a week, or waiting on
someone else. For each, tell me what it's waiting on and who to nudge.
Model tier: HotBot Chat Pro for this one. Reasoning about dependencies — what’s waiting on what, and why — is deep work. Pro’s large context window means it can hold the full project state at once instead of losing the thread.
When a third-party model is the better pick
HotBot gives you 800+ models from every major provider under one subscription, and sometimes a specific third-party model just fits better. Writing a nuanced client email in a particular voice? Try a model known for prose. Reasoning through a tangled dependency graph? Try a top reasoning model. You don’t have to guess and commit — switch models mid-project and keep going. (These names identify the models available on HotBot; HotBot is an independent service, not affiliated with any of them.)
Without the Connector: The Free-Tier Method
No membership yet? You can still do all of this. It’s just a little more manual.
Copy the relevant Basecamp content — the message thread, the to-do list, the check-ins — and paste it straight into HotBot. Then use the same prompts from the steps above, minus the “read the project” part. So instead of “read the latest messages,” you’d paste the messages and say “turn this discussion into a clear ticket.”
It works well. The downsides are the copy-paste tax and the fact that you’re working from a snapshot instead of live data. For a lot of teams, that’s a fine way to test the waters before subscribing.
Common Issues
The summary feels generic. You didn’t give it enough context, or you didn’t tell it how to structure the output. Add “group by status,” “under 200 words,” or “for a non-technical audience.” Specificity fixes almost everything.
It’s missing recent activity. On the free-tier paste method, you’re working from whatever you pasted — it can’t see anything newer. Re-paste, or connect the app as a member for live data.
The wrong tone. Tell it. “Make it warmer.” “Cut the jargon.” “Shorter.” HotBot iterates fast, so treat the first draft as a draft.
It won’t let me connect Basecamp. Connectors are members-only. On the free tier, you’ll need to subscribe first, then connect it from inside HotBot.
A Quick Note on Limits and Privacy
Two caveats worth stating plainly. HotBot works with your Basecamp data when you ask it to, in a session you’re driving. It’s an assistant, not an autonomous agent watching your projects around the clock. If you need event-triggered automation — something firing the moment a to-do goes overdue — that’s a different category of tool.
Treat connected data thoughtfully. Only connect projects you’re comfortable having the assistant read, and review anything before it goes to a client or gets posted back.
What’s Next
Once you’ve run these five workflows a couple of times, start building your own. Save the prompts that work as templates. Try chaining them — a sprint summary that feeds straight into a stakeholder update. Test the same task across different models on HotBot and see which voice you prefer.
And if you’ve been reading all this from the free tier, sign in or subscribe and connect Basecamp. The live-data version is a different experience once you stop pasting.
FAQ
Do I need to be a member to connect Basecamp?
Yes. HotBot connectors are a members-only feature. You’ll need to sign in and subscribe, then connect Basecamp from inside HotBot — after that the assistant works with your Basecamp data directly.
Is HotBot an official Basecamp product?
No. HotBot is an independent AI chat service and isn’t affiliated with or endorsed by Basecamp or 37signals. The Basecamp connector simply lets HotBot work with your Basecamp data once you connect it.
What does HotBot cost?
There’s a free tier, and full access runs $7.95/week or $39.95/quarter. The connector features require a membership — you can compare options on the pricing page.
Which model should I use for Basecamp work?
Use HotBot Chat for fast everyday tasks like writing tickets, Chat Plus for step-by-step work like sprint summaries, and Chat Pro for deep reasoning like spotting blocked dependencies. You can also pick from 800+ third-party models when one fits a task better.
Can I use HotBot with Basecamp on the free tier?
Sort of. You can’t use the connector on the free tier, but you can paste Basecamp content directly into HotBot and use the same prompts. You’re just working from a snapshot instead of live project data.
Is this a ChatGPT alternative for Basecamp?
Yes — if you’re looking for a Basecamp ChatGPT alternative, HotBot gives you one subscription with access to 800+ models plus its own HotBot Chat, Chat Plus, and Chat Pro tiers, so you’re not locked into a single provider.
