What’s inside

One SKILL.md (the playbook) + one starter template. A preview:

Loopwise SaaS Landing

When to use

• Your SaaS product's value is a repeating cycle — a workflow that runs daily, weekly, or per event — and a feature-list landing page makes it look like a static tool
• Visitors understand your features but still ask "so what does it actually do for me every day?" — the loop answers that question
• You are launching an automation, monitoring, reporting, or feedback product where the magic is iteration, not a single action
• Your current page lists features in no particular order, and prospects bounce because they can't picture the product in their routine
• You need pricing that maps to how customers actually use the product — per loop, per cycle, per run — and the page must explain that mapping

Workflow

1. Name the loop (input: product behavior + customer interviews → output: loop definition)
   Write the loop in one sentence: "Every time {trigger} happens, the product {does X}, which produces {outcome}, which feeds back into {next trigger}." The trigger must be a real event in the customer's world (a new signup, a deploy, a Monday morning), not a product action. If you can't name the trigger, you don't have a loop yet — you have a feature list, and this skill will not save it. Get the loop sentence approved by someone who talks to customers before building anything.
2. Tell one loop, end to end (input: loop definition → output: hero story)
   The hero tells a single pass through the loop with a real example: a named trigger, the product's actions in order, the concrete outcome, and the feedback that starts the next pass. Use real numbers from a real customer or from your own dogfooding — "every Monday, it reconciles 400 invoices in 9 minutes and flags 3 for review" beats "automates your workflow." The hero's headline names the loop's outcome, not the product's category. One loop, told completely, earns the scroll; a feature grid does not.
3. Expand each loop stage into a section (input: hero story → output: section drafts)
   Give each stage of the loop its own section, in loop order: the trigger stage (how the product notices), the action stage (what it does, with a screenshot of that exact moment), the outcome stage (what the customer sees, with the real result), and the feedback stage (how the result improves the next pass). Each section answers one question: "what happens here, and how do I know it worked?" Keep each section to one screenshot, one short paragraph, and one proof line. The page's order is the loop's order — never reorder sections for visual variety.

Template preview

Loopwise SaaS Landing — Page Template

One page, one loop. Name the loop first — if the loop sentence isn't real, don't build the page.

Loop definition

One sentence: Every time {trigger in the customer's world}, the product {does X}, which produces {outcome}, which feeds back into {next trigger}.

Trigger: {real event} | Product action: {steps in order} | Outcome: {concrete result} | Feedback: {how the outcome improves the next pass}

Hero story (one complete loop pass)

Headline (names the outcome): {one line} The loop, told: {trigger → actions → outcome → feedback, with real numbers from {real customer / own dogfooding}}

Buy the full skill pack — $4.99 Pro — all 471 skills