How to write an automation integration proposal

A proposal is the first physical thing your customer holds. Before they've seen your team on-site, before they've watched you commission a cell, before they've heard you troubleshoot a PLC issue at 11pm — they have your proposal. It does a lot of work.

Most SI proposals fail not because the engineering is wrong, but because the document doesn't communicate the engineering clearly. This guide covers what goes in a winning automation proposal, section by section, and why each part matters.

The sections that matter

A complete automation proposal has ten sections. Not all of them carry equal weight.

Green rows are the sections most likely to determine whether the project moves forward

Executive Summary is the most important section and the one most integrators write last, as an afterthought. Write it first, or at least rewrite it last with fresh eyes. Your customer's VP of Operations may read only this page. It should state the problem, the proposed solution, the investment range, and the payback period. No more than one page.

Current State Analysis shows the customer you understand their situation before you propose a change to it. Describe the existing process — what's manual, what's inconsistent, what's slow. Quantify where you can: current cycle time, labor headcount, defect rate. This section builds the justification for everything that follows.

Proposed Solution is where most integrators spend most of their writing time, and where customers spend least of their reading time. Keep it to three or four paragraphs. State what the system does, how it addresses the pain points from the Current State, and what makes your approach appropriate for this application. Don't bury the lead with robot specifications — lead with outcomes.

Equipment Specification gives customers the technical detail they need to evaluate the proposal. List the major components: robot model and reach class, end-of-arm tooling, safety system, controls architecture, vision system if applicable. Include model numbers. Customers and their engineering leads will look these up.

Scope of Work is the most legally consequential section. Be specific about what's included and, equally importantly, what's not. "Site preparation" is a common source of disputes — define who supplies compressed air, who runs conduit, who pours foundations. The more explicit the exclusions, the fewer change orders you'll fight over later.

Project Timeline should show phases, not just a delivery date. Engineering and design, procurement, fabrication, FAT, site installation, SAT and commissioning, warranty. Customers want to know when they'll see progress, not just when the project ends.

Investment Summary frames the price before showing it. One or two paragraphs that restate what the investment covers — equipment, engineering, installation, commissioning, training, documentation — before the customer sees the number. Payment milestones go here: typically 30% at order, 40% at FAT, 30% at SAT.

ROI Analysis is the slide your internal champion uses to justify the project to their CFO. Labor savings, throughput gains, quality improvement, payback period. If you can show a 14-month payback on a $200K investment, you've made the decision easy. Use real numbers from the current state analysis you wrote earlier.

Terms and Conditions protects you. Quote validity, change order process, warranty scope, limitation of liability. Keep it readable — dense legalese gets ignored, which means no one knows what they agreed to.

About Us closes the document. Two paragraphs: who you are, what you've built, what makes you the right integrator for this project. If you have a relevant reference project, mention it here.

The common mistakes

Leading with your company instead of their problem. The first paragraph of the executive summary should describe the customer's situation, not your certifications. Nobody wants to read about your founding story before they know you understand their problem.

Scope that's too vague. "Installation and commissioning" is not a scope. "Mechanical installation, electrical terminations, PLC programming, robot path programming, operator training (one 4-hour session), and SAT" is a scope.

ROI math that doesn't add up. If you claim 18-month payback but the numbers in the Investment Summary and ROI Analysis don't produce that result, the customer's engineer will notice. Run the math. Show the calculation.

Pricing without context. "$187,000" on a line is a different read than "$187,000 — covering equipment, engineering, fabrication, installation, and a 12-month warranty." Frame what the number includes before showing it.

Inconsistent equipment references. If you mention a "FANUC M-20iD/25" in the Equipment Specification section and a "FANUC 20kg payload robot" in the Proposed Solution, it looks like two different people wrote the document without talking to each other. Use consistent model references throughout.

How long should a proposal be?

Long enough to answer every question a technical buyer would have. Short enough that an executive can read the Executive Summary and Investment Summary in five minutes and know whether to keep reading.

In practice: 12–20 pages is about right for a mid-complexity project ($100K–$500K). Under 8 pages feels thin. Over 25 pages and you're writing for yourself, not your customer.

The speed problem

The integrators who win proposals aren't always the integrators with the best engineering. They're often the ones who responded first with a credible document. A slow turnaround — even when the proposal is excellent — signals to the customer that you might be slow on the project too.

Most integrators can put together a good proposal. Few can put one together in a day.

ScopeDraft generates complete automation proposals in under 10 minutes — scope of work, equipment specs, pricing tables, and ROI analysis. Try it free.