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

Harbor market-entry engagement

A fictional consumer-products company needs a market-entry decision, not a generic strategy deck. The preview shows a consulting proposal organized around questions, workstreams, deliverables, governance, and fee assumptions.

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

Professional services Consulting Consultants and advisory teams

Illustrative Arc screen

Inspect the visible document hierarchy.

The image is a product specimen for evaluating layout and structure. It is not proof that a customer used Arc or achieved a particular outcome.

Illustrative Arc consulting proposal layout showing workstreams, deliverables, and phases.

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

  • Client brief
  • Discovery notes
  • Market research
  • Team biographies
  • Fee assumptions
Human review checks

Questions to close before release

  • Confirm the decision questions
  • Check deliverable ownership
  • Validate timing and dependencies
  • Approve fees and expenses

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.

Harbor market-entry engagement Fictional structure

Decision to support

Harbor must decide which segment and route to market merit a controlled launch. The proposal keeps that decision visible instead of hiding it beneath a broad methodology.

Workstreams

Customer demand, channel economics, competitive position, operating readiness, and launch design are treated as linked workstreams with explicit questions.

Deliverables

The draft names the expected artifacts and review points while leaving client-specific quantities and acceptance criteria for confirmation.

Working model

Cadence, steering roles, client inputs, access requirements, and decision rights are stated before the timeline.

Fees and assumptions

Fee structure, expenses, taxes, payment timing, and change-control assumptions remain visible for partner and client review.

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 Claims-workflow business case

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.