Founder roadmap — not final public marketing copy.

Padrino Pay V1 Roadmap

A focused view of what remains before Padrino Pay can launch as a strong, simple, clean product for real families.
You are here

Between Gate 1 and Gate 2

Current phase

Brand + prototype validation

Setup flow is strong. Homepage is in visual refinement. Next major product build: public support page and goal setup.

Gate 1 mostly completeGate 2 startedHomepage in refinementSetup flow prototyped
Gate 1Brand system selectedMostly complete
Gate 2Product flow completeStarted
Gate 3Payment readinessUpcoming
Gate 4Bilingual readinessUpcoming
Gate 5Pilot readinessUpcoming

Roadmap philosophy

Padrino Pay V1 should be strong, simple, and clean — not barebones.

V1 should feel trustworthy, useful, beautiful, and complete enough for real families to use proudly. The product should stay focused, but it should not feel unfinished, cheap, or like a throwaway MVP.

01 · Launch scope

Roadmap status lanes

A sequence from decisions already made through the work required for launch, with later expansion held deliberately outside V1.
01Mostly complete

Decided / Source of truth created

The product and brand rules already established for the launch version.

  • Brand foundation
  • Brand applications
  • Mission, vision, and values
  • V1 fee and tip rules
  • Stripe and payment processor assumptions
  • Support page accent palette rules
  • Lead visual direction
  • Wordmark-led logo direction
  • Page Boost strategy
  • Contribution routing rules
  • Homepage strategy and sales architecture
  • Homepage implementation spec
  • Creator setup flow rules
  • Milestone ownership rules
02In progress

In progress / Visual system

The selected direction being tested as a coherent, reusable product system.

  • Brand system preview
  • Core brand palette testing
  • Typography testing
  • Wordmark refinement
  • Support page accent palette testing
  • Design Lab surfaces
  • Creator setup flow visual validation
  • Homepage visual correction
03Started

Strong V1 product build

The focused product experience real families need to create, share, and support a page proudly.

Started / prototyped

  • Page setup flow
  • Prototype homepage

Next product build

  • Public support page
  • Goal setup rules UI
  • Support all open goals
  • Extra Support routing
  • Creator dashboard starting state

Still required for V1

  • Contribution checkout
  • Tip behavior
  • Bilingual EN/ES public page and checkout
  • Recent support
  • Updates and goal-complete milestones
  • Organizer and honoree section
  • Thank-you tracking
  • Contributor records
04Not started for real

Payment and trust readiness

The financial and support boundaries required before real money movement can begin.

  • Stripe Connect Express onboarding
  • Payout setup required before live payments
  • Payout status states
  • Processor fees deducted before payout
  • $10 minimum contribution
  • $5,000 V1 standard max contribution
  • 30% optional tip cap
  • Fraud and risk boundaries
  • Help and trust language
05Not started

V1 launch readiness

The review, testing, and family-facing readiness needed for a confident first public release.

  • Mobile QA
  • Accessibility checks
  • Spanish copy review
  • Test payment flow
  • Payout onboarding test
  • Supporter email and receipt direction
  • Organizer notifications
  • Privacy and terms placeholders
  • Founder review checklist
  • Pilot family readiness
06Deferred

Later / not V1

Valuable expansion work intentionally kept outside the focused launch scope.

  • Multi-currency
  • Mexico payouts
  • International payout recipients
  • Instant payouts
  • Advanced Page Boost palettes
  • Custom color picker
  • Vendor direct payouts
  • Event-specific landing pages
  • Native mobile app
  • Large contribution manual review workflow
  • Advanced analytics
  • Full marketplace and vendor network

02 · Product standard

What V1 must not compromise

Focused scope does not mean a diminished family experience. These qualities define launch readiness.
01Bilingual access
02Payment trust
03Clean contribution flow
04Public page beauty
05Clear goal support
06Fee and tip clarity
07Payout setup clarity
08Mobile usability
09Free page dignity
10Simple creator experience

03 · Launch gates

Decision gates before launch

Each gate should be explicitly cleared before the first public version moves to the next stage.
Gate 1Mostly complete

Brand system selected

Needs

  • Core palette
  • Typography
  • Wordmark direction
  • Support-page accent palette
Gate 2Started

Product flow complete

Needs

  • Create page
  • Goals
  • Public page
  • Checkout
  • Dashboard
  • Thank-you tracking
Gate 3Upcoming

Payment readiness

Needs

  • Stripe Connect Express plan
  • Payout onboarding
  • Payout states
  • Test transactions
  • Payout expectations
Gate 4Upcoming

Bilingual readiness

Needs

  • EN/ES product copy
  • Spanish review
  • Language toggle behavior
  • Bilingual receipts and notifications direction
Gate 5Upcoming

Pilot readiness

Needs

  • Real family test
  • Mobile QA
  • Support and trust docs
  • Founder review
  • Launch checklist