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.
Choose by delivery context
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.
Read a real exported proposal alongside the brief Arc received. The example keeps supplied scope, commercial assumptions and reviewer responsibility visible.
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.
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.
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.
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.
Inspect scope, exclusions, requirements and price assumptions. Use reviewable edits and saved comparisons; an unresolved buyer question needs an owner or an explicit qualification.
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.
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.
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.
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
Choose a proposal kind, add the source pack, and review the generated structure in the Arc workspace.
Use the deterministic analyzer for section coverage, checklist signals, and optional requirement-coverage review.
Review fictional structures, supported handoffs, documentation, trust materials, and current plan information.
Six current decision contexts
Each route below leads to an existing Arc workflow page with a more detailed explanation of that context.
Move from client context and approved proof into a structured first draft while preserving account-specific review.
Organize discovery, methodology, workstreams, deliverables, governance, and fee assumptions for partner review.
Connect discovery notes, buyer priorities, approved proof, implementation context, and commercial assumptions.
Create a structured partner, customer, services, or funding-related draft from the material the founder already has.
Frame delivered value, continuity, changes, open risks, future scope, and commercial assumptions for an existing account.
Organize an RFP and supporting material into a response structure with visible gaps and final human approval.
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
Arc prepares a structured first draft from the material you provide. Your reviewers still own the facts, scope, pricing, commitments, and final approval.
Updated