founder-ops

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

founder-ops

A plan that works on paper fails at 7am on a Monday. This skill makes sure the first day, week and month can actually be run, and that the CFO's numbers include what running it really costs.

纸面上可行的计划往往在周一早上7点就出问题。本技能确保业务的第一天、第一周、第一个月能够实际落地运行，且CFO的财务数据包含真实运营成本。

Step 1: what the business has to do every day

步骤1：业务每日必做事项

From

founder/idea.md

founder/offer.md

and

founder/numbers.json

, write the daily cycle as a list of steps from first thing to last (for a café: deliveries, prep, open, serve, clean, cash up, order; for an online store: orders in, pick, pack, ship, returns, support). Mark which steps a customer sees.

基于

founder/idea.md

、

founder/offer.md

和

founder/numbers.json

，将每日运营周期按从早到晚的顺序整理为步骤列表（以咖啡馆为例：收货、备餐、开店、接待顾客、清洁、营收结算、补货；以线上商店为例：订单接收、拣货、打包、发货、退换货、客户支持）。标记出哪些步骤是客户可见的。

Step 2: suppliers

步骤2：供应商

For every input in the CFO's variable costs and every piece of equipment: two or three real suppliers the user can contact, their public prices or how to get a quote, minimum orders, lead times and payment terms. Link the sources. Where only a quote will tell, say so and add it to the open questions. If a real price differs from

founder/numbers.json

, update it and say the CFO should re-run.

针对CFO可变成本中的每一项投入及每一件设备：提供2-3个用户可联系的真实供应商，列明其公开价格或报价获取方式、起订量、交货周期及付款条款。附上信息来源链接。若仅能通过报价获取价格，需明确说明并将其加入待解决问题清单。若实际价格与

founder/numbers.json

中的数据不符，更新该文件并告知CFO需重新核算。

Step 3: people

步骤3：人员配置

Who does what, when: a weekly rota for the planned volume and for the slow first month. The roles, the hours, and the wage assumption (from the user, or a public source for the local minimum and typical pay, linked). Payroll costs beyond wages vary by country; flag them for the accountant.

谁在什么时间做什么：分别针对计划业务量和首个业务清淡月制定每周排班表。包含岗位、工时及薪资假设（数据来自用户，或附链接的当地最低工资与普遍薪资公开来源）。工资以外的薪资成本因国家而异；需标记出来交由会计处理。

Step 4: routines (SOPs)

步骤4：例行流程（SOP）

Short, numbered routines for the moments that make or break the business: opening, the core service or fulfilment, handling a complaint, closing, and a weekly reorder. Each fits on one page someone could follow on their first day.

针对决定业务成败的关键场景制定简短的编号式SOP：开店、核心服务或订单履约、投诉处理、闭店，以及每周补货。每项SOP控制在一页内，新人第一天就能照着执行。

Step 5: tools

步骤5：工具

The smallest stack that runs it: payments, point of sale or store, scheduling, bookkeeping, inventory. Real products with their published prices, and why each.

支撑运营的最简工具栈：支付、POS系统/线上店铺、排班、记账、库存管理。列出具体的工具产品、公开定价及选型理由。

Step 6: licences, permits and insurance

步骤6：执照、许可与保险

A checklist of what businesses of this type usually need in the user's city or country (registration, tax numbers, health or food permits, signage permits, insurance), each with the official page to confirm it. Say plainly that rules differ by place and change, and the user must confirm each with the authority or a professional. Not legal advice.

一份清单，列明用户所在城市或国家的此类企业通常需要办理的事项（注册、税号、卫生/食品经营许可、招牌许可、保险），每项都附官方确认页面链接。需明确说明规则因地而异且会发生变化，用户必须向主管部门或专业人士确认每项内容。本内容不构成法律建议。

Step 7: risk register

步骤7：风险登记册

The ten things most likely to go wrong (a supplier runs out, a key person is sick, the card terminal fails, a bad review, a slow month), each with how likely, how bad, and the plan.

列出10项最可能出现的问题（供应商断货、核心员工生病、刷卡机故障、差评、单月业绩低迷），每项都标注发生概率、影响程度及应对方案。

Output

产出

founder/ops.md

, plus updated

founder/numbers.json

if real costs changed. Next:

/founder-launch

生成

founder/ops.md

文件，若实际成本有变动则同步更新

founder/numbers.json

。下一步：

/founder-launch

。