Skip to content
Arc
Sign In Get started

Arc · worked guide

Partnership proposal template for a defined shared project

A partnership proposal describes a proposed collaboration before the parties commit to final terms. It should explain the shared goal, what each party would contribute, who would own the work and how the parties would decide whether to continue. A proposal is separate from a negotiated partnership agreement.

Choose a Partnership proposal →

A worked workflow

A partnership proposal with contributions and milestones

A useful commercial partnership proposal explains what both parties would contribute and what they are being asked to decide. The fictional parties below are negotiating a pilot; they have not entered an agreement.

The supplied brief

Parties
Alder Workshop would supply training content and facilitators. Birch Analytics would supply the pilot environment and participant coordination.
Joint objective
Test a three-session administrator-training program with a jointly reviewed feedback report.
Commercial assumption
A proposed GBP 12,000 cap with milestone payments of 30%, 40% and 30%: GBP 3,600, 4,800 and 3,600.
Open issues
Brand approvals, permitted data use, intellectual property, cancellation and any exclusivity require explicit negotiation.
  1. State the joint outcome

    Choose a partnership proposal and supply both parties’ objectives, contributions, proposed operating model and decision.

    Inspect: Each promised contribution needs a named owner and a dependency. Do not infer that one party has agreed to supply a resource.

  2. Make the milestones inspectable

    Separate preparation, delivery and joint review. Tie any proposed payment milestone to a clear deliverable and acceptance step.

    Inspect: The three illustrative amounts sum to GBP 12,000. Acceptance conditions and who can approve a milestone remain part of the proposed terms.

  3. Expose unresolved commercial terms

    Review IP, confidentiality, brand permissions, data access, exit arrangements and any exclusivity request.

    Inspect: A polished proposal must not silently convert an open issue into a mutual commitment.

  4. Prepare the recipient’s version

    Inspect the saved draft and exported file, including contribution tables, assumptions and the next decision.

    Inspect: A proposal requests agreement in principle; a final partnership agreement needs its own negotiated and reviewed terms.

Before approving the result

  • Use the parties’ actual legal identities in a real matter.
  • Check that the contribution table matches the milestone plan.
  • Keep proposed, accepted and contractually agreed terms distinct.

Fictional partnership-planning example. Arc does not make an agreement binding, approve data sharing or determine the legal effect of a proposed commercial term.

Arc · inspectable review specimen

A partnership proposal that separates roles and commitments

A partnership proposal should name the joint job, each party’s contribution, the operating process and the terms still open for negotiation. A referral goal is not an achieved result.

Authored fictional instructional sample. The downloadable Word file is rendered through Gixo’s real document exporter. This is separate from the captured product workflows on this page.

Joint objective

Fictional parties Harbor Workshop and Mariner Studio propose a three-month referral pilot for website handoff training. No agreement has been signed.

PartyProposed contributionBoundary
Harbor WorkshopIntroduce interested organizations with their permissionNo promise of qualified leads or sales
Mariner StudioProvide a discovery call and scope proposalBuyer approval is separate
Both partiesReview the referral log monthlyUse only agreed, permissioned information

Commercial discussion

A proposed referral fee is 20% of net revenue actually received for eligible pilot work, with a cap and attribution window still to be negotiated. A GBP 1,000 eligible receipt would imply GBP 200 before the parties settle tax treatment. This is a worked arithmetic example, not a payment commitment.

Open terms

Resolve attribution, refunds, confidentiality, customer permissions, intellectual property, exclusivity, termination and dispute handling. Record who may approve final terms. Do not interpret this proposal as an executed partnership.

Authored fictional partnership proposal for review. No referral, payment, buyer message or signature was sent.

Arc · real output

From a supplied scope to a proposal you can inspect.

The first page of the consulting proposal Arc wrote: the cover details, the notice that the buyer and bidder are fictional, and the start of the executive summary.
Related worked example · Consulting proposal · Consulting proposal: repairs satisfaction measurement, Harbourside Housing Association. View full size ↗

Read a real exported proposal alongside the brief Arc received. The example keeps supplied scope, commercial assumptions and reviewer responsibility visible.

