Capacity planning, now in your chat.
Loomsight plugs directly into the AI assistants you already use—like Claude and ChatGPT. Instead of digging through software, just ask your AI to staff a project, check the bench, or flag an overloaded week, and get the exact calendar details instantly.
Every resource planner assumes you’ll come to it — another tab, another login, another board somebody has to remember to update. So the schedule is only ever as true as the last person who felt like opening it.
Loomsight goes the other way: it lives inside the assistant you’re already talking to. Ask who’s free in October, book six weeks of an art director, move a project two weeks left — in a sentence, and the calendar comes back drawn.
You ask. It writes. The board stays true.
Nothing new to log into
Loomsight is an MCP server, not another dashboard somebody has to remember to open. Connect it once to Claude, ChatGPT, or anything else that speaks MCP — it's OAuth end to end, so there's no API key to paste and no token to rotate.
The calendar draws itself in the chat
Ask for the schedule and you get the schedule, not a wall of JSON. The capacity calendar is an MCP app: your assistant renders the real board in a sandboxed frame and you page the weeks from inside the reply. A host that can't draw it still gets the whole calendar as data.
Capacity is your roster, not a number you maintain
A title's bench is however many people carry it. Hire a second art director and October has two; nobody edits a capacity field, because there is no capacity field to fall out of date.
Proposals count at the odds you gave them
Work you haven't won is weighted by its win probability, so a long shot doesn't read as unavailable. Loomsight also names the opposite case: the week that only looks safe because the proposals sitting in it are discounted.
Oversold weeks arrive as a run, not a rash
Consecutive weeks where a title is asked for more people than hold it are gathered into one conflict — which title, from when to when, and how short. A bench that's short for a month is one thing to solve, not four.
Staffing in three records that stack
A project role says which role the work draws on, an allocation is one stretch of days at one rate, and an assignment names the person. Shortlist someone, put them on the role, confirm it — nothing is given up on the way up, and reshaping the dates never takes anyone off the job.
A whole roster in one call
Every tool takes batches rather than one record at a time, and people can carry a photograph by URL — Loomsight fetches it, crops it square, and re-hosts it privately. “Read our team page and set the studio up” is a single call; everyone without a photo is drawn as initials on a colour off their name.
Nothing is deleted, everything is signed
Archiving is what happens instead of deleting: the record stays, the year of work booked against it stays, and restoring brings it back under the same id. Every edit is written down with the connection that made it, and can be reverted.
Consent you can read in five seconds
Eight scopes — one read and one write per subject area — granted to the organizations you pick and nothing else. See every connection and when it was last used, and cut one off on its next call rather than whenever its token would have expired.
From nothing to a live resourcing plan, in one conversation.
Connect it once
Add Loomsight to your assistant as an MCP server and approve it. You choose which organizations it reaches and what it may do — read the roster but not rewrite it, book staffing but not archive projects. It shows up beside your other connectors and stays there.
projects:read · people:read · staffing:write — and nothing you didn't grant.
Say what you need
“Who's free in October?” “Put Priya on the rebrand for six weeks at half time.” “We just won Lumen — does it fit?” Loomsight reads the schedule, writes the records, and answers in the same breath. Batches, not one row at a time.
“Book an art director on Atlas from the 6th, 0.5 FTE.”
Read the same board anywhere
The calendar your assistant draws and the one the web app draws are the same calendar off the same numbers — they cannot drift into disagreeing. Bring the rest of the team into the app; nobody has to adopt an assistant to see the plan.
Chat, browser, or structured output — one model behind all three.
Simple pricing that scales with your studio.
Free for your first 10 users. After that, pay $5 per staffed user per month — unstaffed accounts are always free.
Free
For small teams getting off spreadsheets.
- Up to 10 users
- Unlimited projects, people & roles
- MCP server & the capacity calendar app
- Capacity, conflicts & win-weighted proposals
- Email support
Team
For growing agencies running multiple teams.
- Everything in Free
- Unlimited users
- Google sign-in & hosted team photos
- Full edit history & one-click revert
- Per-organization connection scoping
- Priority support
Enterprise
For holding groups & multi-studio networks.
- Everything in Team
- Multiple organizations under one login
- SSO & advanced permissions
- Dedicated onboarding
Questions, answered.
Ask your assistant who’s free in October.
Tell us about your team and we’ll connect it to your assistant with your own projects and people in it.