A Working Session for StudentBridge, by SoluteLabs
Tailor at scale.
How AI can help StudentBridge personalize, adapt, and decide faster, without changing the bet that already works.
Aim for the hour
2-3
AI ideas worth exploring together
A shared view on which one might be most useful to look at first
An open door for the next conversation
Working session
A practical hour, three pillars, nine ideas on the table. The intent is to leave with a short list worth piloting, picked together.
Section 01 / Why we are here
What this hour delivers.
One question, three areas, one hour. The document is built backwards from a single outcome. Leave with two or three use cases worth piloting, and if one looks promising, scope it from there.
What this hour covers
- Personalization at scale. Tailoring student journeys, landing pages, emails, and follow-ups based on profile, intent, program interest, and engagement signals.
- Faster content adaptation. Where AI can help your team repurpose core content into personalized versions without sacrificing brand or quality.
- Decision acceleration. Identifying where prospects drop off, what content performs, and where automation can help admissions and marketing teams respond faster.
- The outcome. Leave with two or three practical AI use cases worth testing, and if something looks promising, scope a small pilot from there.
Two SoluteLabs engagements are useful conceptual anchors for what we will discuss today. Investment Analyst, a conversational voice and text AI agent that recommends learning content paired with AI search for discoverability. Ecal, an AI-driven onboarding flow that conversationally collects user information to improve onboarding. Both patterns map naturally onto StudentBridge surfaces.
Section 02 / What StudentBridge already wins
Bet on video.
Gen Z spends three hours a day on short-form video. The enrollment funnel is built on video, virtual tours, and 1:1 engagement at scale. 250+ colleges trust the result. The work below extends that bet rather than challenging it.
| Product | What it does today |
| VisiTOUR | Virtual and self-guided campus tours. Visitors personalize routes by interest. Reported 34% lift in tour-to-lead conversion. Embeds from homepage to CRM with no friction. |
| Video Viewbook | Digital storytelling that replaces the traditional brochure. Expert-produced. Customizable per institution. |
| Amplify · StudentSync | 1:1 SMS and email at scale. Dynamic mobile content. Slate CRM sync. |
| On-Demand Events | Live and recorded open houses, admitted-student days, major-specific sessions. 24/7 access. |
| Creative Services | Hybrid production. Full-service to self-production. Explicitly built for teams that are stretched thin. |
Three capabilities power the entire portfolio. Personalization. High-volume content production. Behavioral data capture at every step. These are the three things modern AI is best at. The gap between what StudentBridge is built on and where AI is missing on the surface is the opening for this hour.
Section 03 / The three pillars
The three pillars.
Three columns. Every AI idea below sits in one of them.
01
Pillar one
Attract MORE
Personalization at scale
Capture richer signal at the front door, then tailor every downstream surface (tour route, viewbook cut, SMS cadence, event invite) without growing the team. Today's checkbox UX produces shallow tags. Conversation produces structured intent.
02
Pillar two
Amaze MORE
Faster content adaptation core bet
Repurpose the content you already produce into persona-specific cuts, languages, and formats. Authentic footage stays real. AI is the editor, the dubber, the narrator, and the sequencer. Never the cinematographer.
03
Pillar three
Achieve MORE
Decision acceleration
Two decisions. The prospect's (apply, visit, deposit) and the admissions team's (which leads to chase, what content to promote, when to intervene). AI shortens the time between question and action on both sides.
Section 04 / Where AI fits
Nine ideas. Three worth piloting first.
Nine AI use cases that fit the StudentBridge product surface. Three compose into one loop and are worth piloting first. The other six are extensions for a later wave. All sit inside the enrollment funnel, between first inquiry and deposit.
| # |
Use case |
Product |
Pillar served |
Focus today |
| 1 | Conversational intake on VisiTOURReplace static interest tags with a 60-second AI chat. Captures structured signal at the front door so every downstream personalization gets sharper. | VisiTOUR | Personalization | Pilot |
| 2 | Persona-cut Video ViewbooksAI re-sequences existing footage into persona-specific 90-second cuts. Each visitor sees a viewbook tuned to them, no new shoots. | Video Viewbook | Content adaptation | Pilot |
| 3 | Weekly AI funnel briefingsMonday morning brief per institution. Where prospects dropped, what content worked, what to do this week. Replaces dashboard mining with action lists. | Cross-product analytics | Decision acceleration | Pilot |
| 4 | Auto-recap reels from On-Demand EventsLong recorded events into 60-second highlight cuts and program-specific recaps. Squeezes more value from content already produced. | On-Demand Events | Content adaptation | Extension |
| 5 | Multilingual auto-dubbing of viewbooksAI dubs existing English viewbooks into target languages with preserved voice. Opens international recruiting without re-shooting. | Video Viewbook | Content adaptation | Later |
| 6 | AI-generated micro landing pages per inquiryWithin 30 seconds of an inquiry, AI assembles a uniquely composed landing page from existing content blocks. Drops bounce rates on every campaign. | Amplify + Viewbook | Personalization | Later |
| 7 | Dynamic SMS and email copy in AmplifyOne campaign brief, thousands of generated variants tuned to each recipient's profile. Lifts open and reply rates measurably. | Amplify | Personalization | Later |
| 8 | Generative campus map narrationAI narrator tells a different 30-second story at each tour stop per visitor persona. No re-shoots when buildings or menus change. | VisiTOUR | Content adaptation | Later |
| 9 | Yield prediction with intervention draftsML predicts which admits are most at risk of melting and surfaces personalized outreach drafts ready for counselor review. | Amplify + analytics | Decision acceleration | Later |
A loop, not a list
Use Cases 1, 2, and 3 compose. One captures the signal. Two uses the signal to personalize content. Three uses the signal to direct human action. Three use cases, one story, one customer journey. The other six are extensions for a later wave.
Section 05 / Use Case 1
Conversational intake on VisiTOUR.
Replace the interest checkboxes at the top of VisiTOUR with a 60-second conversation. Same downstream personalization engine. Five times the usable signal per visitor. Direct map of the Ecal pattern you have already seen.
5.1 The problem
Today VisiTOUR opens with tappable interest tags. A high-intent prospect who is into tennis and marine biology with a first-generation status and a cost concern gets the same checkbox UX as a casual browser. Most visitors leave anonymous. The depth of signal caps the depth of personalization downstream.
5.2 What AI does
A conversational widget, text-first, voice optional. An LLM extracts structured fields in the background. Program interests, extracurriculars, persona (first-gen, transfer, adult, parent), concerns (cost, distance, safety), intent stage (browsing, comparing, ready). Those fields feed the existing personalization engine. Every downstream surface gets sharper for free.
5.3 Who feels it
| Student | Feels heard from second one. Not surveyed. |
| Parent | Separate intake track surfaces the parent question set early. Cost, safety, outcomes, aid. |
| Admissions counselor | Inherits a structured profile instead of a tag list. Higher quality follow-up in less time. |
| StudentBridge | Every product (Viewbook, Amplify, Events) gets better inputs the moment intake ships. |
5.4 Pilot shape · 6 to 8 weeks
- One partner institution. Embed the widget on their VisiTOUR landing. Weeks 1-2
- Define the field schema with their admissions team. Connect to existing personalization engine. Weeks 2-4
- A/B against current tag UI. Live to half of inbound traffic. Weeks 4-7
- Measure: fields captured per visitor, tour-completion rate, tour-to-lead conversion lift. Week 8
Target outcome
A measurable lift on tour-to-lead conversion on top of the 34% StudentBridge already reports, plus a structured signal feed ready to power Use Cases 2 and 3.
Section 06 / Use Case 2
Persona-cut Video Viewbooks.
Most edtech can produce content faster than they can tailor it. AI as the editor solves the tailoring half without touching the production half.
6.1 The problem
A Video Viewbook today is one experience for everyone. A first-generation 17-year-old, a transfer student returning at 28, and a parent of a high-school junior see the same content in the same order. The Creative Services team produces one master. They cannot reasonably hand-cut per persona at the scale of 250+ institutions.
6.2 What AI does
Tag every clip in an institution's library on multiple axes (speaker, topic, persona fit, emotion, length, tone). At visit time, sequence a 90-second persona cut from existing footage based on the visitor's intake signal. Brand-safe templated lower-thirds, captions, music bed. No new shooting. Real footage stays real.
6.3 Persona examples
P1
Student
First-gen
Belonging-led cut
Opens with first-gen student stories, mentorship programs, dedicated support center.
Athlete
Facilities-led cut
Opens with team training, coaches, championship moments, dorms near athletic complex.
Adult learner
Outcomes-led cut
Opens with career services, employer partners, flexible scheduling, alumni stories at 30+.
P2
Parent
Parent track
Cost, safety, outcomes same library · different 90 seconds
Opens with financial aid stories, career placement rates, campus safety services, faculty access, alumni success. The second decision-maker hears the story tuned to their concerns.
6.4 Pilot shape · 8 to 10 weeks
- Pick one institution with a rich existing footage library. Define four personas with their team. Weeks 1-2
- AI-tag the library. Build the sequencer. Brand-voice approval gates in the UI. Weeks 3-6
- Run persona cuts against a control viewbook. Measure watch time and click-through to apply. Weeks 7-10
How Creative Services sits inside this
Creative Services is not replaced by AI. The team still shoots, writes, and approves. AI is the editor that lets one master become four authentic cuts. The cameras stay. The editors gain leverage.
Section 07 / Use Case 3
Weekly AI funnel briefings.
Every Monday morning, every institution gets a one-page brief on what to do this week. Generated. Reviewed. Sent.
7.1 The problem
StudentBridge captures rich engagement across all five products. Admissions and marketing teams are stretched thin and rarely have the time to mine the dashboards for actionable patterns. The platform produces signal. Teams need direction.
7.2 What AI does
An LLM layered over engagement data summarizes the week, ranks drop-off points, identifies high-performing content, flags high-intent prospects with stale contact recency, and drafts the recommended next actions. Output is one page per institution, delivered by email and surfaced inside the existing analytics view.
7.3 Example brief
Monday brief · Mock
- This week. 312 prospects engaged with VisiTOUR. 217 completed a tour. 28 reached the apply CTA.
- Where it leaked. Engineering prospects dropped 70% at the lab stop. Two clips (X, Y) were rewatched 3x.
- Recommended. Promote clip X in this week's SMS to engineering inquiries. Suggested copy below.
- Action list. Three high-intent prospects without contact in 10+ days. Aaron, Maya, Devin.
7.4 Pilot shape · 8 to 10 weeks
- Read-only data access to two or three pilot institutions' analytics. Weeks 1-2
- Brief template designed jointly with one admissions team. Weeks 2-4
- Weekly cadence. Counselor feedback captured each Friday. Weeks 4-10
Why start here
No new UX for students. No content production change. No Slate write-back required initially. Low LLM cost. Fast to a working demo. A natural first use case to pilot, building the data and habits the other two depend on.
Section 08 / Discovery sprint
One week of discovery, before any build.
Before code is written for any pilot, a short paid discovery sprint grounds the work in real systems, real users, and real numbers. One week. One outcome. A pilot scope locked in writing, with a confidence level both sides can sign off on.
8.1 What the week covers
01
System and data walkthrough
Read-only walkthrough of the relevant StudentBridge surface (VisiTOUR, Viewbook, Amplify, or analytics), Slate integration shape, content libraries, and existing instrumentation. No production access required.
02
User and journey shadowing
Time with one admissions team at a partner institution to watch the real workflow, plus interviews with two or three counselors. The aim is to validate that the pilot moves a number that matters to the people doing the work, not just a dashboard metric.
03
Risk surface and scope lock
FERPA posture, Slate write paths, brand-voice guardrails, LLM cost envelope. Everything that could derail the pilot named upfront. Pilot scope, success metric, and timeline locked in a one-page sign-off.
8.2 What you walk out with
| Pilot scope sheet | One page. What is in, what is out, what we measure, what success looks like. |
| System map | Annotated diagram of the StudentBridge surfaces touched, the data flows involved, and the integration seams. |
| User and persona notes | Direct observations from the partner institution: where the work actually breaks, what AI should and should not touch. |
| Risk register | FERPA, brand, integration, and cost risks named with proposed mitigations. |
| Fixed pilot quote | A fixed-price pilot proposal with a clear milestone schedule, replacing the indicative ranges in this document. |
Why this comes first
A pilot built on guesses ships a feature that does not move the right number. A week of discovery is the most efficient way to make sure the right pilot gets built, not just any pilot. The cost of the sprint is folded into the pilot if either side proceeds, so the commitment is genuinely small.
Section 09 / What a pilot looks like
Bounded. Measurable. Reversible.
After discovery locks the scope, a SoluteLabs pilot is intentionally small. The point is to learn whether the use case moves a number that matters, not to ship a product. If a pilot does not earn the right to scale, we shut it down. Cleanly.
01
One institution
A single pilot partner inside the StudentBridge customer base. Their admissions or enrollment marketing team becomes the design partner.
02
One use case
One of the three lead pilots above. Not bundled. Not blended. One thing to learn at a time.
03
One metric to move
Tour-to-lead lift, watch-through rate, counselor action rate. Defined before the pilot starts. Measured at the end.
| Pilot |
Primary metric |
Window |
| Use Case 1 · Conversational intake | Structured fields captured per visitor; tour-to-lead conversion lift | 6-8 weeks |
| Use Case 2 · Persona viewbooks | Average watch time; click-through to apply, vs. control viewbook | 8-10 weeks |
| Use Case 3 · Weekly briefings | Counselor-reported "I took an action from this brief" rate; week-over-week response time | 8-10 weeks |
Governance, said upfront
- FERPA and student data. Pilots begin with de-identified data, or with production data only with the institution's IT sign-off in writing.
- Slate integration. Additive only. No writes that risk the existing sync.
- Brand voice. Every generated asset routes through a brand-approval gate before publication.
- Cost. LLM cost lands in the cents per student, not dollars. Predictable, not surprising.
- Ownership. SoluteLabs builds and operates. StudentBridge owns the IP, the data, and the customer relationship.
Section 10 / Working questions
A few things worth discussing together.
Each of the use cases above could take different shapes depending on context that only the StudentBridge team can speak to. A short list of questions to talk through before scoping a pilot.
| Whose decisions to accelerate | The prospect's, or the admissions team's at your customer institutions. Both are valid; the priority shapes the pilot. |
| Slate integration depth | How tight is the integration today and how far do customers expect it to go. Governs every downstream pilot. |
| What customers are already asking for | Which institutions are pulling for AI features today, and what they are pulling for. |
| Prior AI experience inside StudentBridge | What has been piloted, what worked, what did not. |
| Brand-voice and creative review | Where the Creative Services team would want approval gates on AI-generated content. |
| Pilot ownership | Who on the StudentBridge side would partner with us day-to-day once a pilot starts. |
| Success threshold | What a pilot would need to move for it to graduate into a wider rollout. |
Shared outcome for the hour
Two or three use cases to take forward together, a partner named on each side, and a working follow-up to keep the conversation moving.
Section 11 / Next steps
If anything here resonates, one small step.
A one-week discovery sprint. Together we pick one use case, walk the relevant StudentBridge systems, sit with one of your partner institutions, and come back with a fixed-price pilot scope that replaces the ranges in this document.
A small, bounded commitment that lets both sides see exactly what the pilot should be before anyone signs up for anything bigger. When the fit is there, the discovery week rolls straight into the pilot, the work continues without a separate kickoff.
The ask
A one-week discovery sprint, scheduled at a time that works for your team. If that feels like the right next move, we can sketch the shape of it together before we leave the room.