Haggle Bot for procurement (idle seats, price comparison, negotiation prep)
让 Bot 找出没人用的订阅席位。 Let a bot find the seats nobody uses.
SpaceXAI 2026-09-04 官方文章：他们做了一只叫 Haggle Bot 的采购 Bot，接上 Slack、Notion、Drive、Gmail、Hex 和 Ramp，先摸清约 125 家在用供应商。例子：某个软件 43 个付费席位 90 天没人用，退掉省 $14,220；另一个按月付费的软件找出每年 $85,662 的闲置项；续约时比较几家替代品、算出筹码再起草回信；每周新员工物品订单在 Amazon、Costco、Uline、Walmart 间比价，结果写进可改的表格。文中给出完整设定文模板：哪些事可以直接做、哪些每次都要你点头、哪些绝对不做（签约、下单、付款）。官方称累计找出超过 $100,000 的直接节省。 Official SpaceXAI post, Sep 4, 2026: a procurement bot called Haggle Bot, connected to Slack, Notion, Drive, Gmail, Hex, and Ramp, first mapped about 125 active vendors. Examples: 43 paid seats idle for 90 days on one product ($14,220 saved), $85,662 a year of unused SKUs on a month-to-month product, renewal research that priced alternatives and drafted a counteroffer, and weekly new-hire supply orders shopped across Amazon, Costco, Uline, and Walmart into an editable sheet. The post shares a full instruction template with three permission lines: always allowed, needs the operator’s go every time, never (signing, buying, approving charges). SpaceXAI reports more than $100,000 in direct savings.
为什么推荐Why we recommend it 官方 News（2026-09-04），早间页面 200。收录理由：设定文模板把「能做、要批、绝不做」三条线写得很清楚，小公司查闲置订阅也能直接套。边界：节省金额是官方自报，本库无法核实；需要能读到账单和席位使用数据。本库未实测。 Official News (Sep 4, 2026), page returned 200 this morning. Why listed: the template draws clear lines between allowed, needs-approval, and never, and a small company can reuse it to find idle subscriptions. Boundary: savings figures are self-reported and not verified here; you need access to billing and seat-usage data. Not tested here.
查数据、问同事、整理档案可以自动；给供应商发信每次都要批；签约、下单、付款一律不做。 Reading data, asking colleagues, and keeping dossiers can run on their own; every vendor-facing send needs approval; signing, buying, and paying are never allowed.
先在可撤回、不外发的范围内试跑。本条未批准前：查数据、问同事、整理档案可以自动；给供应商发信每次都要批；签约、下单、付款一律不做。。 Try it first in a reversible, non-outbound scope. Until approved: Reading data, asking colleagues, and keeping dossiers can run on their own; every vendor-facing send needs approval; signing, buying, and paying are never allowed..
把跑通的步骤存成 Skill，下次同类任务直接复用，而不是重新口述。 Save the working steps as a Skill so the next similar job reuses them instead of being re-explained.
确认输出可靠后，再考虑定时或事件触发；例行默认仍应停在待审。 After output is reliable, consider a schedule or event trigger. Routines should still stop at review by default.
