Builder resource
The Founder List
A Next.js site, a ConvertKit list, and a Plandalf checkout. Nothing else.
Ship a first paid product with three tools and no automation platform in the middle.
Three tools, no glue. Next.js renders the site, ConvertKit owns the list and the broadcast, Plandalf handles the offer page and Stripe takes the money. Webhooks tag buyers in ConvertKit automatically.
Built for: Indie hackers, technical founders pre-team
Architecture
Treat Plandalf Offers as the commerce layer between the sales page, the buying moment, and the payment processor. Your stack owns the audience and fulfilment experience. Plandalf owns offer configuration, checkout state, pricing rules, buyer identity, invoices, and the events that drive follow-up.
How This Stack Makes The Sale Work
The Founder List is useful when each tool has a clear job: the audience surface creates intent, Plandalf turns that intent into a configured offer, Stripe collects payment, and the follow-up tools receive the purchase context they need.
Where the buyer starts
Next.js owns the attention layer. Keep the editorial page, newsletter block, landing page, or product screen focused on why the buyer should act, then hand the buying decision to Plandalf Offers.
What the buyer is purchasing
Plandalf should own the offer, products, prices, checkout mode, coupons, order bumps, upsells, invoice settings, and confirmation behavior so Stripe is not the only durable record.
What happens after payment
The purchase event should drive fulfilment, receipts, lifecycle email, CRM updates, tax context, and reporting. Kit (ConvertKit) should receive commerce context instead of a bare form submission.
Choose The Pattern
Start by deciding which business moment you are building. The stack changes depending on whether checkout starts from a sales page, a launch campaign, an offer page, a checkout template, or an existing product catalog.
Sell from Next.js
Use when: Next.js already owns the audience, post, landing page, or storefront moment and only needs the checkout layer to open at the right time.
Build: Place the hosted page trigger beside the buying copy, point it at a Plandalf offer, and keep products, prices, coupons, invoices, and automations inside the offer record.
Package the commercial object
Use when: The business needs a clean product, price, bundle, cohort, download, membership, or service package before traffic reaches checkout.
Build: Create the product and price, attach conversion controls such as coupons, order bumps, and upsells, then make sure the invoice and fulfilment event carry the same line-item context.
Route the work after purchase
Use when: The checkout is only useful if the buyer gets access, receives the right receipt, lands in the correct sequence, and leaves a durable record for support.
Build: Use Plandalf Automations and sequences to send the purchase event into Kit (ConvertKit), while payment stays with Stripe.
Build The Offer Layer
The offer is the commercial object your product points at. It should describe what the buyer can purchase, how checkout appears, which price rules apply, what invoice gets recorded, and what automation happens after purchase.
Wire The Buying Moment
The stack should decide when the buyer is ready. Plandalf should decide what the checkout means. Keep the page, campaign, or offer focused on the buying moment, then let the offer carry the checkout mode, product, price, invoice, and automation context.
Plan The Data Contract
The useful part of a commerce stack is not the button. It is the agreement between the offer, Plandalf, the payment processor, and follow-up tools about which object owns each piece of commerce state.
Product Surfaces This Stack Depends On
These screenshots come from the product surfaces behind The Founder List. They show the Plandalf records and controls a builder should configure before sending buyers from Next.js into checkout.
Build Recipes
Use these like product-specific implementation notes: choose the selling moment, configure the Plandalf surface, then link into the exact features, integrations, sequences, and docs needed to ship it.
Publish a product-backed checkout from the sales surface
Outcome: Traffic starts where the buyer already is, while Plandalf owns the offer, checkout state, payment context, invoices, and follow-up event.
- Choose the page, post, template, or campaign that should create demand.
- Point its buying action at a Plandalf offer with products, prices, checkout templates, and payment options already configured.
- Preview the checkout surface before traffic reaches it.
- Verify the purchase event creates the expected invoice and fulfilment path.
Add conversion controls after the base checkout works
Outcome: Coupons, order bumps, upsells, and save offers stay attached to the offer instead of becoming scattered campaign code.
- Start with the base product and price so checkout is correct without extra controls.
- Add only the coupon, bump, upsell, or deadline control that fits the selling moment.
- Test the invoice and purchase event after each conversion control is added.
- Send the buyer into the correct automation or sequence after checkout completes.
Preserve the operational record
Outcome: Support, finance, fulfilment, and lifecycle tools can answer what happened after the buyer paid.
- Confirm the invoice settings, customer fields, and product line items before launch.
- Use purchase events or sequences for fulfilment instead of relying on the success screen.
- Route receipt, support, tax, and lifecycle work to the right downstream tools.
- Keep the adjacent stack links handy when the build needs tax, invoices, or webhook depth.
Compare The Pattern
A commerce stack is different from a processor-only checkout, a marketplace storefront, or a standalone funnel tool. Use these linked comparisons when a builder is deciding whether Plandalf Offers should sit between the sales surface, payment processor, and follow-up tools.
Plandalf vs Stripe Checkout
Compare with Stripe Checkout. Use this when you need Stripe payments plus offer configuration, invoices, post-purchase automation, and seller-operated checkout changes.
Plandalf vs Gumroad
Compare with Gumroad. Use this when your product already has its own app, catalog, customer identity, and fulfilment path instead of needing a marketplace-style checkout product.
Plandalf vs SamCart
Compare with SamCart. Use this when checkout needs offer automation, product context, invoices, and post-purchase workflows rather than a separate funnel tool beside the business.
Plandalf vs Shopify
Compare with Shopify. Use this when the business is selling software, access, templates, subscriptions, or services and does not need a full storefront catalog.
Linked Implementation Map
Use this map when The Founder List turns from an idea into implementation work. Every linked feature, integration, docs page, workflow, comparison, template, and tool is a next step a builder or agent can follow from this stack.
Product surfaces
Configure these Plandalf features before sending buyers into the stack.
Integrations
The tools that own the audience, payment, delivery, tax, CRM, or follow-up path.
Docs handoff
Move from stack planning into exact setup, SDK, API, and webhook reference pages.
Recipes and sequences
Use these when the sale needs fulfilment, lifecycle, webhook, or automation depth.
Comparisons
Decision pages for buyers choosing between Plandalf and narrower checkout, funnel, storefront, or automation tools.
Templates and tools
Adjacent pages that help turn the stack into an implementation plan.
Operational Recipes
These are the practical recipes a builder usually needs after the checkout opens. They stay product-level: Offers, Automations, integrations, invoices, sequences, and payment events explain the workflow before any tool-specific setup.
Send transactional receipts separately from lifecycle email
Trigger: Invoice or purchase recorded
Action: Kit (ConvertKit) handles receipts, while lifecycle tools handle onboarding and expansion.
Builder Checklist
Before shipping the integration, verify these decisions. If one is unclear, the checkout may open, but the business workflow after purchase will still be brittle.
02Identity mappedYour product can reconcile the buyer, customer, workspace, account, or entitlement after purchase.03Event path chosenFulfilment starts from a purchase event or sequence, not from a front-end success screen alone.04Records preservedInvoices, line items, payment state, and customer fields are available for support and reporting.Next Steps
Substack Shop
Sell a template, report, workshop, membership, or paid download from a Substack post while Plandalf owns the offer, checkout, invoice, and purchase event.
The API-First Product
Split transactional email from lifecycle email so each tool does what it's good at.
The Coach
Take deposits and recurring retainers without re-platforming your existing site.
The Newsletter Creator
Monetise an existing newsletter audience by selling one-off products from inside the same list tool.
The Affiliate Tax Launch
Connect affiliate sales, payment options, live tax calculation, and post-purchase reconciliation.
The Course Creator
Enrol each buyer into the right cohort sequence the moment they pay.