Many Sites, One Workspace: Running a Portfolio Built on Relationships

A portfolio in this town is rarely a list of companies. It is a list of people — a producer, the engineer he books, the room they both work out of — and every one of them has a website. The work gets done. What goes missing is any record of which site it was done for.

Nobody decided to run eleven properties. They arrived one at a time, each attached to somebody you already knew, and by the third year only the person who signed up for each of them can explain the set.

The list is people, and the websites came afterward

Look at how a set of properties accumulates here. A producer has his own domain because his credits are his résumé. The engineer he books most weeks has a separate one, for the same reason and with a different list of credits. The studio they record in has a third, run by whoever answers the phone. Three sites, one working relationship, no corporate structure connecting any of them.

An artist keeps a personal domain — tour dates, mailing list, merch — while the label maintains its own page for the same records. They serve different readers, rank for overlapping phrases, and nobody ever wrote down which one is supposed to win. Downstream, a venue on the east side has a restaurant in the same building and an event brand it books private parties under: three domains, two people, all of it run between soundchecks.

The point is not that this is disorganized. The organizing principle is a relationship rather than a plan, and relationships do not produce the tidy hierarchy most tools assume. There is no parent company — only a producer who knows a caterer who knows a venue manager, and eleven domains hanging off those introductions.

"Which site was that for?" and why nobody knows

The failure is not dramatic. Reports get produced, links get placed, pages get rewritten. What degrades is attribution — the ability to say, six weeks later, which property a piece of work was performed against and on whose instruction.

It degrades because the record lives in the wrong places. A decision is made in a text message; a keyword list arrives attached to an email; somebody approves a page change by phone from a parking lot. None of it is written against the property it concerns, so reconstructing it means reconstructing a conversation.

In a portfolio built by relationship this compounds faster than in a corporate group: no shared calendar, no shared drive, frequently no shared email domain. The only thing every property has in common is you.

A feed that writes itself, project by project

The fix is structural, not behavioral: give each property its own running record and let the system write most of it unprompted.

Chronology is the underrated part. When a ranking moves, the useful question is what else happened that week, and a feed answers it by scrolling — eleven properties, eleven independent histories rather than one blurred one.

Questions answered against your own figures, not the open web

A general-purpose chatbot can describe SEO. It cannot tell you what happened to the venue's restaurant site in the last twenty-eight days, because it has never seen the data. The assistant here is wired to the project itself, which changes what is worth asking.

The mechanism explains the answers you get. A router model reads each question and decides which data blocks are relevant — Search Console, results-page data, campaign state, custom material — then loads between zero and three of them. A question about how something works loads nothing. One about last month's clicks loads the analytics block. One comparing your position against a competitor's may load three.

Answers stream token by token, so a long reply starts arriving immediately rather than after a pause. Up to twenty messages of history are retained, so follow-ups work — you can say "and the restaurant site?" and be understood without restating the question.

• Ask about one property at a time. The assistant is bound to a project; comparisons across the portfolio belong in the dashboards and exports.
• Batch work is accepted as lists. Keyword and URL lists can be handed over in bulk, which suits a venue adding a season of pages at once.
• Twenty messages is working memory, not an archive. Anything that matters later should become a to-do or a note in the feed, where it persists.

Everything it produces lands in the same stream as the automated entries, so an assistant that answers from the project's own record doubles as documentation.

All, Links, Files, To-do — and the state most task lists refuse to have

A feed that captures everything becomes unreadable by month four unless it can be narrowed. Four filters do that: All shows the complete history, Links shows placements, Files shows what was uploaded or generated, To-do shows open commitments.

The to-do states are the more interesting decision: active, deferred or dismissed. Most tools offer done and not-done, which forces every "we decided not to bother" into either a permanent open item or a deletion that erases the reasoning.

Dismissed is the state that pays for itself. When an owner asks in October why nothing came of a June suggestion, the answer is visible: raised, declined, and the decision sits in that property's timeline rather than in somebody's recollection.

Full-text search runs across every message in the record, which is what turns "which site was that for?" into a query. Search a donor domain, a surname or a phrase from a page, and the property announces itself with the date attached.

