One-Pilot Solo Company Cockpit

The Problem

A solo company often handles business judgment, task execution, cash tracking, scheduling, and health maintenance at the same time. These states usually scatter across chats, spreadsheets, calendars, and notes. One-Pilot keeps them in a small set of local Markdown files and updates them through natural language, instead of asking the user to maintain multiple systems by hand.

How It Works

• Local data model: directions, actions, finance, schedule, health, and relationships live in directions.md, actions.md, finance.md, schedule.md, health.md, and relationships.md.
• Industry templates: it can start from self-media, ecommerce, consulting, education, creator/streamer, or general templates, loading preset directions and dedicated files.
• Cross-domain updates: finishing an action can write linked income to finance.md, release time blocks in schedule.md, and update actual duration.
• Proactive alerts: overdue tasks, budget use, cash flow, health load, client follow-ups, and system expirations can trigger reminders.
• Natural language and commands: it supports phrases for logging expenses, scheduling meetings, and creating batch health tasks, plus quick checks such as /finance, /health, and /schedule.

Boundaries

It is useful for making solo business operations into a local, reviewable state machine, but it does not replace banking, calendar, health-device, or project-management tools. External integrations often depend on user-provided API credentials, intelligent suggestions still need human confirmation, and sensitive data in ~/onepilot/ should be backed up regularly.