Workflow-specific products Content, decks, briefs, proposals, legal, and sales each have a clearer buying path.
Review before delivery Draft, edit, collaborate, approve, and export in the same workspace.
Security + procurement path Security policy, support, and Azure Marketplace buying are public.

Fictional proposal example

Community-skills grant draft

A fictional nonprofit is preparing a workforce-skills funding application. The preview shows how funder instructions, program evidence, delivery design, measures, and budget notes can be organized for a human-led application review.

This scenario and every passage below are fictional and illustrative. They demonstrate a reviewable proposal structure, not customer work or a promised result.

Internal & funding Grant Nonprofits and program teams

Before drafting

Bring the source pack and name the release checks.

The quality of a proposal draft depends on the material supplied and the reviewers accountable for its claims.

Illustrative source inputs

Material this fictional team would prepare

  • Funder guidance
  • Community-needs evidence
  • Program design
  • Partner letters
  • Budget notes
Human review checks

Questions to close before release

  • Check funder eligibility
  • Verify every evidence claim
  • Reconcile narrative and budget
  • Obtain authorized sign-off

Illustrative section preview

A document shape the team can challenge.

The passages below describe what each section should accomplish. They are not complete proposal language and should never be copied as factual evidence.

Community-skills grant draft Fictional structure

Need statement

The draft links the proposed program to supplied community evidence and clearly marks any statistic or source that still needs verification.

Program design

Activities, participant criteria, delivery partners, safeguarding responsibilities, and program boundaries are organized against the funder's questions.

Outcomes and measurement

Proposed measures are written as targets for funder and program-team review, not as guaranteed outcomes.

Budget narrative

Cost categories, assumptions, match funding, in-kind support, and exclusions are aligned with the separate budget workbook.

Submission review

Eligibility, attachments, declarations, signatures, and deadline ownership remain explicit final checks before submission.

Replace this fictional structure with the actual buyer request, approved evidence, scope, pricing, risks, exceptions, and reviewer decisions for the opportunity.

Use the archetype, not the fictional facts

Create something like this from your own source material.

Arc will start with the same proposal kind. Upload the real opportunity inputs and replace every illustrative assumption with approved evidence, scope, pricing, and commitments.

Next example

Inspect Northstar account-expansion proposal

Your material, your review, your decision

Move from source files to a proposal draft your team can inspect.

Arc prepares a structured first draft from the material you provide. Your reviewers still own the facts, scope, pricing, commitments, and final approval.