Projects / Website launch
A thoughtful launch.
One place for the brief, the next steps, and the decisions.
Goal
Launch a clear, useful home for our new product. Keep the first release focused.
Write the project briefDone
Review homepage copyIn progress
Prepare the launch checklistNext up
Launch briefLinked to this project
Start with the bigger picture.
A useful project has more than a title. Keep its goal, constraints, decisions, and next actions together so a collaborator or connected agent can understand what you are trying to do.
- Organize projects and tasks with statuses and relationships.
- See work in a list or board, and follow revision history.
- Add comments and corrections while preserving the original entries and author attribution.
- Keep separate workspaces for different groups of people.
Make room for the work that repeats.
Set up recurring tasks with a timezone, selected weekdays, and a time. Pause a schedule when plans change, and keep each occurrence’s completion history separate.
Reminders go to the schedule owner’s verified email. Scheduled work is processed in the background; it does not wake an external AI agent or send a message into its chat.
Keep the source within reach.
Use comments for project and task updates, decisions, and history. Write editable library notes for briefs, plans, and reusable references. Keep original attachments and exports as files.
Track a useful link once and attach it to multiple projects or tasks. Keep personal and work accounts distinct, and use explicit sender or thread rules to find related records already tracked in the workspace.
With a connected Google account, create plain-text Google Docs and export supported files to a tracked PDF in Drive. Optionally enable Gmail matching to import the subject, sender, thread ID, and link for messages that match saved sender or thread rules. Message bodies and attachments are not imported.
Archiving a resource in MCPBinder and moving its original file to Google trash are separate actions. Your workspace should make that distinction clear.
Explore Google DriveLet agents work with the same context.
Compatible clients connect through a remote MCP endpoint. You choose the workspace, allowed projects, connected accounts, and actions. Agents use the same checked services as the web app.
Choose read and propose permissions when you want a person to review suggestions. Direct editing permissions allow direct changes; review is not automatically required for every action.
Understand agent permissions