Skip to content
Arc
Sign In Get started

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.

Arc · real output

From a supplied scope to a proposal you can inspect.

The first page of the consulting proposal Arc wrote: the cover details, the notice that the buyer and bidder are fictional, and the start of the executive summary.
Related worked example · Consulting proposal · Consulting proposal: repairs satisfaction measurement, Harbourside Housing Association. View full size ↗

Read a real exported proposal alongside the brief Arc received. The example keeps supplied scope, commercial assumptions and reviewer responsibility visible.

Consulting proposal: repairs satisfaction measurement, Harbourside Housing Association

A ten-week advisory engagement for an invented housing association: situation, approach and phases, a requirement-by-requirement compliance matrix, deliverables, timeline, team, terms, and a fee built phase by phase from the bidder's day rates, with the days of each role shown.

Inspect the source brief or data

Propose a ten-week advisory engagement for Harbourside Housing Association, on behalf of Larkfield Analytics Ltd, that answers the association's brief: review the current repairs survey, recommend how to measure repairs satisfaction by contractor, and leave a reporting approach for the repairs team and the board. Build the fee for each phase from the standard rates in the evidence file (the days of each role times the day rate) and show those days. Add nothing the evidence file does not state. Put a notice on the cover page that the buyer and the bidder are fictional and the proposal is a worked example. Inputs: the buyer's document (brief-harbourside-housing.md); the bidder's evidence file (larkfield-evidence.md); commercial terms: value 46,000 to 52,000 GBP, valid for 60 days, payment terms 'Invoiced monthly in arrears, payable within 30 days.'; deal context: The buyer and the bidder in this proposal are fictional, and this proposal is a worked example. The engagement lead presents to the buyer's board in the ninth week.

Read the sample review notes

A separate reviewer agent read its 177 claims against the bidder's evidence file, the buyer's brief and the deal terms: 115 are supported, 58 add design detail or an inference, 4 are in no input (it calls the fee fixed) and none contradicts one. Every price line recomputes. It is not a person's review.

Prepare the source pack

Choose the proposal kind and supply the buyer brief, approved evidence, delivery assumptions and commercial terms. For RFP work, retain the issued requirements and separate known answers from missing evidence.

Review the proposed response

Inspect scope, exclusions, requirements and price assumptions. Use reviewable edits and saved comparisons; an unresolved buyer question needs an owner or an explicit qualification.

Package the reviewed version

Inspect the actual PDF, Word or HTML output. Tracked delivery activity and a recorded deal outcome answer different questions; verify the recipient, permissions and current approval state before sharing.

Buyer requirements and response ownership

Keep buyer RFP files separate from bidder evidence and approved reusable answers. Inspect extraction coverage, requirement source locations, questionnaire previews and submission limits. Response work can carry an SME owner, due date, escalation owner and required reviewer decisions. Compare an addendum with the source before changing a response.

Commercial schedules and recurring totals

Review each line's quantity, rate, unit, optional status and one-off, monthly or annual recurrence. Inspect recurrence totals and the estimated first-year total separately. Currency, supplied tax input and commercial assumptions need review. When importing Business metrics, select and review the source values before applying them to the schedule.

Buyer edition and submission package

Choose the current saved response or an approved edition. Inspect retained attachments, filled questionnaires, the compliance matrix and the package preview. A release manifest identifies stored delivery bytes. For tracked links, review recipient access, expiry, password and permissions separately from delivery activity and the recorded opportunity outcome.

A draft or readiness check is not approval of pricing, legal terms or a delivery commitment. Arc proposal drafting does not imply CRM, CPQ or tax-calculation automation.

Choose by starting point

Use the path that matches what you have today.

You have source files

Prepare a new proposal draft.

Choose a proposal kind, add the source pack, and review the generated structure in the Arc workspace.

Choose a proposal type

You have an existing draft

Inspect readiness before rewriting.

Use the deterministic analyzer for section coverage, checklist signals, and optional requirement-coverage review.

Analyze a draft free

You are evaluating fit

Inspect examples and product boundaries.

Review fictional structures, supported handoffs, documentation, trust materials, and current plan information.

Browse illustrative examples

Six current decision contexts

Match Arc to the source, review, and handoff in your proposal process.

Each route below leads to an existing Arc workflow page with a more detailed explanation of that context.

Agencies

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

Open the workflow

Consulting

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

Open the workflow

B2B sales

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

Open the workflow

Startup founders

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

Open the workflow

Account management

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

Open the workflow

RFP responses

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

Open the workflow

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.

Review Arc trust and product boundaries

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.

Updated