Back to examples
Client onboardingInternal workflow example

Sales-to-delivery agency handoff

Connect an approved sale to onboarding, access checks and a documented delivery handover.

This example explains a workflow design and its controls. It does not represent verified client results. Tooling and benefits must be validated in each project's context.

Sales-to-delivery agency handoff editorial cover

Solution example

Sales-to-delivery agency handoff

Connect an approved sale to onboarding, access checks and a documented delivery handover.

The design connects these steps: Accepted proposal → Readiness checklist → Access inventory → Credential rules → Folder plan → Kickoff pack → Delivery tasks → Kickoff email. Rules, exceptions and approvals are defined before external actions are connected.

Workflow map

Handoff workflow from sold deal to kickoff pack

The workflow turns sales context into delivery tasks, folders and access checks before kickoff.

Readiness lanes convergeStart1. Deal becomes readyClosed-won | readiness stateCRM/Supabase2. Check handoff dataScope | owner | dates | accessPython/FastAPI3. Build kickoff packSummary | risks | first tasksOpenRouter4. Create workspace planFolders | board | checklistGoogle Drive + ClickUp5. Check blockersMissing access | missing assetsReady forkickoff?NoYes6b. Request accessOwner | missing itemsResend/email7b. Track blockerException queueRetry6a. Create tasksKickoff | access | first delivery7a. Send handoffDelivery owner | summaryResend/emailEnd

Main database: Supabase

The workflow uses Supabase as the source of truth: it stores each record, status, and key event so the team can see what happened, retry failures, and debug without searching every tool.

Tool icons

SupabasePython/FastAPIOpenRouterGoogle DriveClickUpResend/email

System rationale

A handoff is not one event; it is a readiness system

The handoff only works when commercial, legal, access and delivery setup are connected. This case turns accepted work into a kickoff-ready state, then creates the workspace and first tasks.

Readiness comes first

A client should not create delivery noise until contract, payment, owner and access questions are visible.

Access needs rules

The workflow asks for access with purpose, owner and credential handling rules instead of collecting secrets in chat.

Workspace creation should be repeatable

Folders, kickoff pack, questionnaire and first tasks are produced from the same source so every project starts cleanly.

Add-ons that fit on top

Contract checklist
NDA/DPA gate
Payment/deposit check
Google Drive/SharePoint folders
ClickUp/Asana project template
Kickoff calendar draft
Access review schedule
Client readiness dashboard
Weekly delivery digest
Handoff score

The scenario

Design scenario: Connect an approved sale to onboarding, access checks and a documented delivery handover. The starting point is a workflow with scattered information, manual steps and responsibilities that need to be made explicit.

Before implementation, we review available data, responsible owners and decisions that need approval. Understand the workflow first.

The approach

The design connects these steps: Accepted proposal → Readiness checklist → Access inventory → Credential rules → Folder plan → Kickoff pack → Delivery tasks → Kickoff email. Rules, exceptions and approvals are defined before external actions are connected.

AI can help classify, extract or draft; sensitive actions retain human review. Clear controls at each step.

What was used

Tooling was chosen from the process outward, not from a pre-decided technical preference. Each piece needed a clear owner, a stable integration path and a simple way to inspect errors.

In practice, the build combined Supabase, Python/FastAPI, OpenRouter, Google Workspace adapter, ClickUp, Resend-ready email. The tools visible to the team stayed close to their daily work, while integration logic was documented and kept separate from sensitive commercial decisions.

SupabasePython/FastAPIOpenRouterGoogle Workspace adapterClickUpResend-ready email

Workflow design

Manual approach and proposed workflow

Manual approach

1Proposal accepted
2Sales notes searched manually
3NDA/payment/access status checked in separate places
4Folders created manually
5Access chased in chat
6Kickoff repeated discovery

Proposed workflow

1Client readiness row
2Commercial/legal/access checklist
3Access inventory
4Credential rules
5Google folder adapter
6Kickoff pack
7ClickUp first tasks
8Delivery handoff summary

Visible artifacts

  • Commercial readiness checklist
  • Access inventory
  • Safe access request draft
  • Kickoff agenda
  • Discovery questionnaire
  • Folder structure
  • First delivery tasks
  • Launch criteria

Controls

  • No secrets stored
  • Access requests use least privilege
  • Checklist blocks kickoff when required items are missing
  • Credential rules included in client email
  • Human review before client-facing message

What this aims to improve

The aim is to reduce manual coordination and make records, exceptions and the next action visible. Any improvement must be validated against the project's own data and operating conditions.

Project scoping establishes a baseline and success criteria so proposed improvements can be tested. Validate the benefit in context.

The workflow in one line

01Accepted proposal02Readiness checklist03Access inventory04Credential rules05Folder plan06Kickoff pack07Delivery tasks08Kickoff email

Tooling and boundaries

The design shows how Supabase, Python/FastAPI, OpenRouter, Google Workspace adapter, ClickUp, Resend-ready email can work together. Final tooling, scope and controls are agreed for each project.

Integrations need appropriate permissions, run logs and a way to review exceptions. The team should be able to understand and operate the workflow.

What this example demonstrates

Design components
  • Proposal-accepted trigger
  • Commercial/legal checklist
  • Access inventory
  • Credential rules
  • Client folder plan
  • Kickoff pack
  • Discovery questionnaire
  • ClickUp task sync
  • Launch criteria
Intended controls
  • No secrets stored
  • Access requests use least privilege
  • Checklist blocks kickoff when required items are missing
  • Credential rules included in client email
  • Human review before client-facing message

Discuss a similar workflow.

Discuss your workflow

Free initial conversation. No obligation.

Ductio newsletter

Practical ideas for better work.

Get ideas on automation, connected systems and more reliable processes.

Ductio
DuctioSYSTEMS
Custom automation, connected systems and support for teams that need reliable, documented workflows.
Operating focus

CRM operations, reporting workflows, approvals, document handling, and AI-assisted internal tools.

Copyright © 2026 Ductio. All rights reserved.

Discuss your workflow

Free initial conversation. No obligation. We will work through the details together.

Add more details (optional)

We use these details to respond to your inquiry. Please do not include passwords or confidential business data. Privacy notice

You can also email contact@ductiosystems.com.