Skip to content

Conversation

@joebeernink
Copy link
Collaborator

Summary

  • New project spec for driving community tier signups through better website presence
  • Addresses the gap: communities are the primary revenue driver but the website has no dedicated community-focused conversion page

Key Findings (Current State)

  • Home page CTA is "Join us today" — entirely volunteer-focused
  • Communities are buried under the Explore dropdown submenu
  • Partnerships page targets service providers (hauling, disposal), not geographic community partners
  • No dedicated "For Communities" landing page explaining the value proposition
  • No self-service enrollment path

Project Scope (4 Phases)

  1. "For Communities" landing page at /for-communities — hero, value props, feature showcase, pricing table, success stories, enrollment form, FAQ
  2. Home page community integration — community CTA in hero, featured communities section, community stats
  3. Navigation & discovery — "For Communities" in main nav, footer, and related pages
  4. Backend — enrollment form API endpoint that feeds into AI Sales Agent pipeline (Project 40), public community stats API

Test plan

  • Review project spec for completeness
  • Verify no conflicts with Project 2 (Home Page Improvements) or Project 36 (Marketing Materials)

🤖 Generated with Claude Code

Joe Beernink and others added 3 commits February 9, 2026 06:56
New project spec for a "For Communities" landing page, home page
community CTAs, self-service enrollment funnel, and community success
stories to drive community tier signups.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update Project 45 to reuse the existing partner request form instead of
building a separate enrollment system. Add Community = 3 as a new third
PartnerTypeEnum (not replacing Government) with clear distinction between
service partners and geographic community partners.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Detail how the form should distinguish Government, Business, and Community
partner types with card-style descriptions. Specify behavior when arriving
from /for-communities vs direct /becomeapartner, including conditional
intro text and pre-selection via query param.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@joebeernink joebeernink merged commit 99d408c into main Feb 10, 2026
1 check passed
@joebeernink joebeernink deleted the dev/claude/add-project-45-community-showcase branch February 10, 2026 01:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant