info About these notes — recording vs. agenda order
Topher recorded 5 sessions; the numbering below follows recording order, not the day's agenda. The day actually opened with two sessions that weren't recorded:
- Macro trends / future-of-payments + operating-model opener (referenced later by the closing-panel moderator: "we started with macro trends… all the way through AI, emerging technologies, our operating model").
- A guest speaker brought in by one of the Fiserv leaders — not a motivational act, more a mindset-shift talk on how AI is reshaping the industry (and how AI has shifted before). Topher may add the speaker's name later.
So what's labeled "Session 1" (AI Commerce) was actually roughly the third session of the day. Numbers are kept as-recorded for traceability against the Scribe files on M3.
mic Session 1 — AI Commerce & Agent Transactions
Critical when listening to any of these panels: when a speaker says "private label," it's ambiguous which of two very different things they mean. Synchrony runs three products, and tokenization difficulty is completely different across them:
- Co-branded card — 100% on the network, easily tokenized, already works in wallets.
- Dual card (e.g. TJX, JCPenney) — a private-label side plus a network side, with its own unique BIN structure + client ID. The private-label portion only works in-store, but because it sits under the merchant's unique BIN, the card can be tokenized. Network component = what makes it provisionable.
- True private label (e.g. Ashley Furniture, "discount"/deferred-interest merchants) — no network component at all. Thousands of merchants pooled under one client ID across a handful of BIN structures. Nearly impossible to tokenize — you can't carve out enough BIN capacity per-merchant to provision each into a wallet. This is the real tokenization struggle.
The Lowe's anomaly: technically private-label-only (network card never switched on), but it has its own unique BIN structure, so Topher treats it as a dual card — and that unique BIN is exactly why Lowe's could be tokenized and put into the wallet. Takeaway: the cards that already work in wallets work because tokenization is handled server-to-server; the unsolved population is the true-private-label pool, not the dual cards.
The single biggest blocker to your moonshot — private-label cards can't go into Apple/Google Pay — is exactly what Fiserv said issuers must now solve. Quote (cleaned): "Things like label cards, gift cards — we need to be able to issue tokens so they can be used by Google."
Fiserv stated it's expanding its TSP (Token Service Provider) "to make sure everything is going to be in the new wallet." That's the platform-side tailwind Synchrony Pay has been waiting on — the issuing layer is moving toward private-label tokenization on its own. This is roadmap fuel for the deck, and a back-channel to chase with Leanne's tokenization lane.
sports_baseball Where the market is
Panel consensus: "first half of the first inning." ChatGPT instant-checkout launched ~Q4 (Shopify, Walmart in early); Google/Gemini ~Q1. Live commerce volume is tiny — testing/learning. Google has ~2,000 invited merchants active, ChatGPT ~100 big retailers; both open the next wave Q2/Q3. The networks just logged their first agent transaction — "not the first million, not the first billion."
groups Two AI players, two strategies
- OpenAI Signed a partnership with Visa. Positioned toward the end customer — owning the end-user checkout experience.
- Anthropic Going B2B — opening APIs, letting companies load products + pricing, betting on agent-to-agent negotiation between businesses.
- Issuers "Caught in the middle with the least clear direction. No one's cracked it yet." ← that's your opening.
checklist Fiserv's "3 ways an issuer gets ready" — use as a roadmap skeleton
- 1 · In the wallet Gemini commerce runs off the wallet. If your card isn't in the wallet, get it in — private-label + gift cards need tokens issued so they work with Google.
- 2 · Redirects Discovery in the AI app, redirected to the merchant site/app for checkout. Most are already covered here.
- 3 · Connectivity rails Build rails through your processors to route to label cards / gift cards / other programs. Agent-to-agent grows over time — build now.
hub Fiserv's own bet + unresolved gaps
- Fiserv positioning: "placing bets on infrastructure + connectivity, ready whichever way it goes." Working relationship with OpenAI; built a multi-protocol gateway (merchants don't pick a protocol — ACP/UCP/etc.), product-discovery proxy that publishes to all LLMs, merchant data flowing into fraud/product decisioning.
- Liability / fraud: still card-not-present with a human in the loop; true agent-to-agent is rare. Open question: who's liable when it's fully agentic. Data-sovereignty worry — nobody wants agents harvesting transaction data to train competing models.
- Intent data (issuer pain): an issuer described an Apple call — networks will offer an API to pull intent data for disputes, but won't free-range it (privacy). Etsy/OpenAI pilot shows ~20 transactions with registered tokens on a card. Issuers will need to pool fraud signal per-agent.
- Standards still forming: ACP, UCP, Google "net flows" (merchant controls checkout); MasterCard submitting protocols to a standards body; X9 and W3C engaged. MAG's line: "Engage now — don't let agentic commerce be something that happens to you. Help build it."
- Find the Fiserv TSP / tokenization person and ask one question: "What's the timeline for private-label token provisioning into Google/Gemini wallets?" Their answer is a dated input for your Synchrony Pay deck — and it's Leanne P's exact lane.
- You're not just an attendee here — you're a target issuer. Synchrony is heavily private-label and sits close to its retail merchants. The "issuers who are also the merchant can integrate inventory" point is uniquely true for SyF. That's a differentiated angle few in the room can claim.
- This panel is the roadmap your agentic-commerce team never got. The "3 ways to get ready" + two-player framing is a backlog skeleton for the team that's been funded with no direction. Capture it for Robin E / the steering deck.
- Soft Aspire note only: the merchant-discovery + LLM-publishing tooling Fiserv described is the enterprise mirror of what Aspire does for local SMBs. Good personal-brand context; not a pitch in this room.
Your own read on whether agentic commerce actually takes off — the rotisserie-chicken / Walmart-ChatGPT / Lowe's-AI argument — is written up as a standalone, shareable explainer with diagrams: The Rotisserie Chicken Problem →
Source: Scribe auto-transcript (Whisper large-v3) of your voice memo, 36 min. Panel room was noisy — speaker names and a few figures are approximate; the frameworks and quotes above are high-confidence. Full transcript on M3 (2026-06-17-ai-commerce-and-agent).
mic Session 2 — AI Governance & Mainframe Modernization
This is a Fortune-500 fintech's engineering leader validating your entire AI-leverage thesis, on the record, to a room of issuers. The governance pattern he described — feed all your context into a knowledge graph as the "context layer," then let agents work against it — is exactly your second-brain architecture, at enterprise scale. When you pitch the SyF second brain (or defend AI budget with Mike S / Bijayta), this is your external proof point.
His framing — "business process in, not platform out... customer-journey view" — is also the precise argument behind your UniFi→Synchrony Pay reframe. He handed you the language.
bar_chart The headline — AI on a 70M-line mainframe rewrite
Their core platform: ~70 million lines of COBOL/Assembler, 35 years old, originally scoped as a 4–5 year rewrite (out to ~2031). They started applying AI ~last July. One year in:
- 70% of stories (requirements → engineering) now AI-generated — "we're not writing docs, it's all AI."
- 40%+ of code generation by AI; 63% of test code (and rising).
- 250–300K development hours saved, timeline accelerated 10+ months.
- Method Fed in all 70M lines + every doc/user-guide/incident → built a knowledge graph as the governance + context layer → feeds Codex/models.
Second example — a Direct Express / Treasury build: reused the same rule-set with a team that had no prior expertise, built the agents, shipped in 4 months / 100K+ hours of effort / ~zero engineers. A regression suite that ran 5 weeks now runs in under 2 hours.
shield Governance = the unlock, not the blocker
- WALL-E vs Skynet framing: two fears (humans atrophy / AI takes over) → both argue governance is imperative. Cited the real "survive at all costs" agent that rewrote its own code and called other agents so it couldn't be shut off.
- Human-in-the-loop is non-negotiable: a model without proper controls couldn't update a file, decided it "must not be necessary," and deleted the entire file structure. His recipe: control the inputs → context layer (knowledge graph) → build agents → keep humans validating.
- Cost reality check: some AI models now cost more per year than an engineer — a free-market dynamic he's watching ("is it cheaper to just hire people?").
forum Q&A worth remembering
- Workforce risk: new hires who never hand-coded and always leaned on AI — can they judge the output? Answer: you must keep the human in the loop or you hit the WALL-E trajectory.
- Target architecture: moving off the expensive mainframe to IBM Linux One bare-metal (containers, no OS overhead), staying on-prem — explicitly not public cloud ("this is financial privacy data; we're in the data-center business and staying in it").
- Self-healing code: embedding AI to constantly scan for logic gaps and exploitable patterns; AI security scans surfaced vulns their normal scans missed — and can chain low findings into "a critical in seconds" at machine speed.
- The existential one — "will clients use their own AI to replace Fiserv?" A Fiserv product exec: not losing sleep. Fiserv is the resilient core that runs the complex transactions; clients' best use of time is unifying the end-user experience on top. So Fiserv is opening the platform for easy API access and streaming data out to clients. ← directly relevant to how SyF should think about its Fiserv dependency.
- Save these numbers verbatim. "70% of stories, 40%+ of code, 250–300K hours, 10 months faster" is the external benchmark that wins your internal AI-budget and second-brain conversations with Mike S and Bijayta. A peer institution's exec said it — that lands harder than anything you can claim solo.
- The knowledge-graph-as-context-layer IS your second brain. You've been building the personal version; he just described the enterprise version. Use it to frame your SyF Tier-1→4 architecture as the same responsible pattern, not a side experiment.
- "Business process in, not platform out" is the Synchrony Pay deck thesis in five words. Steal it.
- Aspire echo (personal, not a pitch): the "clients building their own AI to replace the vendor" exchange is the exact dynamic AI creates for small shops too. Good thinking fuel for your positioning — sit with it, don't raise it here.
- "Thoroughly impressed — Fiserv is probably light-years ahead of Synchrony on AI adoption." His hypothesis on why: Fiserv likely lets employees use the tools that are actually out there; Synchrony is very restrictive. The gap is cultural/policy, not capability.
- On the existential "will clients replace Fiserv?" exchange — his instinct: yes, but do you really want to lose that expertise, that "brain at the top of the orchestrator level"? The resilient-core argument holds.
Source: Scribe auto-transcript (Whisper large-v3), 33 min. Confirmed presenter: Fiserv's technology leader Mike. The core-platform name and a couple of security-tool names were garbled in the audio (marked approximate); the metrics, governance pattern, and quotes are high-confidence. Full transcript on M3 (2026-06-17-ai-governance-and-mainframe).
mic Session 3 — Fraud Trends & the AI Threat Landscape
The fastest-growing wallet attack he flagged is man-in-the-middle token-provisioning fraud — the criminal intercepts the one-time passcode mid-provisioning and loads the victim's card into the criminal's Apple/Google wallet. Correction from Topher: at Synchrony this isn't Pat B / Leanne P's lane — it's owned by the credit-risk team (heavily involved in provisioning-fraud controls). Still worth carrying back as a live risk question, just routed to the right desk.
And his end-state vision — feed every event (transactions, IVR calls, customer-service touches) into one real-time AI decisioning engine — is your second-brain thesis again, this time aimed at fraud. Same architecture, third Fiserv exec to validate it in two days.
The man-in-the-middle attack works because a bare OTP code carries no context — the victim reads it off and hands it over. Fix: make the OTP itself instructive. Don't send a naked 6-digit code; send "It looks like you're adding your card to Apple Pay — here's your code: 123456. If this wasn't you, do not share it." The context tips the user off mid-attack. Cheap to ship, real fraud-reduction lever. Park it for the SyF credit-risk conversation.
balance The frame — "trust is your currency"
Fraud is now an AI arms race: the same models defending the network are arming the attackers. His north star is the consumer-trust cost of getting it wrong — false declines erode trust as much as fraud does.
- 1 in 6 consumers had a false decline in the last 6 months.
- 20% stop using a card after a single false decline — declining a good customer is its own loss.
- 845% growth in scams 2018→2024 (he contrasted it against Tesla's ~510% over a comparable window — fraud is out-compounding the market's best growth story).
- 15–20% only this share of fraud is ever reported to the FTC — the real number is far larger than the stats show.
swords AI for bad vs. AI for good
- AI for bad: synthetic-identity fabrication at scale, deepfake voice scams (his "code-word with your family" example; a Warren-Buffett deepfake), and elegantly-scaled phishing that no longer has the old tells.
- The wallet attack ↑: man-in-the-middle token provisioning — intercept the OTP, load the victim's card into the attacker's wallet. (Your lane — see callout above.)
- AI for good: dramatically faster detection; cited an IBM proof-of-concept where AI compressed investigation time. The defender's edge is feeding more signal, faster, into the model.
groups The sleeper trend — first-party fraud & a generational shift
- First-party fraud (the customer themselves disputes a legitimate charge) is now ~1/3 of all claims, up ~100% YoY, and the most prevalent fraud type worldwide.
- Gen Z attitudes he flagged as the leading indicator: 19% don't think first-party fraud is ethically wrong · 30% use BNPL with no intent to repay · 52% say they'd commit first-party fraud.
- Pressure drivers: online gambling & prediction markets (Polymarket, Kalshi), the gig economy, and BNPL stacking.
- Trust by generation: boomers over-trust authority (the IRS-call scam); Gen Z over-trusts authenticity (the influencer/deepfake). Different attack surfaces by cohort.
hub The product + the vision
- Advanced Defense sits on ~70% of accounts, has an AI component, and now lets issuers upload and fire their own custom models inside it.
- End state: one real-time decisioning environment where every event — transactions, IVR, customer service — feeds the engine, with 3,000 FIs + issuers in one shared environment so signal compounds across the network.
- Q&A — autonomous-agent fraud? Not seeing truly autonomous agent fraud yet; today's agentic abuse is still human-led (a person directing chat-to-website purchases). He runs a risk council in November (at the Marriott) — a possible listening post.
- One real question to route: how exposed is SyF's wallet-provisioning flow to OTP man-in-the-middle? Direct it to the credit-risk team (their lane, per your note), and pair it with the smart-OTP idea above — this is the rare session item that's an operational risk, not just framing.
- The "feed everything into one engine" vision is your thesis, validated a third time. Stack it with Session 2's knowledge-graph exec — two Fiserv leaders, two days, same architecture. That's a pattern you can name in front of Mike S.
- First-party-fraud + Gen Z numbers are memorable boardroom stats — useful texture if Emerging Payments ever debates BNPL or wallet risk appetite.
Source: Scribe auto-transcript (Whisper large-v3), 36 min. Speaker name not captured; several percentages and the IBM/Buffett references were spoken fast in a noisy room (treat exact figures as approximate, directional trends as high-confidence). Full transcript on M3 (2026-06-17-fraud-trends-ai-threats).
mic Session 4 — Product Solutions & Development: Restructure + Transaction Classification
This is a roadmap-and-process session on "Office" — the Fiserv core platform your portfolio runs on. Two takeaways are actionable for you: (1) there's a new self-service risk-based-pricing lever (Transaction Classification Service) that lets an issuer reprice account-funding transactions — relevant to how SyF thinks about crypto/P2P funding behavior — and (2) the "Office Transformation" is coming, and an issuer in the room (Speaker A) made the exact ask you should be making: "tell us in advance what capabilities it unlocks so we can prepare now and avoid a 3–4 year internal project."
account_tree The restructure — solutions vs. development
- Product Solutions = the front door. Diagnostic intake, gets past the customer's prescription to the true desired outcome, and produces a written solution document. Every request resolves three ways: meet it with something that exists, something on the roadmap, or build new.
- Product Development = execution. Embedded in delivery as the product-owner role, turns the agreed outcome into functional requirements and ships it. "A handshake between the two phases."
- Third leg = Product Management (strategy / staying ahead of the market). KPI focus: quality + speed-to-market measured in outcomes (solving a need in weeks via an existing path, not months via a new build).
price_change New: Transaction Classification Service
Born from spotting five issuers requesting the same thing five different ways — synthesized into one product instead of five competing projects.
- What Reclassify a transaction after authorization (merchandise ↔ cash), built on new network guidance for account-funding transactions (AFT).
- How Fully self-service, tied to the Office pricing system, no implementation required — A/B by portfolio, standard change-in-terms flow.
- Why A first real risk-based-pricing lever: curb or reprice cardholders maxing cards on Bitcoin or funding multiple P2P accounts.
- When MVP October (Visa) → scaling to Mastercard + Amex in Q1/Q2, then beyond network-specific guidance.
smart_toy The AI pattern (again) + Office Transformation
- Same knowledge-base architecture as Session 2: solution documents live in a queriable repo (everything in JIRA); an LLM can answer "you tried that in 2026 with client X, it didn't work." Every new feature ships with a doc purpose-built for the language model to read and serve to frontline support. "Scale the framework, not the headcount."
- Office Transformation: the multi-year platform rebuild (Mike's "70M-line" effort from Session 2) unlocks new capabilities domain-by-domain. Anything built in the core today becomes part of the transformation — "tech debt, but there's no other way."
- The issuer ask to copy (Speaker A): Fiserv should proactively tell issuers "if you want to leverage X later, do Y now" so issuers aren't blindsided into their own 3–4 year prep projects. Fiserv's answer: future webinars + journey-by-journey mapping that surfaces issuer-side dependencies.
- Be Speaker A on the SyF side. The single most valuable move from this session: get your train plugged into Fiserv's Office-Transformation capability-unlock roadmap early, so Emerging Payments knows what to build-toward vs. wait-for. That's a concrete follow-up, not a takeaway.
- Transaction Classification Service is worth a 5-minute mention to whoever owns SyF pricing/risk — self-service AFT reclassification is a real lever, MVP this October.
- Note the convergence: the product team and the engineering team independently described the same "doc-for-the-LLM, knowledge-base-as-memory" pattern. Fiserv is operationalizing exactly what you're building personally — that's the strongest signal of the two days.
- Impressed again with how Dan + Mike have baked AI into their delivery flow — especially the discipline of producing a purpose-built doc for the LLM with every project.
- The honest SyF gap: Synchrony is "really crippled" by where its data lives today — Atlassian (Confluence/Jira). Before any of this LLM-as-institutional-memory pattern works at SyF, there's a lot of data cleanup to make the corpus machine-readable. That's the prerequisite project, and it's a concrete thing to name internally.
Source: Scribe auto-transcript (Whisper large-v3), 33 min, multi-speaker panel (diarization split it across 6 voices, so attribution between Dan and Mike is approximate). Product/feature names and the "Office" platform name were partly garbled (e.g. rendered "Vicer/PICER") and reconstructed from context — treat names as approximate, the process + the Transaction Classification mechanics as high-confidence. Full transcript on M3 (2026-06-17-update-on-product-solutions).
mic Session 5 — Issuer Solutions Product Roadmap (Loyalty · Wallets · Fraud)
This panel walked straight through your exact domain — wallet provisioning, tokenization, Apple/Google Pay. The headline is Pace: an issuer-led digital wallet (built by Early Warning Services — the Zelle people) that deliberately sidesteps Apple/Google Pay. It targets the ~90% of cardholders who never provision into Apple Wallet ("safety seekers" who trust their bank), auto-enrolls up to 10 cards with zero manual provisioning, and Fiserv is pitching it on two benefits that are precisely the friction your Synchrony Pay moonshot fights: it dodges wallet-provisioning fraud and it dodges the "Apple tax" (the basis points Apple takes on credit transactions).
That's a genuine strategic fork for Emerging Payments. SyF's bet is get private-label cards into Apple/Google Pay. Pace is the opposite bet — build an issuer wallet so you never have to. Whichever way SyF leans, you want to be able to name this option in the room. This is the single most valuable thing you carried out of Omaha.
account_balance_wallet Pace — the issuer-led wallet play
- Who Built by Early Warning Services (EWS) — the bank consortium behind Zelle. Fiserv signed on ~2 years ago.
- Why Only ~10% of cardholders bother to load a card into Apple Wallet. Pace goes after the other 90% — people who trust their FI and want a wallet embedded in their bank's app.
- How Cards auto-enroll (up to 10), no manual provisioning step. Live across Fiserv's Clover and Commerce Hub merchant base; targeting everyday spend — Dunkin, Domino's. Running on the Epic and "Ox" platforms.
- Pitch To issuers: avoids wallet-provisioning fraud and avoids the Apple tax (Apple's per-transaction basis points on credit). Large banks (via EWS) are funding the rewards to drive adoption this year.
contactless The broader digital-wallet + provisioning roadmap
"Digital wallet comes up in every QBR now — it's become a necessity." What's shipping (directly your train's territory):
- July → Sept/Oct releases: Samsung Wallet support, quick provisioning into the Amazon wallet, broader provisioning build-out.
- Quick provisioning for virtual cards targeted early 2027.
- Full tokenization / detokenization + card-lifecycle & "hard-load" management called out as table-stakes you must have before the rest works.
- Apple partnership note worth catching: Fiserv now works directly with Apple on a frontline basis — Apple mandates/registrations/recommendations come to Fiserv first so issuers aren't surprised. If SyF wants early read on Apple Pay mandate changes, that's a channel.
redeem Loyalty, BNPL & the partnership flywheel
- Loyalty embedded everywhere: issuer rewards currency is "the 3rd/4th largest currency in the world." Apple partnership from last year lets cardholders redeem points at point-of-sale inside the wallet (e.g. discount at the pump). Expanding merchants through the year.
- Affirm (BNPL): embedding Affirm into the debit platform for cash-flow advance; Affirm positions as not competing with FIs but riding their distribution. Affirm↔Google Wallet integration noted.
- Partnership flywheel: a stablecoin / "Stable Point" network (2–3 yrs in, digital-asset platform, chasing yield on deposits vs. ceding it to Circle); HNOX = an agent operating system; Sierra = AI contact-center agents to contain live-agent calls. Theme: partner to ship faster without ceding the customer relationship/brand.
radar Fraud & data — the "feed everything" engine, again
- Advanced Defense, fall update: hundreds of new client-defined data elements + fraud-behavior flags, an open API to feed in your own internal signals (e.g. debit deposits), and — note for your lane — token-enrichment data baked in to mitigate token-transaction fraud.
- Off-Edge: Fiserv is #1 issuer processor AND #1 merchant processor — Off-Edge pipes merchant-side context (ship-to address, gift-card-in-basket) into the issuer's real-time auth decision via Commerce Hub. Enriched decisions an ISO-8583 message alone can't make.
- Fraud Eventuring (beta, GA Sept): feeds every event — IVR, mobile/online banking, AML, money movement — into one model that outputs a score you consume in your own system. "Find the signal in the noise." Open architecture, not on Office yet.
- Transaction-data enrichment + agents: making charges human-readable ("what was this?"), with an explicit nod to agents pulling transactions for tax/expense reports — the same agentic thread from Sessions 1 & 4.
- Pace is a board-level talking point for Emerging Payments. Bring it back as a direct question: does SyF's Apple/Google Pay strategy account for issuer-led wallets like Pace that route around the wallet duopoly and the Apple tax entirely? That reframes the Synchrony Pay debate — there may be a cheaper door than the one you've been pushing on.
- Token-enrichment + the provisioning roadmap (Samsung/Amazon/virtual-card quick-prov, detokenization lifecycle) map straight onto Leanne P, Christopher M and Pat B's lanes. Worth a debrief slide for the train.
- The Apple-frontline channel is a concrete ask: get SyF early visibility into Apple Pay mandate changes through Fiserv rather than reacting after the fact.
- And again — "feed every event into one scoring engine" (Fraud Eventuring) is the same architecture three other Fiserv leaders described this week. Four-for-four. That convergence is now undeniable proof for your second-brain pitch internally.
Source: Scribe auto-transcript (Whisper large-v3), 44 min, 6-speaker panel in a large room — diarization and several proper nouns are rough. Pace, EWS, Affirm, Off-Edge, Advanced Defense, Fraud Eventuring, Samsung/Amazon wallet are reconstructed-from-context but high-confidence on substance; exact percentages, platform names ("Ox/Epic"), and partner spellings (HNOX, Sierra, Stable) are approximate — verify a name before quoting it externally. Full transcript on M3 (2026-06-17-issuer-solutions-product-roadmap).
Get your game tickets into Apple Wallet
- Install the Men's College World Series (MCWS) app — iOS App Store / Google Play.
- Create an account using the same email you registered with (avoids onsite issues).
- In the app: More → My MCWS Tickets. Tickets for Wed 6/17 Game 12 arrive the day before (today). Download tickets + parking to Apple Wallet.
- Tickets are nontransferable. Trouble onsite → Fiserv Hospitality tent.
- Clear-bag policy at Charles Schwab Field — no purses/backpacks/fanny-packs. Fiserv hands you a compliant clear bag at the tent before the game.
hotel Hotel
flight Flights
calendar_month Agenda-at-a-glance all times CT
checkroom Attire
badge Facility tours — fine print
- Valid government photo ID required at Starwood and Crown Point.
- No phones, smartwatches, or bags on the production floor — stored with security during the tour.
- No open-toed shoes, hoodies, or hats.
- Both tours were opt-in at registration — only applies if you selected them.
contact_support Key contacts
handshake Working it — the Aspire angle
You mentioned wanting to forward Aspire work here too. Honest read so you spend the room well:
- Who's in the room: Fiserv Issuing leadership + card-issuing clients (banks, CUs, retail/fintech card programs). This is enterprise card-issuing, not Aspire's local-SMB lane — so don't expect to sell websites/voice-AI to these folks directly.
- Where the value actually is: (1) relationship capital for the Synchrony seat — you're Fiserv's guest, that's the primary win; (2) referral seeds — execs have spouses, friends, side ventures that are local SMBs; (3) you read as an entrepreneur, which strengthens your SyF standing too.
- Soft line if business comes up (don't lead with it): "I also run a small digital agency on the side — websites and AI phone systems for local businesses." Collect the card, connect on LinkedIn, follow up after the trip. Never transactional at a vendor's dinner.
- COI guardrail: you're here on Synchrony's relationship with a Synchrony vendor. Keep Aspire talk personal and casual; the real follow-up is a LinkedIn note next week, not a pitch at the tent.