1,599 件 ・ 関連度順
概要と使いどころ
Design or review annual operating budget — headcount plan, departmental spending, revenue targets, and variance tracking. Use when asked to "build our budget", "plan headcount for next year", or "review our spending".
日本語の概要は準備中です。原文の説明を表示しています。
Generate financial reports — monthly close package, variance analysis, and management reporting. Use when asked to "generate monthly financials", "close the books", or "write variance commentary".
日本語の概要は準備中です。原文の説明を表示しています。
Calculate and extend runway — current cash, burn rate, runway months, and the levers available to extend it. Use when asked to "how long is our runway", "when do we run out of money", or "what cuts extend runway by 6 months".
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit a financial model — 3-statement model (P&L, cash flow, balance sheet), scenario analysis, and sensitivity tables. Use when asked to "build a financial model", "model our growth scenarios", or "what happens to runway if we hire 5 people".
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve unit economics — LTV, CAC, payback period, gross margin, contribution margin. Use when asked to "are our unit economics good", "what is our LTV/CAC", or "how do we improve gross margin".
日本語の概要は準備中です。原文の説明を表示しています。
Prepare fundraising financial materials — investor model, data room financial docs, cap table, and use-of-funds narrative. Use when asked to "prepare for Series A", "build our investor model", or "what financials do investors want".
日本語の概要は準備中です。原文の説明を表示しています。
Financial reconnaissance — audit current P&L, burn rate, runway, unit economics, and financial health to understand where the constraint is. Use when asked to "audit our finances", "what is our runway", "are our unit economics healthy", or "before building a financial model".
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit compliance program — SOC2, GDPR, HIPAA, or ISO 27001 readiness assessment, gap analysis, and remediation roadmap. Use when asked to "do we need SOC2", "are we GDPR compliant", "what does our compliance program need", or "build a security policy".
日本語の概要は準備中です。原文の説明を表示しています。
Design and run OKR program — company objectives, team key results, cascade design, and quarterly review cadence. Use when asked to "design our OKRs", "are our OKRs good", "cascade goals to teams", or "run a quarterly OKR review".
日本語の概要は準備中です。原文の説明を表示しています。
Design meeting and communication cadence — what meetings to run, how often, who attends, and what decisions they make. Use when asked to "design our meeting structure", "what meetings should we have", "reduce meeting load", or "build our operating rhythm".
日本語の概要は準備中です。原文の説明を表示しています。
Document or redesign a business process — standard operating procedure (SOP), process map, RACI, and owner assignment. Use when asked to "document this process", "write a runbook", "design how we handle X", or "map the process for Y".
日本語の概要は準備中です。原文の説明を表示しています。
Manage vendor relationships — vendor selection scorecard, contract review checklist, renewal tracking, and vendor consolidation audit. Use when asked to "evaluate this vendor", "review this contract", "track vendor renewals", or "reduce our SaaS spend".
日本語の概要は準備中です。原文の説明を表示しています。
Draft or review legal ops documents — NDA, MSA, SaaS agreement review checklist, vendor contract terms. Use when asked to "review this contract", "draft an NDA", "what should I look for in this agreement", or "build our contract review process".
日本語の概要は準備中です。原文の説明を表示しています。
Design performance management system - review cycles, calibration process, career ladder, and PIP framework. Use when asked to "build a performance review process", "design career levels", "how do we handle underperformers", or "run a review cycle".
日本語の概要は準備中です。原文の説明を表示しています。
People reconnaissance - audit org design, hiring pipeline, comp structure, onboarding, and performance systems to understand what is working and where the constraint is. Use when asked to "audit our people ops", "what is broken in our hiring", "review our org structure", or "before designing a comp framework".
日本語の概要は準備中です。原文の説明を表示しています。
Build onboarding playbook - day 1 through week 4 checklist, access provisioning, context transfer, and success milestones. Use when asked to "build an onboarding process", "how do we onboard new hires", or "reduce time to productivity for new joiners".
日本語の概要は準備中です。原文の説明を表示しています。
Run human-to-agent migration - audit which roles can be agent-assisted or replaced, design the transition playbook, and manage the offboarding of displaced roles. Use when asked to "which roles can agents replace", "how do we transition to AI-first ops", or "build our agent migration plan".
日本語の概要は準備中です。原文の説明を表示しています。
Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".
日本語の概要は準備中です。原文の説明を表示しています。
Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
日本語の概要は準備中です。原文の説明を表示しています。
Document and strengthen company culture - values articulation, team norms, communication protocols, and culture health diagnostics. Use when asked to "define our values", "document how we work", "diagnose culture health", or "write team norms".
日本語の概要は準備中です。原文の説明を表示しています。
Design compensation framework - salary bands, equity philosophy, offer templates, and total comp benchmarking. Use when asked to "design our comp bands", "how much equity should we give", "is our comp competitive", or "write an offer template".
日本語の概要は準備中です。原文の説明を表示しています。
Write support playbook -- response templates, issue-type runbooks, tone guide, and common resolution paths. Use when asked to "write support templates", "build a support playbook", "train our support agents", or "standardize our support responses".
日本語の概要は準備中です。原文の説明を表示しています。
Design SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".
日本語の概要は準備中です。原文の説明を表示しています。
Design escalation path -- Tier 1 to Tier 2 to Engineering handoff, decision criteria, and communication templates. Use when asked to "design our escalation process", "when should support escalate to engineering", "build an escalation runbook", or "reduce escalation rate".
日本語の概要は準備中です。原文の説明を表示しています。