Free AI Proposal Builder for Contractors: What to Put in Before Roxy Drafts the Proposal

The best proposal builder in the world cannot rescue a vague job note. If the note says "paint exterior, customer wants it done soon" or "HVAC replacement, old unit, send quote," the proposal will still need a lot of fixing. The useful shift is not that AI magically knows the job. The useful shift is that a contractor can bring clear field notes into a tool like Roxy and get a client-ready first draft much faster than starting from a blank document.

That matters because proposal speed is a real operating problem. A contractor can do a careful site visit, answer every question in person, and still lose momentum if the customer waits two days for a written scope. By then the customer may have another quote, may forget what made your recommendation different, or may decide that the cheapest number is easiest to compare. A proposal is not just paperwork. It is the written version of your judgment, your scope, your pricing logic, and the next step you want the customer to take.

Roxy is built for that moment. It is a free AI proposal builder for contractors who want to turn job notes into a polished proposal draft without building every document from scratch. The Free plan supports up to 10 Roxy-branded proposals every 30 days, and Pro is $49/mo when you want more control. The important part is knowing what to put in before you generate the draft.

Start with the customer's actual problem

Many contractor proposals start too far downstream. They list line items and prices before they restate the reason the customer called. That makes the proposal easier to skim, but harder to trust. Before you ask Roxy to draft anything, capture the problem in the customer's language and then add your professional diagnosis.

For example, a homeowner may say, "The upstairs is hot even when the air is on." Your note might add, "Existing system is short cycling, return airflow appears limited, and customer is deciding between repair and replacement." A painting customer may say, "The trim looks rough." Your note might add, "Peeling on south and west elevations, failed caulk at window trim, mildew on shaded siding, customer wants durable prep rather than a quick color refresh."

That distinction helps the proposal feel specific. It also helps avoid the common mistake of writing a proposal that sounds like every other proposal. When a customer sees their concern reflected accurately, the document feels connected to the walkthrough they just had.

Use this simple structure:

• Customer concern: what they said they want fixed.
• Site finding: what you observed.
• Recommendation: what you propose doing.
• Reason: why this scope is the right fit.

That is enough to make the opening of a proposal sharper across almost any trade.

Capture scope as work areas, not just tasks

A proposal should make it easy for the customer to understand what is included. The fastest way to do that is to organize scope by work area. This is especially useful when the job has multiple rooms, systems, elevations, fixtures, or phases.

Instead of writing "replace fixtures," an electrical contractor might note: "Kitchen: replace three pendant fixtures, verify existing boxes, install dimmer compatible with selected lamps. Dining room: remove chandelier, cap and make safe if customer delays replacement. Exterior entry: replace existing sconce with weather-rated fixture supplied by customer." That gives Roxy enough structure to draft a proposal that reads like a project plan rather than a loose task list.

The same pattern works for HVAC, roofing, flooring, landscaping, drywall, remodels, and painting. A painting proposal can be grouped by siding, trim, doors, shutters, prep, masking, primer, and finish coats. A landscaping proposal can be grouped by demolition, grading, soil prep, planting, edging, mulch, irrigation adjustments, and cleanup. A remodel proposal can be grouped by demolition, framing, rough-ins, finishes, inspections, and final punch list.

The goal is not to write the full proposal in your notes. The goal is to give the builder enough raw material that the first draft has the right shape.

Separate estimate math from proposal explanation

Contractors sometimes ask AI to "write an estimate," but estimating and proposal writing are different jobs. Estimating is where your trade knowledge, measurements, labor assumptions, material costs, supplier pricing, production rates, risk, and margin belong. Proposal writing is how you explain the result clearly enough for the customer to approve it.

Roxy should not replace your estimating judgment. Use your normal process to decide the price. Then use Roxy to package the scope, pricing summary, timeline, terms, and next steps in a cleaner document.

Before generating the proposal, capture the pricing context you want the customer to see. You may not want to expose every internal cost, but you should decide how the price will be presented. Is it one fixed project total? Is it broken into phases? Are there good-better-best options? Are allowances included? Are there unit prices for unknown quantities? Are taxes, permits, disposal, or mobilization included?

For smaller residential work, a simple structure is often enough:

• Recommended scope total.
• Optional upgrades or alternates.
• Deposit or scheduling requirement if applicable to your workflow.
• Conditions that could change price.
• How long the proposal remains valid.

When the price is not the lowest, the proposal needs to show why. That does not mean adding fluff. It means explaining prep, materials, sequence, warranty assumptions, access constraints, cleanup, and communication in plain language.

Write down exclusions before they become disputes

Exclusions are not negative. They are a way to protect the relationship before work starts. Many disputes begin because the contractor assumed something was obviously outside scope and the customer assumed it was included. A good proposal makes those boundaries visible.

