Partnership outreach: a concrete collaboration proposal

Use this sequence for a specific joint project with a clear work split. It proposes a workshop, then offers an outline and closes the conversation.

The organizations and project are fictional. Replace them with an offer you can deliver and use a proposal route that accepts this type of enquiry. A public employee address does not establish permission.

Prepare the offer

The example is a practical record-keeping workshop for a business community. The sender supplies the teaching and session outline; the prospective partner decides whether the topic fits its members.

Do not promise attendee numbers, revenue or an endorsement. If the project needs registration data, agree how it will be handled separately.

Merge field: firstName, using the fallback there. The project details are plain text so you can review the work split without relying on unknown fields.

Message 1: name the project

Initial subject: Record-keeping workshop proposal

Hi {{firstName | there}},

Your collaboration page asks for workshop proposals for small-business members.

I organize practical bookkeeping sessions. I would like to propose a short workshop on the records a business can prepare before its first bookkeeping appointment.

I would prepare and teach the session. Your team would decide whether the topic fits and whether you want to host or share the invitation.

Would you like a one-page outline showing the topic and work split?

Thanks,
Maya

If you prefer no further proposals from me, reply and I will stop.

The opening must match the actual collaboration instructions. Do not claim an invitation that the organization has not made.

Message 2: answer a workload question

Hi {{firstName | there}},

One practical detail on the workshop: I would bring the teaching materials and lead the session. I am not asking your team to write the content.

The outline would let you review the audience fit and responsibilities before any planning call.

Would you like me to send it?

Maya

Reply if you would like me to stop contacting you.

Only send this if the work split remains true and no reply, bounce or opt-out has ended the enquiry.

Message 3: close this proposal

Hi {{firstName | there}},

I will close this proposal after this message.

If the workshop topic becomes relevant later, you can reply here and we can check whether the timing and responsibilities still fit.

Thanks,
Maya

Do not interpret silence as an agreement or publish the prospective partner’s logo.

Adapt the responsibilities and send the outline

Before using Message 1, replace the collaboration-route statement, audience, topic, organizer contribution and partner workload with your actual proposal.

If the partner requests the outline, a personal reply can deliver it:

Hi Alex,

Here is the proposed outline:

Audience: members preparing for a first bookkeeping appointment.
Topic: organizing records and questions for that appointment.
My contribution: teaching, materials and a session outline.
Your decision: whether the topic fits and whether to host or share the invitation.
Still to agree: timing, venue or platform, promotion and any costs.

This is a proposal for review, not an agreed event. Does the work split fit, or would you change it?

Maya

These details are the same fictional example as the initial message. Replace them with what you can deliver. Do not add a partner logo or claim a collaboration until it is actually agreed.

Keep the proposal focused on one next step. Use the campaign-writing guide to format and save the message. After a reply, follow the partner’s answer.

Turn a reply into an actual next step

If they ask for the outline, send it manually and answer their questions. If they decline the project, respect that decision. If they ask to stop all messages, record the opt-out.

ColdMerge follow-ups have no independent subject; they remain in the first message’s thread and mailbox. A detected human reply stops the campaign sequence, while automatic replies do not. Follow-up reference

Preview the greeting and project facts before launch. Keep proposed responsibilities distinct from an actual agreement.

Check opt-out controls before launch

ColdMerge’s unsubscribe footer and one-click header start off. Review and enable the appropriate controls before sending. A reply asking to stop does not automatically suppress the address across campaigns: choose Mark as opted out manually. That suppression applies across the Organization. See How unsubscribes work for the configuration and recipient behavior.