Build an application. Shape a campaign. Investigate a question. Give your AI team a clear outcome, the tools it needs and criteria an independent reviewer can check.
Choose a website launch, marketing campaign or research report. Edit its brief and acceptance checks, then explicitly accept the agreement. The office prepares draft tasks, owners, independent reviewers and the order of work.
Playbook v1
Website launch
Research, content and design feed an implemented website, followed by a release handoff. Publishing remains a separately authorized action.
See the work and its reviewers
Audience and site brief
research analyst → analyst review · document handoff
Build an evidence-based campaign package with audience research, strategy, creative, copy and measurement. Account actions and spending still require their own access and approval.
See the work and its reviewers
Audience and evidence
research analyst → analyst review · document handoff
Assign the available team and review the project workflow. It checks the agreement, people, permissions, model configuration, allowances and required repository or runner before you queue work.
Handoffs carry evidence.
Downstream employees receive accepted prerequisite documents after their checksums are checked. Missing, changed or oversized material stops the handoff. Code is identified by its accepted commit and must be inspected in the repository.
When the agreement changes, review how its current criteria map to the existing playbook steps and explicitly approve the revised plan. History stays intact, while steps return to draft for fresh work and review. Active attempts must settle first; starting the revised drafts is a separate action.
Preparing a workflow does not call a model, grant tools or hire employees. A configured credential is setup evidence, not a successful provider request. Follow the workflow setup →
Choose the handoff
Code, documents and evidence.
01 / Repository delivery
Files that run.
Employees work in a repository, submit a pinned commit and receive independent review. Accepted changes can integrate into the project branch. This suits applications, scripts and executable pipelines.
Building, signing, device testing and deployment depend on the actual runtime, hardware, credentials and tools available.
02 / Document delivery
Work you can read and use.
Employees produce complete written deliverables saved with a checksum. A different employee reviews the saved output against the current criteria. This suits research, plans, copy, specifications and operating procedures.
A written design specification is not a native design file. Canva or other asset creation requires an authorized tool connection and a recorded result.
A mixed project combines both formats. Research, copy and design can produce reviewed documents while implementation produces code; each task declares its own format and discipline. Every completed task still needs independent review.
The project type suggests a delivery method; you can change it. Expected outputs and acceptance criteria remain editable. Suggestions enter your agreement only when you deliberately add them. See the project controls →
Start with the outcome
Find the shape of your project.
01Repository suggested
Website
Public websites, landing pages and content sites.
Example outputs
Website source and responsive pages
Content and accessibility review
Build and hosting instructions
What a reviewer could check
The agreed pages contain approved content and working navigation
The layout remains usable on the agreed mobile and desktop sizes
The delivery includes reproducible build instructions and states which checks ran
What this work needs
An accessible repository and required build tools
Approved brand assets, content and licensed media
Hosting and domain access if publishing is part of the approved scope
02Repository suggested
Web application
Browser applications with user flows, services and data.
Example outputs
Application source and database changes
Tests for the agreed user journeys
Setup and deployment notes
What a reviewer could check
Each agreed user journey works with representative test data
Access rules and error states are verified against the requirements
Setup instructions describe configuration and checks actually performed
What this work needs
A repository, runtime and test database
Test accounts and permission to use required services
A hosting environment for deployment; production changes need explicit authorization
03Repository suggested
Mobile application
Android, iOS or cross-platform application work.
Example outputs
Mobile application source
Build and device test evidence
Signing and store submission checklist
What a reviewer could check
The agreed flows are implemented for the specified platforms
The handoff distinguishes device-tested behavior from untested behavior
Build and release instructions name outstanding signing or store requirements
What this work needs
The chosen mobile SDK and supported build host; iOS builds require macOS and Xcode
A compatible emulator or physical device for device-level verification
Owner-controlled signing certificates and store accounts for release; no store approval is guaranteed
04Repository suggested
Desktop application
Applications and utilities for specified desktop operating systems.
Example outputs
Application source
Platform build or packaging instructions
Installation and smoke-test evidence
What a reviewer could check
The agreed functions are implemented on the named operating systems
Installation and error handling are checked where a compatible host is available
The handoff identifies untested platforms and signing prerequisites
What this work needs
Compatible operating systems, runtimes and packaging tools
A test host for each supported platform
Owner-provided signing or notarization access when distribution requires it
05Repository suggested
API and integration
Service endpoints, webhooks and connections between systems.
Example outputs
API or integration source
Interface documentation and examples
Authentication and failure-path tests
What a reviewer could check
The implemented request and response contracts match the agreed specification
Authentication, validation and retry behavior have documented evidence
Examples and setup instructions identify external service dependencies
What this work needs
Repository and service runtime
Authorized test endpoints, credentials and representative payloads
Explicit access to external systems; credentials are not supplied by the project type
06Repository suggested
Automation
Repeatable scripts, scheduled processes and assisted business workflows.
Example outputs
Automation scripts or workflow configuration
Dry-run evidence
Operating and recovery instructions
What a reviewer could check
The workflow handles the agreed inputs without duplicating side effects
Failure, retry and recovery behavior are documented and tested where possible
The handoff identifies every external action that still needs approval or credentials
What this work needs
A supported runtime and permission to access target systems
Safe test inputs and an agreed schedule
External tools or MCP connections must be configured separately; no physical tasks are performed
07Document suggested
Data and analysis
Data exploration, analysis reports and reproducible transformations.
Example outputs
Analysis report with methods and limitations
Tables and metric definitions
Reproducible transformation plan or repository code
What a reviewer could check
Every reported metric identifies its source, period and calculation
Missing data, assumptions and uncertainty are stated
The conclusions follow from the supplied evidence and avoid unsupported causal claims
What this work needs
Authorized datasets with a documented meaning and permitted use
Readable data or configured analysis tools; a narrative report does not execute a notebook
Use repository delivery for executable pipelines and arrange the required runtime
08Document suggested
Marketing and SEO
Positioning, campaign plans, channel strategy and SEO recommendations.
Example outputs
Audience and positioning brief
Campaign or SEO action plan
Measurement plan and content calendar
What a reviewer could check
The plan connects the target audience, offer, channels and measurable objective
Recommendations cite supplied evidence and distinguish assumptions
The plan identifies budget, approvals and account access required before launch
What this work needs
A product brief, audience and business objectives
Authorized analytics or research sources for evidence-based recommendations
Ad spending, outreach and publishing require separately configured access and approval
09Document suggested
Content and communications
Articles, copy, scripts, editorial calendars and business communications.
Example outputs
Editable copy or script
Editorial outline and source notes
Publication checklist
What a reviewer could check
The content follows the agreed audience, purpose, format and tone
Factual claims are supported or clearly marked for verification
The handoff includes the requested variants and remaining publication decisions
What this work needs
Approved facts, brand guidance and source material
Permission to use supplied text and media
Publishing and sending to other people require separate approval and access
10Document suggested
Design and creative
Brand directions, UX specifications, design briefs and tool-assisted assets.
Example outputs
Design brief and visual direction
Screen or asset specifications
Editable asset links when an authorized design tool is connected
What a reviewer could check
The design direction addresses the agreed audience, use and brand constraints
The handoff specifies layout, content, accessibility and export requirements
Produced assets are distinguished from specifications and linked only when actually created
What this work needs
Brand assets, dimensions, reference material and usage rights
Canva or another design tool needs an authorized connection and supported actions for native assets
Document delivery alone produces a written handoff, not a guaranteed image, video or editable design file
11Document suggested
Research and strategy
Evidence summaries, comparisons, feasibility assessments and decision briefs.
Example outputs
Research brief with source references
Options and tradeoff comparison
Recommendations with uncertainty and next steps
What a reviewer could check
The report answers the agreed question and identifies the sources available to it
Facts, inferences and unresolved questions are separated
Recommendations follow from the evidence and state their practical limits
What this work needs
A defined question, decision context and permitted source material
A configured research connection for live sources; model recall is not current verification
Human expert review for decisions requiring professional judgment
12Document suggested
Business operations
Operating procedures, process analysis, plans and internal documentation.
Example outputs
Operating procedure or process map
Action plan with owners and dependencies
Templates and decision log
What a reviewer could check
The procedure defines inputs, responsible people, steps and expected outputs
Exceptions, dependencies and approval points are documented
Recommendations distinguish proposed changes from actions actually taken
What this work needs
The current process, responsible people and business constraints
Authorized records and separately configured tools for actions in other systems
Physical operations, legal signatures and financial commitments remain human responsibilities
13Document suggested
Custom solution
A scoped combination of disciplines defined by your brief.
Example outputs
The outputs explicitly agreed in the brief
Evidence and handoff instructions
Dependencies and remaining decisions
What a reviewer could check
The deliverable addresses each agreed requirement
Claims identify evidence, assumptions and any work that could not be performed
The handoff identifies how to use the result and what remains for the operator
What this work needs
A clear scope and an agreed delivery format
The tools, data, accounts and runtime the work actually requires
Unsupported or physical actions are reported as limitations, not represented as completed
Consistency across the work
One brand. Clear decisions.
Publish client brand guidance.
Record logo and asset references, colors, typography, tone, approved product facts, claims to avoid and usage rights. Review the saved draft, then publish an immutable revision.
Each project chooses an exact client revision. New kit releases do not change existing selections; once work is queued under an agreement, changing its brand guidance requires a new contract version.
Put copy, channels, planned dates and project evidence on a content calendar. Approve the saved revision for handoff. Every edit creates a new draft, while the earlier wording and approval remain visible.
Record outcomes from real sources with a value, unit and measurement period. Entries are labeled operator reported; mistakes can be voided with a reason. The office does not infer return on investment or claim a campaign caused a result.
Brand links are not fetched automatically. A content approval is not publication, an email send or permission to spend on advertising.
A practical handoff
Take reviewed documents with you.
Download supported written evidence as PDF, Word, Excel or PowerPoint. Convert text, headings, lists and tables while retaining the original source checksum separately from the exported file checksum.
PDF
A portable rendering of the written source.
Word
An editable document for further human work.
Excel
Supported source tables in a workbook, without executable formulas or macros.
PowerPoint
A text and table presentation based on the source structure.
Exports are alternate renderings, not a new acceptance decision. Images and links remain references. Native Canva assets, rendered video, deployed sites and signed applications require the relevant tools and evidence that those actions succeeded.
The template brings engineering, leadership, platform, marketing, creative, research, operations, client services, people and finance into one company.
New roles include a Chief Marketing Officer, Marketing Strategist, Content Writer, Designer, SEO Specialist, Research Analyst, Data Analyst and Business Operations Specialist. An existing company adds missing roles deliberately; a migration does not start new employees working.
See the current agreement, independent acceptance evidence and local checks of accepted document or commit pins. Missing or changed sources and incomplete checks remain visible. Download the handoff as Markdown.
Recorded deployment, actual limits.
Compare accepted pins with deployment records and their last health observations. A matching reference does not prove the version served by a live host. Earlier accepted pins are recovery references, not a tested rollback plan.
Opening the handoff checks local sources. It does not publish, run a new HTTP check or roll back a system. Release access, backups, signing, review and the actual action remain separate steps.
It does not install a mobile SDK, connect an account, publish a campaign or operate physical equipment. The team must use available capabilities, report missing prerequisites and distinguish proposed actions from completed work. External approvals, app-store decisions and business results are not guaranteed.
Nucovo