The web person who also works for three of your clients

Here is a situation nobody writes into a security policy. The freelancer who maintains a studio's site also builds for two other studios and the venue down the street. That is normal, it is how small markets function, and all of those clients know it.

What they do not want is for that person to see each other's numbers — not from suspicion, but because a professional in a community this size has to be able to say truthfully that they never saw a competitor's traffic. The access controls protect the freelancer as much as the client.

The alternative most portfolios run on is a login passed around by text message, which cannot be revoked from one person without locking out everyone. Being able to grant one site and take it back the same afternoon makes the boundary enforceable rather than aspirational.

Tag by person and by property type, and keep the list flat

Site tags work as a global filter: apply one and every view narrows to the properties carrying it. That makes the tag vocabulary the most consequential decision in setting a portfolio up, and the usual instinct — build a hierarchy — is the wrong one.

A hierarchy assumes a property belongs to exactly one branch. These do not. The venue's restaurant belongs to the venue commercially, to hospitality by category, and to two named owners by relationship; forced into a tree it lands in one place and goes invisible from the other two. Flat tags applied several at a time describe it from every angle that matters.

• Never encode structure into a tag name. A tag reading "venue-restaurant-east" is a tree wearing a flat label. Apply "venue" and "restaurant" separately and let the combination do the work.
• Tag the person even when they are not the client. An engineer who does not pay you still routes referrals, and one day you will want to see everything connected to him.
• Retag when a relationship changes, not when a company does. Here the relationship is the durable object; companies get renamed around it.

Exports, charts, and a week across eleven properties

Most of the portfolio never logs in. A producer wants two numbers and a sentence; a venue partner wants a page he can forward to his co-owner. Reporting exists for people who will never open the panel.

Exports come in two sizes for two purposes. CSV and JSON run to 10,000 rows — the analyst's format, sorted and read as language. PDF is capped at 250 rows and rendered server-side, and that cap is a useful constraint: it forces you to choose what matters before sending. The report builder carries your own logo and colors, so the same figures go out under your branding to six unrelated owners.

The visualizations do the interpretive work. Time series show the shape of a trend rather than its endpoint; metric cards carry the headline figures; tables filter and sort at fifty to two hundred rows a page; sparklines put a direction beside a number, which is usually all a busy owner reads. Heat maps for countries and devices matter more than they sound — out-of-state rows in a tourism-adjacent business generally mean planning, not booking.

A realistic week: Monday, read the health flags across every property and let the unflagged ones wait. Tuesday, work the two that flagged, asking the assistant what changed and reading the answer against the feed. Wednesday, clear the to-do lists — active items done, seasonal ones deferred, bad ideas dismissed with a reason. Thursday, generate the PDFs. Friday, review the access list and tag anything new.

Where the term list has to be chosen rather than inferred, FullSEO at $500 per month per domain adds manual keyword selection with automatic fallback, placement aimed at a Domain Authority target, and a human-review mode before on-site changes ship, backed by a team of specialists, developers and writers. On a portfolio this shape the common arrangement is the second tier on the one or two properties carrying the revenue and the first tier everywhere else. Campaign automation kept beside the analytics makes that mixture manageable from one screen, and a report builder with your own logo and colors lets it be explained to six owners without six tools.

Now the part the software does not do. It will not tell you which of eleven properties deserves next month's attention — that is a judgment about revenue, relationships and who is currently unhappy, none of which appear in a dashboard. It will show that a number moved; it will not establish why, because the cause is usually offline and often human. It cannot set a goal, since a goal is a decision about what the business is for. And it will not talk to the owner: somebody has to sit across from the producer and explain, in his vocabulary, what the report means and what it does not.

What the workspace removes is the overhead around those four things — the reconstruction, the credential hunting, the spreadsheet in one person's downloads folder. We write about multi-property portfolios on our blog, and setting them up is part of our services for studios, venues and hospitality groups across Middle Tennessee. Link your Google account and load every property you already administer — the first useful surprise is usually the count.

Questions that come up when the portfolio is being set up