Loading…
pilotdesk.example
This example shows the real shape of the Founder AI chief of staff. It is written so a busy owner can understand it fast.
Who this is for
A founder who needs fewer dropped balls each day.
Who gets helped
The founder and team members who need clear priorities.
Main problem
Inbox, calendar, follow-ups, and reports are scattered everywhere.
Daily brief, inbox rules, CRM follow-ups, meeting notes, and weekly report.
The client does not get a box of tools. The client gets a working set of pages, guides, rules, and proof screens that solve the problem.
The customer fills out one short form.
The system builds the pages, rules, reports, and handoffs.
The client opens this website and sees the finished work.
The team follows the guide and uses the first deliverable.
The report shows what changed and what to improve next.
Collect the business, audience, offer, rules, and success goal.
Create every selected page, workflow, guide, and report.
Publish the client site and show what is ready now.
Give the team simple steps for using the system.
Track the result the client paid for.
Each item below is something the client can open, use, send, review, or measure. The words are simple on purpose.
Priorities, communication style, escalation rules, decision preferences, and protected-time rules.
How to use it: This is the main place where the finished work is shown and used.
Open this deliverable pageUrgent, reply-needed, delegate, wait, archive, sales, support, finance, and personal categories.
How to use it: This is the rule or message path that runs the work the same way each time.
Open this deliverable pageScheduling, prep notes, reminders, follow-ups, and conflict handling.
How to use it: This is the rule or message path that runs the work the same way each time.
Open this deliverable pageAt-risk leads, overdue follow-ups, next-step suggestions, and owner notifications.
How to use it: The team uses this to know what to check and what to do next.
Open this deliverable pageMorning summary of urgent items, calendar, blocked decisions, follow-ups, and recommended actions.
How to use it: This proves what happened and whether the result is improving.
Open this deliverable pageSales, support, content, operations, risk, and open-loop summary.
How to use it: This proves what happened and whether the result is improving.
Open this deliverable pageRules for creating tasks, assigning owners, due dates, and follow-up checks.
How to use it: This is the rule or message path that runs the work the same way each time.
Open this deliverable pageActions allowed automatically, actions requiring approval, and actions never allowed.
How to use it: The team uses this to know what to check and what to do next.
Open this deliverable pageMake sure this says it is for busy founders and small teams. If the market is wrong, fix the intake before using the system.
The promised result is: Daily brief, inbox rules, CRM follow-ups, meeting notes, and weekly report. This is what the client should expect to receive.
Start with "Founder operating profile." It tells the team where to begin.
Do the steps in order: intake, build, launch, use, then prove. Do not skip the proof step.
Look at Daily priority brief. It shows what worked, what is blocked, and what to fix next.
Use this before the client calls the work finished.