Prepare a new proposal draft.
Choose a proposal kind, add the source pack, and review the generated structure in the Arc workspace.
Choose by delivery context
Start from the proposal job your team must finish.
Arc is most useful when the team already has deal context spread across briefs, RFPs, notes, scopes, pricing assumptions, and approved proof. Choose the context below by its inputs, review loop, and handoff—not by a generic industry label.
These pages describe current drafting and review workflows. They do not imply vertical expertise, verified customer outcomes, or automated approval.
Choose by starting point
Use the path that matches what you have today.
Inspect readiness before rewriting.
Use the deterministic analyzer for section coverage, checklist signals, and optional requirement-coverage review.
Inspect examples and product boundaries.
Review fictional structures, supported handoffs, documentation, trust materials, and current plan information.
Six current decision contexts
Match Arc to the source, review, and handoff.
Each route below leads to an existing Arc workflow page with a more detailed explanation of that context.
Repeatable client-proposal production
Move from client context and approved proof into a structured first draft while preserving account-specific review.
- Source
- Client brief, RFP, scope, approved case studies, pricing assumptions
- Review
- Account, strategy, delivery, commercial, and client-readiness review
- Handoff
- Client proposal draft for editing and export
Engagement proposals built around the decision
Organize discovery, methodology, workstreams, deliverables, governance, and fee assumptions for partner review.
- Source
- Client brief, interviews, analysis, methodology, team profiles, fee assumptions
- Review
- Engagement lead, subject-matter, risk, and commercial review
- Handoff
- Consulting proposal for client discussion
Buyer-specific sales proposals
Connect discovery notes, buyer priorities, approved proof, implementation context, and commercial assumptions.
- Source
- Discovery notes, account context, product proof, scope, pricing assumptions
- Review
- Sales, product, delivery, finance, and legal review
- Handoff
- Sales proposal for buyer evaluation
Founder-led proposals without a proposal team
Create a structured partner, customer, services, or funding-related draft from the material the founder already has.
- Source
- Opportunity notes, product context, scope, evidence, financial assumptions
- Review
- Founder plus the accountable legal, financial, or technical reviewer
- Handoff
- Proposal draft appropriate to the selected kind
Renewal and expansion proposals
Frame delivered value, continuity, changes, open risks, future scope, and commercial assumptions for an existing account.
- Source
- Account history, approved outcomes, usage context, future scope, commercial notes
- Review
- Account owner, delivery, finance, product, and legal review
- Handoff
- Renewal or expansion proposal
Requirement-led response drafting
Organize an RFP and supporting material into a response structure with visible gaps and final human approval.
- Source
- Buyer RFP, capability material, implementation plan, approved evidence, commercial notes
- Review
- Bid owner, SMEs, security, legal, finance, and executive review
- Handoff
- Reviewable RFP response draft for final submission preparation
Where Arc stops
Drafting support does not transfer accountability.
The opportunity owner and appropriate subject-matter reviewers still approve claims, pricing, scope, legal terms, technical commitments, security responses, funding requirements, and the final release.
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