Out-launch a new launch within its first 24 hours

Each hour, read every launch place the person watches (rows of their Sources I watch list, read by tool:watch-my-sources: Show HN, Product Hunt and Launch YC start there turned off, and a launch newsletter or any other launch feed is a row they add) for products that launched in the last 24 hours; keep the ones whose own pages compete for the person's buyers; reverse engineer each from public evidence within hours, every finding SEEN or INFERRED, and keep the teardown as a row of the person's Library list; draft a counter-launch from its gaps and the person's own proof and get the person's approval; then hand it to the person's marketing workflows (a launch record that starts workflow:plan-a-launch-as-a-content-campaign) to out-launch it. Target: handed off within 1 hour of the launch, and always within 24 hours, measured per launch. Nobody is contacted, no account is made, and nothing goes out without the person's approval.

What it asks for

  • store (Needed, details):
  • market (Needed, words): What the person sells and to whom, in their own words; a launch counts only when its own page overlaps it
  • licence (Optional, words): The licence the person shares their teardowns under, kept in the Licence column of each teardown's Library row (a licence name such as CC-BY-4.0, or unknown)
  • sources (Optional, list): The ids of the rows of the person's Sources I watch list that are launch places; every source tool:watch-my-sources read when left out
  • channels (Needed, list): The platforms and owned channels the person posts on, handed to workflow:plan-a-launch-as-a-content-campaign
  • match_words (Optional, list): Words a launch's own words must hold to be read further (a category, a job the product does); every launch is weighed against market when left out
  • own_product (Optional, words): The person's own product: its address or the id of its record, so the counter-launch is built from what it really does
  • target_hours (Optional, number): The hours after a launch by which its hand-off should be done (1 when left out)
  • deadline_hours (Optional, number): The hours after a launch by which its hand-off must be done (24 when left out, never more)

The steps your AI walks

  1. Read what launched in the last 24 hours from every launch place the person watches
  2. Keep only the launches that compete for the person's buyers
  3. Reverse engineer each match within hours and keep it as a Library row
  4. Draft the counter-launch that out-launches it, and get the person's approval
  5. Hand each approved counter-launch to the marketing workflows
  6. Measure each launch against its 1-hour target and 24-hour deadline

Use it from your AI

Connect the AI you already use to Trillion once. Then ask in your own words; your AI finds this workflow by what it does and runs it.

Say to your AI: “Use Trillion to each hour, read every launch place the person watches (rows of their Sources I watch list, read by tool:watch-my-sources: Show HN, Product Hunt and Launch YC start there turned off, and a launch newsletter or any other launch feed is a row they add) for products that launched in the last 24 hours; keep the ones whose own pages compete for the person's buyers; reverse engineer each from public evidence within hours, every finding SEEN or INFERRED, and keep the teardown as a row of the person's Library list; draft a counter-launch from its gaps and the person's own proof and get the person's approval; then hand it to the person's marketing workflows (a launch record that starts workflow:plan-a-launch-as-a-content-campaign) to out-launch it. Target: handed off within 1 hour of the launch, and always within 24 hours, measured per launch. Nobody is contacted, no account is made, and nothing goes out without the person's approval”