One staff database, eight locations
Maribel manages a family practice spread across eight clinics and about 300 employees. Her core use of xTiles is exactly the kind of thing a scattered organization needs and rarely has: a single staff database that every department can see into, instead of eight locations each keeping their own version of who's who and what's current.
Alongside that, she runs a separate project just for her own assistants and team — assigning tasks and tracking progress without it getting tangled up in the org-wide staff data. Two different jobs, two different projects, one tool.
Worth noting for anyone managing a team of any size: a lot of her staff use the free tier because the practice doesn't cover a subscription for everyone, and that's fine — "that's okay if people use it and spread the word, that's fine for us," as we put it on the call. A shared staff database doesn't require every viewer to be a paying seat to be worth having.
Connecting Claude before exploring it
Maribel's Claude connection happened the way most people's actually do: she read the rollout email, connected it right away, and — busy running eight clinics — hadn't yet had time to dig into what it could do. That's a completely normal place to be, and it's worth walking through what's on the other side of that connection once there's a spare hour to look.
What the connection unlocks once you start using it
The clearest way to show it is a real daily setup already running elsewhere on the team. Claude's routines — not one-off tasks, but a schedule — can run automatically before a workday even starts. Set one for 15 minutes before a 9am start, and by the time the laptop opens, several tiles are already sitting on the daily page:
- Slack, summarized — active threads and channel activity, with direct links back to each one, so nothing has to be re-found by scrolling.
- Yesterday, recapped — a short readback of the previous day, useful even on a quiet Sunday when there's genuinely not much to report.
- Inbox, reviewed and archived — a pass over the last 24 hours of email, summarized into a tile with a link to the original, and the source emails archived once they're accounted for.
One more workflow is worth calling out because it's a little unusual: asking Claude to review the whole day — calendar, email, Slack, xTiles tasks — and log completed tasks for things that got done but never made it onto a list in the first place. There wasn't time to type it up in the moment; the task exists retroactively, already checked off. It's a small thing, but ending the day seeing real work reflected back — instead of an empty list that undersells what actually happened — is its own kind of payoff. A one-paragraph daily summary closes the loop, working like a lightweight journal; ask for the same thing at the end of a week and it rolls up into a review of where the time actually went.
The three-buckets way of thinking about it
It helps to separate what's doing what. Bucket one is the tools already in daily use — inbox, calendar, Slack, meeting notes, task managers. Bucket two is Claude, which can read from and write to all of them. Bucket three is xTiles: the visual surface where what Claude finds actually lands, instead of staying buried in five different apps' histories.
Put together, xTiles ends up working like a dashboard — a control panel showing what Claude already pulled together, without the manual effort of assembling it by hand every morning.
Where this is headed for a staff database specifically
For an organization built on a shared database the way Maribel's is, the most relevant thing coming isn't a new daily-brief workflow — it's Claude gaining direct access to xTiles collections and databases, not just tasks and pages. That means statuses updating automatically instead of by hand, across a database sized for hundreds of staff records, and it's the piece we'd call the real game-changer for business use once it lands. Better auto-generated layouts and outlines, and more connectors beyond Claude and ChatGPT (Zapier among them), are on the same roadmap.
That's the direction the integration is heading — mapped directly onto an 8-location staff database rather than a single person's inbox.
Context flows both ways — even for personal use
Maribel is also a part-time student, and she'd already been using browser extensions to copy class notes into an xTiles project — "everything that I'm reading in my class, I'm copying, pasting everything." The natural next step once Claude is actually connected: point it at that same project as context, and ask it to help her prepare for a test, without retyping or re-explaining the material first.
That's the same integration working in reverse. It's not only about Claude sending a summary into xTiles — an existing xTiles project can serve as context for Claude, so a page of notes, a workspace, or a planner becomes something you point an assistant at rather than something you retype into a chat window.