SourSuite
Start with the funnel templates, then layer the SaaS around them.
The most important part of SourSuite is the template library. Browse the restored route-based funnels first, compare how each one opens, and then use the workspace tools for routing, forms, analytics, and webhook delivery.
Workspace Snapshot
Launch, route, observe
Landing sets
Single-page or multi-variant funnels
Primary goal
Submission volume + completion rate
Delivery model
Webhook-first downstream automations
Control surface
Templates, variants, logging, analytics
Pick the page mix
Launch one page or a full A/B test stack. Swap hero structures, offers, and positioning without rebuilding your funnel every time.
Use native or embedded forms
Run forms directly inside the funnel or drop embeddable capture blocks into an existing site while keeping the same event model.
Track the whole journey
See which pages attract submissions, which variants complete best, and which sources create usable pipeline instead of vanity traffic.
Push outcomes by webhook
Keep the app focused on capture and attribution. Route submissions and lifecycle events to your CRM, email stack, or internal systems with webhooks.
Product Direction
The app should optimize funnel choice, data capture, and downstream routing.
That means the product surface centers on landing page selection, variant testing, form deployment, analytics, and event logs. Business-specific fulfillment stays outside the app through webhooks.
Choose a landing page template and turn on one or more variants.
Decide whether each funnel uses a native form or an embeddable form block.
Send captured events to your downstream systems through webhook delivery.
Use the dashboard to compare paths, variants, sources, and completion rates.
Current Cleanup
What this pivot is cutting out of the old product identity.
The visible app should stop acting like a single vertical business. The retained value is the funnel instrumentation, the variant logic, and the admin visibility.