Supplier Bridge Supplier Circle

Supplier Bridge Supplier Circle – The platforms are already up and running and are entering a critical early-stage growth phase focused on use adoption, usability, engagement, onboarding, and ecosystem development. Would like to check where the students can make an impact in any of the stages.

This is likely a good project for BSIS students

I asked them for more information, here's what the stakeholder said:

1. Is this an existing product, and are you asking for help on it?
Yes. Supplier Bridge and Supplier Circle are both live, working platforms — they're past the build stage and now in an early-traction phase. What we're looking for isn't new feature construction so much as help getting real users on the platform, identifying friction in the experience, and tightening the product based on what we learn. Concretely, that means:
• Hands-on testing of the platforms against real workflows, with structured friction logs
• Onboarding the first cohort of supplier accounts and documenting where they get stuck
• Outreach to small businesses to seed the early user base
• Messaging and positioning experiments — what language gets a first-time supplier to sign up vs. bounce
Separately, we have two adjacent products in the pipeline — FMR (Face My Resume), a real-time video-resume screening tool, and Recall Alarms, a centralized multi-channel recall-notification platform — that are in a similar "ready to push to market with AI enhancements" stage. Those could be alternative project tracks depending on student interest.
2. Are you asking to add AI to the existing product? If so, will the students be given access to the codebase?
There are two layers to this, and we'd like to be transparent about both:
The Supplier Bridge / Circle work above is primarily product/growth work, not codebase work — students don't need source access to run the testing, onboarding, and messaging tracks. They'd work against the live platforms the same way a real user would, plus shared docs and analytics dashboards we'd open up to them.
For the AI-enhancement track (FMR, Recall Alarms, and our internal-tooling AI initiative — using AI for Excel, presentations, email, etc.), the answer is yes, we are looking to add AI capabilities, and we're open to giving students scoped access depending on the project shape. Specifically:
• Read-only access to a sandboxed copy of the relevant codebase for design and prototyping work — yes, we can set this up.
• Write access to the production codebase — we'd prefer not to for IP reasons, but we can have students build AI prototypes in a separate repo that we then review and integrate ourselves.
• API-level integration work (calling our endpoints, building wrappers, building AI agents that sit on top) — full access, no issue.
Happy to align on which model works best for Drexel's process — whatever lines up cleanest with your IP and supervision norms on the senior-projects side.
3. Can you elaborate on what the deliverable is here?
For each track we'd define a concrete, demonstrable deliverable. Some examples:
• Supplier Bridge / Circle growth track: A documented onboarding-friction report plus a target number of activated suppliers (we can set the number jointly), and a tested messaging playbook based on real outreach data.
• FMR AI enhancement track: A working prototype of an AI module (e.g., resume-video scoring, candidate-fit ranking, or interviewer-prep generation), with a written technical design doc and a demo.
• Recall Alarms AI track: A prototype of AI-driven recall-message personalization or routing, with metrics on response/acknowledgment lift vs. baseline.
• Internal AI deployment track: A set of AI workflows (Excel/PPT/email automation) packaged so the LSI team can use them day-to-day, with documentation.
Each deliverable would have: a written report, the prototype/code or playbook artifact, a final demo, and a debrief — sized for a one-term senior project.