A little structure. A clearer next step.

Design-partner qualification

Check whether a prospective partner has the workflow, access and commitment for a useful pilot.

Free to use · No signup · Yours to keepRead the guide

Make it yours.

Start with what you know. Leave the rest open until you have evidence.

0 of 7 fields filledLoading your local draft…

Your answers stay in this browser. They are not sent to Soloop or synced between devices. Download a copy to keep it.

Which organization and workflow?

Explain how this organization represents the customers you want to serve. Mark observations and assumptions separately.

Example

Agency A runs client handoffs between account managers. Whether its process is typical of our target segment is unknown.

0 / 12,000 characters

What is happening today?

Record the most recent instance, workaround, consequence and source/date. Enthusiasm alone is not a qualifying problem.

Example

A recent transfer used a shared checklist. Source: [permissioned note], [date]. Consequence of leaving it unchanged: [record].

0 / 12,000 characters

Who will participate and authorize it?

Name roles for the actual user, sponsor and purchase authority. Keep unconfirmed commitments explicit.

Example

An account manager can participate; the operations sponsor and purchase authority still need confirmation.

0 / 12,000 characters

What access and permission are needed?

List approved sample inputs, environment, permission owner and blocked prerequisites. Do not paste credentials or private customer data.

Example

A redacted checklist may be shared after approval. No production credentials are needed. Permission owner: [role].

0 / 12,000 characters

What will the partner commit to?

Define one workflow, available time, review cadence and next agreed meeting. Record a proposal as a proposal until agreed.

Example

Proposed: one handoff trial and a weekly review for three weeks. User availability and dates are not yet agreed.

0 / 12,000 characters

What can you support?

Set setup effort, support limits and exclusions. Avoid committing to custom work outside the product direction.

Example

Up to two hours of setup and one review per week. No custom CRM connector in this pilot.

0 / 12,000 characters

Invite, clarify or decline?

Give the reason, strongest contrary evidence, unresolved prerequisite and review date. If inviting, state the learning question and exit condition.

Example

Clarify access before inviting. Learn whether the checklist works without founder help; stop if approved sample inputs remain unavailable.

0 / 12,000 characters

A clear record of your thinking, ready to take with you.