Portfolio at a Glance. A real analysis of a university's public-facing web portfolio
Harvest shows you every site your institution runs and what connects them: shared platforms, content patterns, infrastructure clusters.
IT wants to provide secure, reliable infrastructure. Communications wants consistent branding across sites they don't control. Units want their staff focused on mission, not on wrangling their CMS. Everyone's trying to do the right thing. But without a view across the whole portfolio, they're all doing it alone.
Your communications staff are troubleshooting CMS issues instead of doing communications work. Your web directors are firefighting instead of providing strategic support. And every time someone leaves, the training investment walks out the door.
Institutions typically run 3–11 different CMS platforms. No way to enforce accessibility, brand, or security standards across that fragmentation. Hundreds of sites on the same platform, still duplicating each other's work.
Six CMSes means six sets of licenses, hosting, security patches, and support contracts. We can see those costs. The bigger cost is training and supporting the people managing the sites.
Harvest understands your web presence as a portfolio of semi-autonomous sites representing one institution. It detects patterns that only become visible when you look across the whole.
Detect clusters of sites running the same CMS, codebase, or theme. When 40 sites share a platform, fixing once benefits all of them — but only if you see the pattern.
Faculty bios, program descriptions, and institutional data appear across dozens of sites. Harvest identifies where content is shared, duplicated, or inconsistent across the portfolio.
People, programs, courses, events, news — Harvest detects these structured content types across your portfolio and maps them to give you a picture of what your institution is actually publishing.
Harvest produces artifacts you can hand to a provost, bring to a governance committee, or use to scope a vendor engagement.
Harvest crawls your portfolio and produces a structured inventory: every site mapped to its platform, grouped into infrastructure clusters where sites share a CMS, codebase, or theme. You see which platforms you're running, how many sites run on each, and which sites operate outside any shared infrastructure entirely.
Beyond platforms, Harvest tracks contributor capacity (which sites show active maintenance and which have gone dark) and content distribution (where the same content types appear across sites, and where content is shared, duplicated, or inconsistent).
Every aggregate finding is backed by the actual site-level data. "34 sites operate outside any shared infrastructure cluster" links to those 34 sites, with their platforms, page counts, and maintenance status. The Alignment Snapshot Report synthesizes this into an executive-ready document with conditional strategic questions generated from your actual data. But the data is always there underneath.
Harvest detects structured content types across your entire portfolio: people directories, event calendars, course catalogs, program listings, news feeds, policies.
This gives you a content map at the institutional level. Which platforms are publishing people content? Where do event listings appear? Are program descriptions maintained in one place or duplicated across twelve? These patterns are invisible when you look at sites one at a time.
Search for specific content across your entire web presence. Harvest finds matching pages, then uses AI to classify each result according to your governance objective. The question isn't "does this page mention the term?" It's "does this page need substantive revision, a minor edit, or no action?"
The AI understands context. A COVID policy search finds the term on an outdated Student Health Services page (revise) and in a faculty publication citation (no action) and classifies them differently. Of 200 keyword matches, only 6 need revision. That's the difference between a six-page work list and a 200-row spreadsheet of false positives.
Every result includes a per-page rationale explaining the classification, with filter controls and CSV export so your team can use the output directly as a work-tracking spreadsheet.
A snapshot tells you what you have. A change report tells you what's happening. Each crawl compares against the previous one and produces a portfolio-level diff: new pages, changed pages, newly discovered sites, and sites that stopped responding.
The report breaks this down by platform, so you see that your main WordPress instance had 1,005 new pages and 843 changed, while your Omeka digital collections platform had a 46% change rate across 10 sites. That's the kind of signal that tells you where activity is concentrated and where governance attention is needed. It also tracks changes in flags like accessibility issues, so you can see whether problems are being addressed or spreading across the portfolio.
Want to see the full picture? Here's a real analysis — anonymized from a public university with 496 sites across 14 platforms.
Download Sample Report (PDF)Harvest is not a security scanner, accessibility auditor, or SEO tool. Those are page-level concerns, and good tools already exist for them. We pick up on those things during analysis, but the product is the portfolio view.
"Your institution has 496 sites across 14 platforms. Here's what that means for governance, cost, and risk." Nobody else gives you that sentence.
And without it, every consolidation project starts from scratch. The cycle is familiar: mandate a platform, fight the politics for two years, end up with partial adoption and a new layer of fragmentation. Harvest starts from where you actually are.
Harvest serves the people hired to see across IT, marketing, and unit operations — and the firms they work with.
You're responsible for standards, support, and visibility across a distributed portfolio. Harvest gives you the baseline you need to provide support without imposing control.
You need to answer audit questions about your digital footprint, track EOL software across the portfolio, and understand the real platform sprawl. Harvest maps it.
If you respond to RFPs for web portfolio reviews, CMS migrations, or digital strategy — Harvest can accelerate your discovery phase from months to days.
Harvest works from the outside in. No agents to install, no access to grant. If it's on the public web, we can see it.
Give us your institution's root domain. Harvest discovers every site in the portfolio — subdomains, vanity domains, microsites — by crawling outward from the root.
Each site gets fingerprinted: CMS platform, theme or codebase, content types, page volume. Sites sharing infrastructure get grouped into clusters. Tiered crawling keeps the process fast without hammering your servers.
A structured inventory of your entire web presence — platform clusters, content distribution patterns, governance gaps — backed by the site-level data underneath every finding.
We're working with early partners to shape pricing that reflects the value Harvest delivers at different portfolio sizes. If you're interested in being part of that conversation, let's talk.
Let's TalkTiseran is led by Danny Collier, who spent 17 years working in higher education digital strategy and web governance. That experience spans the full range of multi-site complexity — from inherited messes to intentional shared platforms.
Harvest exists because the tools available to web governance leaders don't match the problem they face. Page-level scanners can't see across a portfolio. Spreadsheets can't keep up. And mandated consolidation doesn't work in institutions where authority is distributed.
Harvest is the first step in a larger vision — understand what you have, then build the governance and delivery infrastructure to manage it well. But Harvest delivers value on its own. You don't need to commit to the full arc to benefit from knowing what's actually out there.
We're talking with institutional web leaders and the firms that serve them. If that's you, let's have a conversation.
Book a Conversation