Sales Proposal
Standard new business opportunity
- Focus
- Problem → Solution → Value → Investment → Action
- Draft target
- About 2,500 words before team review and editing
Structure before styling
Arc organizes a draft around one of 21 current proposal kinds, then lets the team review the content and choose an export layout. The proposal kind shapes the expected sections; uploaded material supplies the opportunity context.
Arc does not promise to reproduce an uploaded proposal template. Source files provide context; the selected proposal kind provides the drafting structure.
Current proposal-kind catalog
Each type carries a distinct section focus. The labels below describe drafting guidance, not an assurance that every proposal will contain the same sections or length.
Standard new business opportunity
Formal Request for Proposal response
Large enterprise deals with complex requirements
Quick quote for smaller engagements
Contract renewal for existing customers
Upsell/expansion to existing customers
Re-engagement of churned customers
Consulting engagement
Project-based work
Ongoing retainer or managed services
Staff augmentation or resource placement
Business partnership or alliance
Joint venture or co-investment
Sponsorship opportunity
Internal business case or budget request
Grant application or funding proposal
Investment pitch or funding request
Government or public sector
Research or academic proposal
Creative services (design, marketing, content)
Technology implementation
Current proposal export layouts
Arc currently exposes the layouts below for proposal exports. Layout choice changes presentation; it does not verify the proposal's facts, requirements, or commitments.
Clean business layout for general-purpose proposal exports.
Dense technical format for implementation-heavy proposal documents.
Formal structured layout for rigid, compliance-heavy submissions.
Commercial proposal styling for sales proposals, renewals, and expansions.
Phase-driven consulting format with deliverables and methodology.
Evaluator-oriented response format for RFP, RFI, and RFQ submissions.
Formal institutional layout for grants and public-sector proposals.
Narrative format for alliances, partnerships, and strategic deals.
Implementation format organized around architecture, dependencies, and phases.
The Arc product page currently documents PDF, DOCX, and HTML delivery, plus Markdown, JSON, and plain-text export. Review the live plan and export surface before committing a format to a buyer or procurement team.
A business proposal template and a project proposal template are not interchangeable, because the reader is deciding different things. A buyer reading a business proposal is deciding whether to spend; a sponsor reading a project proposal is deciding whether the plan is sound. Each type below opens on the question its reader actually has, and each has a starting point in Arc.
Most proposal formats carry the same seven parts: an executive summary of the opportunity, the findings or brief that shows you understood it, your approach, the scope and deliverables, the timeline, the pricing and terms, and a single clear next step. The order matters more than the section names — lead with the reader's problem and the evidence you understood it, not with your company background.
A proposal sample and a proposal template are different things, and both are useful at different moments. A sample is a filled-out proposal you read to see how the sections behave in a real engagement; a template is the empty structure you complete. Read worked proposal examples and samples, or start from how to write a business proposal if you want the format explained section by section.
Use an RFP response template as a starting outline for the buyer's evaluation, then fill it with opportunity-specific facts and evidence. Arc's current RFP Response type uses the nine sections below as its starting structure. The issued format, numbering, forms and submission limits take priority; review the generated draft rather than assuming it reproduces every instruction.
| Starting section | What to supply and check |
|---|---|
| Cover Letter | Name the issuing buyer, RFP number and submission purpose; check who may sign and the permitted length. |
| Executive Summary | Explain the proposed response and supported differentiators in the evaluator's terms; check each claim against the supplied proof. |
| Company Overview & Qualifications | Supply relevant company facts, credentials and team capability; verify dates, scope and permission to disclose. |
| Technical Approach | Respond using the buyer's requirement numbering, proposed approach and evidence; identify gaps and assumptions. |
| Management Approach | Explain responsibilities, delivery governance, dependencies and escalation; confirm the people and commitments. |
| Past Performance / References | Provide relevant, permitted references and case studies; distinguish illustrative examples from verified delivery history. |
| Pricing Volume | Use the buyer's requested schedule with all cost elements, assumptions and exclusions; check calculations and commercial approval. |
| Required Forms & Certifications | Complete the issued forms and declarations with authorized, evidenced statements; a drafted sentence is not a certificate. |
| Appendices | Attach only permitted supporting material, with the right labels, versions and links; check submission and page limits. |
Read the fictional Marlow RFP worked response in Word to inspect how the sections connect. It is a completed example, not an empty template or verified supplier credentials. Review the RFP drafting workflow and sample context.
Bring the actual RFP, brief, notes, prior work, pricing assumptions, and approved proof. Then review the resulting structure against the opportunity instead of forcing every deal through the same document.
Your material, your review, your decision
Arc prepares a structured first draft from the material you provide. Your reviewers still own the facts, scope, pricing, commitments, and final approval.
Updated