# Design Partner Pilot Scope Brief

Canonical page: https://waitlist.crany.ai/marketing-templates/design-partner-scope-brief

By Tangenix. Published 2026-10-24. Category: Founder acquisition.

Define a limited software design-partner pilot with a real task, responsibilities, feedback boundaries and a clear review decision.

## Task

Scope a small design-partner collaboration without promising unlimited custom development.

## When to use

Use this when a relevant organization and founder voluntarily want to test a bounded product workflow. Agree operational expectations before starting; use separate appropriate agreements where needed.

## Choose another approach when

The document would substitute for a legal contract, the partner expects unavailable production guarantees, or the work cannot plausibly inform a reusable product.

## Inputs

- The partner’s actual workflow and a named participant authorized to evaluate it.
- Current product limits and the founder’s realistic delivery capacity.
- Safe inputs, feedback arrangements and a proposed review date.

## Template

    Pilot task and intended learning: [specific scope]
    Current product capabilities: [verified]
    Explicitly excluded work: [custom requests, integrations or guarantees not offered]
    Partner responsibilities: [inputs, participant and feedback time]
    Founder responsibilities: [setup, support and deliverables]
    Data and access boundaries: [approved test inputs and applicable separate agreements]
    Success evidence: [observable task outcome, not a promised business result]
    Review date and stop conditions: [actual plan]
    After review: continue / revise / end, by mutual agreement.
    Open commercial or legal terms: [resolve separately before commitment]

## Illustrative example

This is not a Crany customer result. Replace example details with verified facts.

    Fictional pilot tests whether a handoff organizer helps two builders prepare the same sample handoff consistently. The founder provides setup help and records confusing steps; the partner supplies approved sample notes and attends a review.
    Custom invoicing integration is excluded. Success means the agreed handoff task can be completed and limitations are understood, not a guaranteed reduction in project costs.
    The brief identifies unresolved terms for separate review and does not authorize account access, data transfer or an open-ended development commitment.

## How to use

1. Define one task whose learning could inform the reusable product.
2. Agree responsibilities, exclusions, safe inputs and observable evidence.
3. Resolve separate commitments appropriately, then review actual outcomes at the agreed point.

## Checks

- Scope does not imply unlimited bespoke development.
- Success evidence describes an observable task rather than an invented ROI promise.
- This operational brief is not described as a legal agreement.

## What to measure

Compare agreed task evidence, founder effort and reusable learning at review. A successful pilot alone does not prove market demand, customer retention or readiness for all organizations.

## Research and sources

YC’s founder discussion highlights feedback and the tension between reusable products and one-off work. This original pilot-planning brief is not a contract, security certification or proven path to product-market fit.

- [Y Combinator: The Delicate Balance of B2B Sales](https://www.ycombinator.com/blog/balancing-b2b-sales/) — checked 2026-10-24. Historical founder discussion of early customer feedback and the risk of one-off work; not legal guidance or a claim that pilots establish product-market fit.

Prepared with AI assistance. Sources support the stated principles; they do not endorse Crany or guarantee performance.

## About Crany

Crany is an AI marketing co-founder in development for software founders and vibe coders. It is designed to strategize, execute approved marketing and improve based on results. These free resources are usable independently of app access. The public waitlist is at https://waitlist.crany.ai/.