Consulting proposal: repairs satisfaction measurement, Harbourside Housing Association

A ten-week advisory engagement for an invented housing association: situation, approach and phases, a requirement-by-requirement compliance matrix, deliverables, timeline, team, terms, and a fee built phase by phase from the bidder's day rates, with the days of each role shown.

Inspect the source brief or data

Propose a ten-week advisory engagement for Harbourside Housing Association, on behalf of Larkfield Analytics Ltd, that answers the association's brief: review the current repairs survey, recommend how to measure repairs satisfaction by contractor, and leave a reporting approach for the repairs team and the board. Build the fee for each phase from the standard rates in the evidence file (the days of each role times the day rate) and show those days. Add nothing the evidence file does not state. Put a notice on the cover page that the buyer and the bidder are fictional and the proposal is a worked example. Inputs: the buyer's document (brief-harbourside-housing.md); the bidder's evidence file (larkfield-evidence.md); commercial terms: value 46,000 to 52,000 GBP, valid for 60 days, payment terms 'Invoiced monthly in arrears, payable within 30 days.'; deal context: The buyer and the bidder in this proposal are fictional, and this proposal is a worked example. The engagement lead presents to the buyer's board in the ninth week.

Read the sample review notes

A separate reviewer agent read its 177 claims against the bidder's evidence file, the buyer's brief and the deal terms: 115 are supported, 58 add design detail or an inference, 4 are in no input (it calls the fee fixed) and none contradicts one. Every price line recomputes. It is not a person's review.

Prepare the source pack

Choose the proposal kind and supply the buyer brief, approved evidence, delivery assumptions and commercial terms. For RFP work, retain the issued requirements and separate known answers from missing evidence.

Review the proposed response

Inspect scope, exclusions, requirements and price assumptions. Use reviewable edits and saved comparisons; an unresolved buyer question needs an owner or an explicit qualification.

Package the reviewed version

Inspect the actual PDF, Word or HTML output. Tracked delivery activity and a recorded deal outcome answer different questions; verify the recipient, permissions and current approval state before sharing.

Buyer requirements and response ownership

Keep buyer RFP files separate from bidder evidence and approved reusable answers. Inspect extraction coverage, requirement source locations, questionnaire previews and submission limits. Response work can carry an SME owner, due date, escalation owner and required reviewer decisions. Compare an addendum with the source before changing a response.

Commercial schedules and recurring totals

Review each line's quantity, rate, unit, optional status and one-off, monthly or annual recurrence. Inspect recurrence totals and the estimated first-year total separately. Currency, supplied tax input and commercial assumptions need review. When importing Business metrics, select and review the source values before applying them to the schedule.

Buyer edition and submission package

Choose the current saved response or an approved edition. Inspect retained attachments, filled questionnaires, the compliance matrix and the package preview. A release manifest identifies stored delivery bytes. For tracked links, review recipient access, expiry, password and permissions separately from delivery activity and the recorded opportunity outcome.

A draft or readiness check is not approval of pricing, legal terms or a delivery commitment. Arc proposal drafting does not imply CRM, CPQ or tax-calculation automation.

Filled collaboration-planning example

This filled example is an editorial explanation of the structure. The related real product output above is separately identified.

Filled collaboration-planning example
PartExample and review point
Shared goalFictional Harbor Studio and Cedar Training propose a joint customer workshop.
ContributionsHarbor supplies the venue and invitations; Cedar supplies the teaching material and facilitator.
ResponsibilitiesName a lead for agenda approval, attendee permissions, delivery and post-event follow-up.
MeasuresAgree attendance and feedback measures before the event; no invented outcome figures.
Open termsCosts, rights to recordings, branding permission, cancellation and the decision date remain subject to agreement.

Keep the joint plan separate from legal commitments

Explain dependencies and exclusions so the reader can see what is not included. Describe how changes would be proposed and who can approve them. If the proposal names exclusivity, revenue sharing or intellectual-property rights, flag those terms for the relevant commercial and legal reviewers. Arc’s Partnership proposal type can draft from the source brief; final obligations require separate agreement and review. Use a separate legal drafting workflow when the parties are ready to prepare contract language.

Explore a separate agreement draft →

Updated