Date: April 15, 2026
Participants: Jeff Rudnick, Larry Czerwonka, Jon Bockman, Stacey Smith, Joe Sturza, Brooke Snappy's (joined late)
Call Context: Regular Project WE group call. Jon flagged a possible duplicate mailing from the direct mail program; Larry and Jeff addressed it briefly before pivoting to the platform roadmap. Larry demoed the cross-pollinator card builder (live, significant improvements) and the AI visibility grading tool (fake data, early preview). Brooke joined late and triggered a 25-minute conversation about charity fundraiser strategy, automated charity notifications, the duck race fundraiser, and the July 4th 250th anniversary opportunity. Joe surfaced a live car wash partnership with Whitewater (a growing Texas-based chain) — the most commercially significant moment of the call. The conversation ended with Larry sketching a vision for a gamified cross-pollinator loop that blew Jeff's mind. Call ran 65 minutes, about 30 minutes longer than planned.
Larry Adds QR Code Upload Field to Cross-Pollinator Card Builder — With Auto-Sizing and Placement
TIMELINE: Before Joe's car wash partnership goes live — this is a real, in-progress deal
TARGET: Partner uploads their QR/barcode into the card builder; system auto-sizes and places it; partner can reposition. Car washes, subscription businesses, and anyone with scan-at-register flows need this.
WHY: Joe is actively negotiating with Whitewater (nationwide chain, recently entered Michigan). The card builder needs to handle their barcode or the partnership can't be activated. Jeff confirmed this is how every car wash operates now. If it works with Whitewater, Joe may be able to connect Jeff to the chain nationally.
Larry Runs Direct Mail Attribution Report for Jon — Did Recipients Come Back?
TIMELINE: This week
TARGET: Match the full history of sent direct mail postcards against visit/spend records — show who received a mailer and came in within a reasonable window
WHY: Jon wants to know if the direct mail program is actually working before the program gets stopped or expanded. Jeff acknowledged that without an accountability report, programs always get cancelled eventually. Larry confirmed the data exists to run this. Result determines whether they continue, automate, or stop direct mail entirely.
ACTION #3: Larry Ships Cross-Pollinator Card Builder to Jon for Soft Launch — Non-Judging Friends Test
TIMELINE: As soon as developer can be put back on it — was pulled off for other work
TARGET: Jon (and ideally Joe) take the builder to a few local business relationships and have them build their card. Feedback loop before broad release.
WHY: The builder is close. Logo pulls automatically, stock images categorize by business type, background is repositionable, colors/text are editable. The offer-type selector (beyond 10% off) is the remaining gap. Jeff is already holding a new client who wants cross-pollinators and can't onboard them until the system is done.
ACTION #4: Jeff and Larry Explore the Gamified Cross-Pollinator Loop — Location Verification + Automated Reward Trigger
TIMELINE: Design conversation — not a build item yet
TARGET: When a customer visits a cross-pollinator business (e.g., car wash), the system detects or verifies the visit and automatically delivers the bounce-back reward to them, triggering a return visit to the auto shop
WHY: Larry sketched this out at the end of the call — phone geolocation as passive verification (5 minutes at a location = visit confirmed), automated reward delivery without requiring the partner business to do anything. Jeff's reaction: "Larry, thanks for blowing our minds once again." The chain-of-businesses version (bakery → car wash → auto shop → bookstore, each triggering the next) is the long-horizon vision. This is the architecture that makes the cross-pollinator defensible and differentiated.
ACTION #5: Reinstate Automated Charity Notification When a Shop Sets Up a Fundraiser
TIMELINE: Near-term — existed in the old system, got dropped in the rewrite
TARGET: When a shop enters a charity email and activates a fundraiser, the system sends an automated notification to the charity: shop name, what they're doing, a brief blurb, and the charity's logo embedded so they can put it in their newsletter
WHY: Jeff described the old version — Jon set up a high school fundraiser, the charity called him to thank him because of the auto-notification. That's free goodwill, free social media amplification (Joe's Humane Society fundraiser got 70 shares from the charity's own followers), and a relationship hook. Feature should have a toggle for shops like Brooke who already have direct relationships and don't need the form letter.
ACTION #6: Larry Gets Joe's New Avatar Live With a Matching Voice — This Week if Possible
TIMELINE: This week; if not, last week of April when Joe returns from Utah
TARGET: New avatar deployed with a voice that fits the new visual; Joe, Dustin, and Emily pick from options Larry presents
WHY: Larry confirmed this is 30 minutes of work on his end. Joe is leaving town this weekend. If it ships this week, Joe can review before he leaves. If not, they wait two weeks.
ACTION #7: Add Automated End-of-Fundraiser Summary to Charity — Amount Raised, Thank You, Transfer Prompt
TIMELINE: Future feature — flag for roadmap
TARGET: When a fundraiser period ends, system sends charity a summary of total raised and prompts the shop to initiate payment — possibly linking to PayPal or similar for automated transfer
WHY: Jeff named the risk directly — shops sometimes forget to pay the charity. He's aware of shops that ran four fundraisers and never sent a check. Brooke just dropped off hers today. This is a reputational and trust risk that an automated reminder or payment link could eliminate.
Direct Mail — Duplicate Mailing Investigation and ROI Problem
Jon opened flagging that a customer received two postcards within about a week of each other and wanted to investigate before resuming the program. Larry believes the perceived duplication was likely a longer-than-remembered gap between sends — he's seen this before. Larry will run the attribution report to match the mailing list against visit records. The broader conversation landed on a clear truth Jeff articulated: without an accountability report, every direct mail program eventually gets cancelled. Valvoline research was cited showing that text + email + postcard produces meaningfully better retention than any channel alone — but the data has to prove it or the expense doesn't survive.
Portal Roadmap — Grading Page Coming Next Week
Larry confirmed the grading analysis page (Gantt-style visualization of customer segments with clickable drill-down) goes into the pitcrew rewards portal next week. The raw grading report will also get customer names added — currently shows only customer IDs. Jeff hadn't seen the AI visibility grading tool Larry also demoed — a scoring dashboard showing how findable a business is across Google, Yelp, Apple, Bing, directories, and community sites, with action items generated automatically. Fake data only, not live yet, but Jeff's reaction was immediate: "Larry has gone rogue."
Cross-Pollinator Card Builder Demo — Close, Not Done
Larry walked the group through the current state of the card builder. Significant improvements: the prompt is now at the top so users don't have to scroll, logo is auto-pulled from the business's site and confirmed with a single click, stock images are categorized by business type (the system infers the type automatically from the site), backgrounds are repositionable, colors and text are editable, and custom image upload works. The remaining gap: the offer type selector (currently defaults to 10% off, needs to expand to a menu of options) wasn't ready — the developer was pulled onto other work. Jon confirmed he could take it to some business contacts for soft testing. Jeff flagged a client already waiting to do cross-pollinators. Larry acknowledged the delay bluntly and said he hopes to put the developer back on it immediately.
Charity Fundraiser Strategy — Automation Gaps and What's Working
Brooke walked through her four-quarter charity fundraiser calendar: Q1 (small, last-minute — raised $126), Q2 (duck race at Zoombizi Bay with her fleet client — big engagement event, Waddles the mascot duck on her Pro Master van), Q3 (United Way back-to-school supplies), Q4 (People in Need / food drive). Jeff raised two automation gaps that got broad agreement: first, the old system automatically notified the charity when a shop set up a fundraiser (including their logo so they could put it in their newsletter), which generated calls and social shares — that feature was dropped in the platform rewrite and should be restored with a toggle for shops that have direct charity relationships. Second, there's no automated end-of-campaign summary to the charity with the amount raised, or any prompt to initiate payment — Jeff pointed out shops sometimes forget to write the check entirely. Jon described his upcoming DeKalb County Foundation fundraiser with a dollar-match mechanic. Joe confirmed his Humane Society fundraiser generated 70 Facebook shares from the charity's own followers after he personally reached out and shared the graphic.
Car Wash Cross-Pollinator — Joe's Whitewater Deal and the QR Code Problem
Joe surfaced the most commercially significant item of the call: he's actively in talks with Whitewater, a Texas-based car wash chain that recently entered Michigan, about a cross-pollinator partnership. Joe already sends nearly 2,000 customers per year to the nearby Whitewater location via a free car wash program. The new deal structure includes spirit days (a dollar per car wash goes to Joe's charity), community coupons back to Auto Doctor, and the cross-pollinator card. The technical issue: car washes use barcodes or QR codes that their machines read — the card builder needs a way to upload that code so it renders correctly on the digital card and scans properly at the wash machine. Larry immediately confirmed the fix: add an explicit "upload QR code" field, auto-size and place it, let the partner reposition. Jeff's comment: "I'm so glad you brought this up. We have to be able to do this because every single car wash operates this way now." If the Whitewater deal works, Joe may be able to connect Jeff to the chain's national team.
Gamified Cross-Pollinator Loop — Larry's End-of-Call Vision
The final 10 minutes were triggered by Joe asking what would happen if they could track QR code scans. Larry sketched it out: instead of using the partner's QR code, the system generates its own QR code that bounces through the Pit Crew system first and then redirects to the partner's URL — capturing the scan event without the partner needing to change anything. Then the conversation evolved: what if, when the system confirms a customer was at the car wash (via the scan or via phone geolocation — 5 minutes at the location), it automatically delivers a bounce-back reward pushing them back to the auto shop? And what if the auto shop reward then triggers a reward to go back to the car wash? Larry extended it to the chain-of-community-businesses vision: a local loop where visiting each cross-pollinator business unlocks a reward to visit the next, and completing the circuit earns a better reward to start again. Jeff's closing line: "Larry, thanks for blowing our minds once again. Joe, thanks for asking the right question."
Energy Assessment: HIGH
This call caught fire in the final 30 minutes. The first half was standard status — useful but measured. Then Brooke's fundraiser story opened a rich conversation about automation gaps, Joe's car wash question unlocked a 15-minute product design session, and Larry's gamified loop vision sent everyone out energized. Jeff's closing line ("thanks for blowing our minds") wasn't politeness — it was genuine. Jon had already left by that point. The Seinfeld tangents, hockey playoffs, dead whales, and duck-race stories kept the human texture strong throughout.
PEAK #1: Joe Drops the Whitewater Car Wash Partnership
WHY IT RESONATED: Jeff has wanted car wash cross-pollinators since he met the president of the Car Wash Association in Atlanta. Joe had the live deal and the nationwide chain connection. Larry immediately had the technical answer. Everything clicked at once.
STRENGTH: Very strong. Immediate multi-party alignment, real deal in progress, concrete technical path identified on the spot.
PEAK #2: Larry's Gamified Loop Vision — "Thanks for Blowing Our Minds"
WHY IT RESONATED: Larry connected geolocation verification, automated reward delivery, the bounce-back mechanic, and the chain-of-businesses model into a single coherent vision. Joe got it immediately. Jeff drifted partway through (he admitted it) and then snapped back in when the community chain picture became clear. The reaction was unsolicited and specific — a sign the concept landed.
STRENGTH: Strong. Room-wide reaction. Jeff specifically called out Joe for asking the right question that opened the door to it.
PEAK #3: Jeff Sees the AI Visibility Grading Tool for the First Time
WHY IT RESONATED: Larry built a full AI search visibility scoring tool (with action items) that Jeff had never seen. Jon immediately recognized the value. Larry's commentary about AI replacing Google search as the primary discovery mechanism was well-received by the group. Jeff's reaction was delight, not frustration — he knows Larry's rogue builds tend to become products.
STRENGTH: Medium-strong. Early-stage (fake data only), but the concept resonated with everyone present.
FRICTION — MEDIUM
Cross-Pollinator Builder Still Not Done — Jeff Has a Client Waiting
Larry had hoped to have the card builder 100% ready for this call. The developer was pulled onto other work. Jeff is already holding a new client who wants to do cross-pollinators. The group is in limbo. Larry named it directly and committed to putting the developer back on it — but this has been a recurring pattern.
FRICTION — LOW
Brooke Not Running the Full Fundraiser Playbook Yet
Q1 raised $126 and no Facebook post went out. Brooke acknowledged it and has given a staff member Facebook access to help. The infrastructure is in place (Q1–Q4 campaigns set up in LMA), but the amplification layer — tagging the charity, posting to social, reaching out directly like Joe did with the Humane Society — isn't consistent yet. Jeff was gentle about it. This is a coaching opportunity, not a risk.
ENERGY DRIVER: Joe Sturza (Auto Doctor) — Asked the question that unlocked the car wash partnership reveal and the gamified loop conversation. Jeff specifically credited him at the close. Joe is also the most operationally active — running charity fundraisers, negotiating partnerships, already sending 2,000 customers a year to a nearby car wash. He's building the methodology into his business without being asked.
VISION HOLDER: Larry Czerwonka — Showed three distinct product layers in one call (card builder demo, AI visibility tool, gamified loop architecture). The rogue build Jeff hadn't seen was the strongest signal — Larry is building ahead of the conversation, not just executing it.
STEADY OPERATOR: Jon Bockman — Consistent, thoughtful, pushed on the Pumpkin Fest opportunity, volunteered to take the card builder to non-judging friends. His comment about app simplicity (informed by the failed NAPA app experience from his industry council years) was the most practically useful product guidance of the call.
BREAKTHROUGH SESSION (9/10)
This call produced real product direction, a live partnership lead, a feature restoration request with full group buy-in, and a vision statement for the platform's long-term mechanics — all in 65 minutes. The car wash QR upload is a concrete shipping item. The gamified loop is the most compelling articulation yet of what makes cross-pollinator defensible. The only drag is the cross-pollinator builder still not done after another week of delay. But the energy leaving the call was the highest of any WE session in recent memory.
TRAJECTORY:
ACCELERATING — The Whitewater deal is the forcing function. If Joe closes it, it becomes a showcase case for car wash cross-pollinator. If Larry ships the QR upload field and the card builder finishes, Jeff can onboard the client who's waiting. The gamified loop is the product story that makes this category of feature defensible against imitation.
MOMENTUM-CALIBRATE CONFIDENCE: 85%
High confidence on energy and direction. The one uncertainty is whether the cross-pollinator builder actually ships this cycle — the developer-pulled-off pattern has recurred before. If it slips again, Jeff's waiting client becomes a real problem. The Whitewater partnership is in Joe's hands; Larry just needs to build the QR upload field before Joe closes the deal.
Intelligence Extraction Powered by The Arivu OS
Copyright © 2025-2026 The Larry Czerwonka Company LLC | All Rights Reserved