Turning records into pages

Most of the useful information in a business is already in rows — customers in a spreadsheet, stock in an export, members in a database, properties in a listing. Rows are fine for storing things and poor for looking at them.

Hand that export to your AI and ask for one page per record, plus an index, and the whole thing becomes something you can walk around.

Why this suits the app particularly well

Your folders become the segments. A folder per region, per status, per account manager — click one and the view narrows to it.
Search reads the whole page, so you find a customer by anything written on their page, not just the name you filed it under. See Finding a page.
Gallery View shows them as cards, which is genuinely useful for anything with a photo — properties, products, people. See Gallery View.
Links join related records, and the app tracks them in both directions, so a customer page can point at their orders and the order pages point back.
It is portable. A folder of record pages opens on any Mac, in any browser, with no database behind it and no software to install — which makes it a genuinely good way to hand a set of records to somebody.

Ask for it like this

Sample prompt

Read [the CSV / spreadsheet / export] at [path]. For every row, write one self-contained HTML page in [folder], named after [the record's name or ID]. Each page should lead with the name and the two or three things I most need to know, then the rest of the fields laid out so they are readable rather than crammed into a table. Then write an index page at the top of that folder listing every record with a one-line summary and a relative link, grouped by [segment / region / status]. Link related records to each other where the data connects them. Use the colors from my Showspace, keep every page self-contained with no external files, and make them read on a phone as well as a desktop. Before you start, tell me how many records there are and show me one finished page so I can check the layout before you write the rest.

Change the parts in brackets.

The last line matters more than it looks. Ask to see one page before it writes four hundred — fixing the layout once is a minute, and fixing it afterwards is a re-run.

How many records is too many

The app indexes up to 500 pages in a Showspace. Past that, the extra pages are still perfectly real on your disk and still open normally, but they will not appear in the sidebar, the gallery or search — so a 2,000-row export written out one page per row would leave most of itself invisible here.

Showspace health tells you where you stand: it reports the file count against the cap, so you find this out on purpose rather than by noticing something missing.

Three ways round it, in the order most people want them:

One page per group rather than per row. A page per customer with all their orders on it beats a page per order, and reads better anyway.
Only what is live. Active customers, this year's stock, open cases. The archive can stay in the spreadsheet where it came from.
A Showspace per set. Customers in one, inventory in another. Switching between them is one click, and your agent can switch by name. See Switching between Showspaces.

Keeping it current

Export again and ask your agent to rebuild the page. It overwrites what changed, and the app notices within moments — no refreshing and no re-importing. See Renaming, moving and deleting for what happens when a record disappears.

If the data changes often, stop asking an agent each time. Have it write you a small script that reads the spreadsheet and rewrites the page, then run that script on a schedule. Your Mac has a scheduler built in, and several agents will set one up for you. From then on the page is current before you open it, and nobody has to remember anything.

The division worth keeping is this: the agent builds and changes the page; a script refreshes the numbers. Adding a column, changing the layout, deciding what belongs at the top — that is judgment, and it wants a conversation. Pulling today's figures into a shape you already settled is mechanics, and it wants the same answer every single time. A script gives you that. A model asked to rebuild the page hourly will eventually reword one of your notes, re-sort a column, or quietly drop a field, and you will not notice for a week.

Or let something else hold the schedule. A cloud agent such as GrokBot can do the same job without your Mac being involved at all: it reads the sheet and rewrites the page in your Drive on its own, so the records are current when you open the app rather than when you remember to refresh them. See Which AI works with lite.computer.

Set up that way the page is genuinely live: the spreadsheet is the source, the script is the pipe, and the page on your second screen is the current view of it. That is the same pattern behind a dashboard that keeps itself up to date — records are simply a spreadsheet you would rather read. See Which AI works with lite.computer for the agents that can run on a schedule, and Showspace health for catching it if a rebuild ever goes wrong.

Where to keep real customer data

Records about real people deserve a moment's thought about location, and it is the same decision as any Showspace — just with the stakes clearer.

The pages sit in the folder you chose, so that folder decides who can reach them: local disk keeps them on this Mac, a shared Drive folder reaches whoever the folder is shared with. Worth knowing either way: an AI agent that reads the pages sends what it reads to whichever company makes it, so keeping the folder off the cloud is not the same as nothing leaving your Mac. Where to put your Showspace covers the trade-offs.

Nothing here reaches us. The app has no account, no server of ours, and nothing to sign in to.