Plan the proposal
Define the audience, decision, source pack, and reviewers before drafting.
Decision to make: Which outcome, evidence, and approval path should shape this response?
Arc learning path
Learn the workflow before you ask a team to adopt it.
Arc documentation is organized around the proposal decisions a team must make: what to include, which source material supports it, who reviews it, how the draft is evaluated, and how approved work is handed off.
Public guidance explains the workflow and product boundaries. The live workspace remains the source of truth for controls available on your plan and account.
A six-part path
Move from opportunity context to an approved handoff.
Read in order for a first implementation, or open the stage where your current proposal process breaks down.
Ground the draft
Use opportunity material as context and make unsupported gaps visible to reviewers.
Decision to make: Which statements are supported by supplied sources, and which still need evidence?
Keep humans in the loop
Assign review ownership for claims, requirements, commercial terms, and final release.
Decision to make: Who can approve each class of commitment?
Analyze a draft
Use the free deterministic analyzer to surface structural signals before a human review.
Decision to make: Which visible weaknesses deserve attention before submission?
Govern team usage
Define inputs, permissions, review checkpoints, and an accountable release process.
Decision to make: Which controls make the workflow repeatable without removing judgment?
Reuse approved knowledge
Treat prior material as governed source content rather than automatic truth for a new buyer.
Decision to make: What may be reused, who approved it, and when must it be revalidated?
Reference by question
Find the evidence you need for evaluation.
These references separate proposal structures, product behavior, buying criteria, connection paths, and frequently asked questions.
Proposal-type catalog
Compare the current proposal kinds and the drafting focus associated with each starting point.
Illustrative example gallery
Inspect fictional inputs, review checks, and document structures without implying customer results.
Arc product overview
Review the public product workflow and current plan information.
Integration boundaries
See current intake, export, tracked-link, and MCP analysis paths alongside explicit non-claims.
Buyer criteria
Use a decision framework when comparing software for AI-assisted RFP responses.
Proposal FAQ
Find concise answers about Arc proposal workflows and their limits.
Working definition
A generated draft is a review artifact, not a release decision.
Arc can structure a proposal draft from the material supplied to it. The team remains responsible for source quality, factual accuracy, requirements coverage, pricing, scope, legal terms, buyer-specific commitments, and final approval.
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.
Related Pages