Useful exclusions vary by trade. A painter might exclude carpentry repairs beyond minor caulking unless separately approved. An HVAC contractor might exclude electrical panel upgrades, drywall repair, or asbestos abatement. A landscaper might exclude underground utility relocation, irrigation repairs, or plant replacement due to neglect after installation. A remodeler might exclude concealed damage, permit fees, owner-supplied material delays, or design changes after approval.

Put exclusions in your notes in blunt internal language first. Roxy can help turn them into customer-friendly wording, but the actual boundaries need to come from you. If something is unknown, say that too. "Price assumes existing decking is sound. Rotten decking discovered after removal will be repaired at an approved unit rate." That kind of sentence is more useful than a general disclaimer because it tells the customer what could happen and how it will be handled.

Include timeline and access details

Customers often compare contractors on price because the proposal gives them nothing else to compare. Timeline and access details can change that. They show operational competence.

Before drafting, capture the earliest realistic start window, expected duration, weather dependencies, inspection dependencies, customer responsibilities, and site access needs. For example: "Two-day interior repaint once colors are approved; customer to remove wall decor and fragile items; crew needs driveway access by 8 a.m.; low-VOC paint available if requested." Or: "HVAC replacement expected to take one working day after equipment is received; customer should expect temporary loss of heating/cooling during installation; thermostat setup reviewed before completion."

These details help the proposal answer questions before the customer asks them. They also make your business feel organized. A same-day proposal that ignores timeline can still feel incomplete. A proposal that explains what happens next can move the customer toward a decision.

Capture options without confusing the buyer

Options can help, but only when they are clear. If a customer asked for a basic repair and you send six packages, you may slow the decision down. If the customer is comparing long-term value, one recommended option plus one upgrade can be useful.

A good job note for options includes the option name, who it is best for, what changes in scope, and how it affects price or durability. For example:

• Base repair: best for stopping the current leak with the smallest immediate scope.
• Recommended replacement: best for addressing the aged section and reducing repeat service calls.
• Upgrade: best for longer service life, better finish, or improved comfort.

Roxy can help present those options clearly, but the strategic decision belongs to you. Do not add options just because a proposal looks more impressive with more sections. Add them when they help the customer choose.

Use a repeatable field-note format

If you want consistently better proposals, create a note habit. The format below works for many contractor categories:

Project summary: one sentence describing the job.

Customer goal: what the customer wants to solve or achieve.

Site findings: what you observed during the walkthrough.

Recommended scope: the work you recommend.

Work areas: rooms, elevations, systems, fixtures, or phases.

Materials/products: specific products, grades, colors, equipment, or allowances.

Pricing structure: fixed total, phases, options, unit pricing, or allowances.

Exclusions/assumptions: what is not included and what could change.

Timeline: start window, duration, dependencies, and customer responsibilities.

Next step: approve proposal, choose option, schedule call, confirm colors, or request revision.

This is the raw material a free AI proposal builder needs. The cleaner your inputs, the less editing you will do afterward.

Review the proposal like an operator

After Roxy drafts the proposal, do not only proofread the words. Review it like the person who will be responsible for delivering the job.

Ask these questions:

• Is the scope specific enough that a crew could understand it?
• Is the customer likely to understand what they are buying?
• Are the exclusions visible?
• Are options clearly different from each other?
• Does the timeline match your real capacity?
• Does the price presentation match how you want to sell the work?
• Is the next step obvious?

If the answer is no, adjust the proposal before sending. A clean document with weak scope is still weak. AI helps with structure and language, but it should not make the proposal less accountable.

Why this beats starting from a blank document

Many contractors have a template they keep copying. That works until the job is unusual, the customer asks a specific question, or the scope crosses categories. A blank document takes too long. A generic template can sound detached from the walkthrough. A free AI proposal builder gives you a middle path: bring the job details, generate a strong first draft, then edit with your own judgment.

That workflow is useful for solo operators and small teams because it does not require a big software migration. You can test it on the next real opportunity. Take the notes you already collect, organize them with the structure above, and generate a Roxy proposal. If the first draft saves you even one rewrite, the habit starts paying back immediately.

Roxy is free for up to 10 Roxy-branded proposals every 30 days. Use those free proposals to test the workflow across different job types: an HVAC replacement, a painting project, a small remodel, a roof repair, or a landscaping cleanup. When you find the note structure that consistently produces proposals you trust, make it part of your sales process.

The point is not to make every proposal longer. The point is to make every proposal clearer, faster, and easier for the customer to approve. Bring better job notes into Roxy, and the proposal draft has a much better chance of sounding like the contractor who actually walked the site.