According to my Claude AI Assistant “Spock”
Salesforce Product Stack for EventCarpooling
📧 Email Newsletter Digest — Marketing Cloud Engagement (formerly ExactTarget)
This is the core engine. It handles:
- Email Studio — build and send the weekly curated event digest to subscribers per city
- Journey Builder — automate the digest on a weekly cadence, triggered by date or new content
- Content Builder — reusable email templates for each city’s newsletter
- Subscriber lists segmented by city — so Austin, Denver, etc. each get their own digest
🌐 Event Listing Website — Experience Cloud (formerly Community Cloud)
This powers the public-facing website (e.g., austin.eventcarpooling.com):
- City-specific subdomains can each be their own Experience Cloud site
- Event listings pulled dynamically from Salesforce records
- Self-service subscriber sign-up forms
- The eventcarpooling.com homepage can act as a hub Experience site linking to all city sites
📬 Subscriber-to-Subscriber Email Communication — Marketing Cloud + Salesforce Inbox / Einstein Activity Capture
- Marketing Cloud’s Reply Mail Management handles subscribers replying to digests and routing those replies
- For peer-to-peer communication (subscribers emailing each other), Experience Cloud’s messaging/chatter features or a connected email group list managed through Marketing Cloud would handle this — keeping it within the Salesforce ecosystem
👤 Subscriber Management & CRM — Sales Cloud or Nonprofit Success Pack (NPSP)
- Track every subscriber as a Contact record
- Manage city affiliations, subscription status, preferences, and history
- Since this is community-oriented and likely non-commercial, NPSP (free for nonprofits) is worth considering if it fits
✏️ Content & Event Management — Salesforce CMS (within Experience Cloud)
- Admins create and manage event listings as content items
- Content can be published to the right city’s Experience site automatically
- Supports images, descriptions, dates, and categories (music, tech, food, etc.)
📊 Admin Reporting & Dashboards — CRM Analytics (formerly Tableau CRM) or native Reports & Dashboards
- Track subscribers per city, email open rates, click-through rates, new sign-ups, unsubscribes
- Marketing Cloud has its own built-in Analytics Builder for email performance
- For cross-city executive reporting, CRM Analytics gives richer dashboards
🔗 Multi-City Admin Model — Salesforce Orgs + Profiles/Permission Sets
- Each city admin gets a Salesforce user with permissions scoped to their city’s data only
- Sharing Rules and Record-Level Security ensure Austin admin can’t see Denver subscribers
- A super-admin at the eventcarpooling.com level has visibility across all cities
How It All Fits Together
Need Salesforce Product Weekly event email digest Marketing Cloud — Email Studio + Journey Builder Public event listing website Experience Cloud City subdomains (austin., denver.) Experience Cloud multi-sites Subscriber sign-up & management Sales Cloud / NPSP Subscriber-to-subscriber email Marketing Cloud Reply Mail + Experience Cloud Content/event creation by admins Salesforce CMS Reporting for admins Marketing Cloud Analytics + Reports & Dashboards Multi-city admin permissions Profiles, Permission Sets, Sharing Rules
The MVP path would be Marketing Cloud + Experience Cloud + Sales Cloud, which covers 90% of what you described. Salesforce also has a Nonprofit Success Pack and Marketing Cloud for Nonprofits pricing tier if this is a community-driven project rather than a commercial one — worth a look for cost savings.
——
Costing info from Claude:
Licenses: Marketing Cloud Engagement Pro+ runs ~$2,000/org/month ($24K/year), MassMailer and Sales Cloud Enterprise is $175/user/month Cargas | for your city admins. The wildcard is Experience Cloud — it starts at $2/login or $5/member per month, CUBE84 and for a newsletter audience that clicks through once a week, login-based pricing is dramatically cheaper than named member seats. Budget ~$37,500–$51,000/year in licenses starting lean.
Implementation: 560–760 hours at a blended ~$175/hr consulting rate puts the build at $98K–$133K one-time. Experience Cloud site buildout (5 city microsites + hub) and Marketing Cloud journey configuration are the two biggest effort areas.
Timeline: Starting 6/26, you’re looking at roughly 23 weeks of work — a realistic go-live in early December 2026, in time for a January new-year push.
——
Salesforce moat/cost/benefit comparison/recommendation vs. vibecoded solution according to Claude:
The security data is alarming for vibe-coded production apps. Veracode tested over 100 large language models and found that 45% of AI-generated code introduces OWASP Top 10 vulnerabilities — a pass rate that has not improved across multiple testing cycles from 2025 through early 2026. Tech.co Research found that while AI-assisted teams were shipping code 4 times faster, they were shipping 10 times as many security flaws. Titan This isn’t theoretical — in February 2026, Moltbook — a social networking site built entirely through vibe coding — had a misconfigured database exposing 1.5 million authentication tokens and 35,000 email addresses, all wide open to the internet. The root cause wasn’t a sophisticated hack; it was vibe coding without security review. Twistellar
The Salesforce moat is real but mostly matters at scale. Salesforce’s SOC 2 reports cover Sales Cloud, Service Cloud, Marketing Cloud, MuleSoft, Tableau, and others, and are updated regularly and available through the Salesforce Trust Portal. Redress Compliance That compliance posture answers every question a city government, corporate sponsor, or partner like Fetii will ask — before you even get in the room.
The honest verdict is about sequencing, not choosing. For EventCarpooling right now — pre-revenue, single city, validating demand — a vibe-coded stack with a $5K–10K security review is the right call. Spending $135K on Salesforce to find out Austin subscribers won’t RSVP for carpools is the wrong order of operations. But plan the migration to Salesforce at 3+ cities, because OWASP added a dedicated category to its Top 10 in 2025 specifically calling out vibe coding as a security risk pattern CUBE84 — and a subscriber trust breach on a platform whose entire brand is “More Neighbor” is unrecoverable.
—-
My 2 rupees conclusion: Establish product market fit with working MVP solution before $pending a lot more on securing a vibe coded solution that may increase costs substantially. Scaling with serious security vulnerabilities may not be worth it without locking down the app.
After product market fit, focus on security features and migrate out of the current infrastructure.
What this analysis confirms: A major platform like Salesforce is way overpriced with professional services (slow delivery) and seat licensing (outdated). It’s a huge political headache to jump through hoops to bring the pricing down substantially.
The white space for vibecoders is coming up with an infrastructure solution that locks down security and ensures enterprise grade scalability. The opportunity for Salesforce solutions providers is to leverage Agentforce to come up with more agile delivery versus competitors. Leaving Salesforce altogether would be a mistake with it embedded in so many companies for so many years.
It makes little sense for entrepreneurs and small businesses to seek a new solution like Salesforce when cheap AI is readily available. In the near term, enterprises will be asking the same questions. 😉
customersuccessforgood.com 