Read signed scope
Use the client record, proposal, service selection, and sales notes as approved evidence of what was sold.
Client Delivery Agent for Notion
Signed scope. Kickoff ready.
Close the client. Your delivery agent takes it from there.
ClientFlow reads the signed scope, applies your approved service playbook, identifies missing inputs, and prepares the complete Notion delivery workspace - reviewed before execution and monitored through kickoff.
Scopeunderstood
Playbookapplied
Planapproved
Receiptcreated
For agencies
A signed client should not start with a manual reconstruction of your process.
Sales closes the deal. Then someone duplicates a project, renames pages, assigns owners, calculates dates, requests access, and checks that nothing was missed. The result depends on whoever performs the handoff.
Scope evidenceProposal, service field, sales notes
Plan prepared2 projects, 31 tasks, recurring reviews
Owners resolvedSarah, Analytics, Content
Access requestSearch Console required before kickoff
ApprovalOperations reviews before writes
Delivery ReceiptStored after execution
How it works
From signed scope to Kickoff Ready.
Agent reasoning proposes the work. ClientFlow validates, governs, and executes it through deterministic controls.
Apply the playbook
Select the correct published service version, apply conditional branches, and detect missing or conflicting information.
Preview the plan
Review every project, task, owner, date, dependency, access request, recurring deliverable, and external action.
Deploy safely
Provision the workspace through deterministic, replay-safe execution after the configured approval policy is satisfied.
Reach Kickoff Ready
Keep missing access, documents, decisions, and approvals visible until the client is genuinely ready to begin.
A signed client starts with manual reconstruction.
- Someone duplicates projects
- Dates and owners are recalculated
- Access requests are easy to miss
- Founder review stays necessary
Every client starts complete, consistent, and ready.
- Approved playbook applied
- Missing inputs visible
- Plan approved before writes
- Delivery Receipt stored
Actual product flow
One signed client, shown through the real interface.
Northstar Studio signs an SEO retainer. ClientFlow reads the handoff, applies the playbook, flags missing access, previews the plan, writes approved Notion pages, and leaves a Delivery Receipt.
Kickoff readiness
Conditionally Ready
31tasks
1blocking input
v4playbook
Platform relationship
Notion gives you agents. ClientFlow gives them your delivery system.
Notion provides the workspace, context, triggers, and agent runtime. ClientFlow provides the agency playbooks, scope rules, approval policy, deterministic execution, safe recovery, and delivery outcome reporting.
CapabilityGeneric Notion AgentClientFlow Delivery Agent
Read workspace contextYesYes
Run on triggers and schedulesYesYes
Create pages and tasksYesYes
Understand agency service structuresMust be configuredProductized playbooks
Convert signed scope into a governed planCustom buildBuilt in
Use versioned service playbooksManual designBuilt in
Validate the complete workspace graphCustom logicBuilt in
Preview the full delivery transactionGeneral activity reviewBuilt in
Recover partial provisioning safelyCustom developmentBuilt in
Track kickoff readinessMust be designedBuilt in
Manage many customer workspacesWorkspace-specificPartner path
Playbooks and proof
A playbook is more than a task template.
ClientFlow packages service knowledge into required inputs, role rules, dependencies, approval gates, recurring deliverables, readiness checks, and receipts.
Client context, databases, docs
Starts the client preparation job
Playbooks, policies, preview, recovery
Plan hash and exception review
Deterministic Notion writes
Readiness result and evidence
Example
Northstar Studio signs an SEO retainer.
ClientFlow reads the scope, selects the approved playbook, finds one missing access requirement, prepares the delivery plan, asks for approval, provisions the workspace, and stores a Delivery Receipt.
- Scope readSEO retainer, July kickoff, Sarah as account owner
- Missing input foundSearch Console access is required before kickoff
- Plan prepared2 projects, 31 tasks, owners, dates, recurring reviews
- Approval requiredOperations reviews the full plan before production writes
- Receipt createdClient is conditionally ready until access is granted
Outcome case
Every client starts complete, consistent, and ready.
Time savings are supporting evidence. The bigger case is fewer missed inputs, fewer kickoff delays, fewer founder reviews, and a higher percentage of on-time first deliverables.
Reconstruction avoided9.2 hours/month
Equivalent value$1,146/month
Annual savings$13,752/year
Studio subscription-$1,188/year
Net after Studio$12,564/year
ROI multiple11.6x Studio plan
Payback time3 days
Notion launch package
Built for Marketplace review and template distribution.
The connection now has the public pages Notion reviewers and customers expect: install, support, privacy, security, template, and a concrete receipt artifact.
Roadmap alignment
Founding pilots follow the product gates.
ClientFlow is not being launched as a broad self-serve automation builder. The pilot starts with the proven setup surfaces and moves into supervised execution only as the roadmap gates close.
NowPrivate pilot
Foundation and proof
- Verified account and Notion connection path
- Workspace mapping, schema validation, playbooks, and preview
- Seeded Northstar demo for buyer review and QA
NextPilot gate
Production execution
- Polling, matching, and replay-safe Notion writes
- Owner resolution, source stamping, and Delivery Receipts
- Recurring deliverable top-up with durable run history
LaunchRelease gate
20-minute first run
- Resumable onboarding from signup to activated rule
- Plain-language error UX, schema drift recovery, and usage meter
- Staging E2E plus stopwatch acceptance before broader rollout
LaterPost-v1
Agent and partner scale
- Notion agent and MCP packaging where customer plans support it
- Reusable consultant playbooks across customer workspaces
- Readiness analytics, margin controls, and governance reporting
Founding pilot and pricing
Start service-led, then scale into product.
The first offer is a done-for-you implementation against one real service line. Self-serve tiers are roadmap tiers, and Notion subscription, Notion AI credits, and third-party tools are separate from ClientFlow fees.
$750/mo
One done-for-you agency deployment.
$99/month begins after the first successful supervised run. Notion plan and credits are separate.- Workspace assessment
- One production service playbook
- One supervised pilot run
$49/mo
Small teams without Custom Agents.
One workspace, one active playbook, direct Notion trigger, preview approval, and Delivery Receipts.- One active playbook
- Preview and approval
- Limited monthly runs
$149/mo
Agencies using supported Notion agent plans.
ClientFlow Agent/MCP path, scope interpretation, missing-input detection, approvals, replay, and readiness.- Two workspaces
- Three active playbooks
- Readiness monitor
$299/mo
Established delivery organizations.
More workspaces and playbooks, team approval policies, governance, reporting, and priority support.- Team approval policies
- Playbook governance
- Advanced readiness reporting
Security and reliability
Enterprise buyers need architecture, not reassurance.
ClientFlow documents OAuth lifecycle, encrypted vault storage, tenant isolation, durable execution, Delivery Receipts, backups, incident response, and the roadmap to SOC 2 readiness.
Read security notesNotionOAuthEncrypted VaultExecution EngineReplay QueueReceipt Store
OAuth lifecycle
Connect, refresh, revoke, disconnect.
Encrypted vault
AES-256-GCM at rest for Notion credentials.
Data minimization
Retained content is limited to identifiers and execution evidence needed for operation and recovery.
Replay safety
Idempotent action keys and failed-action replay.
Questions users ask fast
Answer adoption blockers before signup.
Does ClientFlow replace Notion Custom Agents?
No. ClientFlow gives Notion agents a production-ready client-delivery system: playbooks, scope validation, approval policies, deterministic execution, recovery, and outcome reporting.
Can ClientFlow work without Custom Agents?
Yes. ClientFlow Direct can trigger and execute from your existing Notion workspace. Agent mode is for teams using supported Notion plans.
Does the agent make changes without approval?
Planning and inspection can run automatically. Production writes follow your approval policy, and founding pilots begin with approval required for every plan.
What happens when part of a run fails?
ClientFlow records every action, keeps successful work intact, and replays only failed or unresolved actions after reconciliation.
Can the agent change our service process?
It can recommend adaptations, but published playbook controls and mandatory tasks cannot be silently removed. Exceptions stay visible and require approval.
What data does ClientFlow store?
ClientFlow minimizes retained workspace content, stores identifiers and execution evidence needed for operation and recovery, and documents what is processed, retained, and deleted.
Can consultants use this?
Yes. Partner mode is designed for Notion consultants who deploy and maintain client delivery systems across customer workspaces.
What is the founding pilot?
A done-for-you deployment: workspace assessment, one service playbook, visual diff, approval flow, one live run, Delivery Receipt, and 30 days of implementation support.