Material experiment / cobalt and terracotta

A paid proof of concept proposal from a software vendor to a company that wants evidence before a long contract. It covers the buyer’s numbers today, five success criteria with pass marks, what the test includes and excludes, a four-week timeline, the vendor team, a similar customer’s result and three test options whose fee counts towards the first year.

Software Proof of Concept Proposal

Overview

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Thank you for the demo last week</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">You want proof that our scheduling works with your systems and your technicians before you commit to a three-year contract.</p>

Introduction

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Where scheduling stands today</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">From your dispatch reports for the last three months and our call with your operations team.</p>

Dispatchers moving jobs by hand after sick calls and overruns

Arrivals outside the time promised to the customer

Where scheduling stands

<h2 style="font-family:var(--proposal-font-accent);font-weight:500;line-height:1.14"><span style="font-size:clamp(30px,4.2cqw,52px)">We recommend testing the five questions your team raised, each with a pass mark agreed before we start.</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">At the end you get a written result for each one: passed, passed with a limitation, or failed. Nothing is left to opinion.</p>

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">The success criteria</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Your IT and operations leads approve this table in week one. We only count a criterion as passed if your team can repeat the test.</p>

What the test answers

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">What is in the test, and what is not</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Everything below is in the recommended option, Full proof of concept.</p>

<p>Your workspace in our EU region, set up with your job types, skills and regions.</p>

A test workspace

<p>Work orders in and completed jobs back, using your SAP test system.</p>

The SAP connection

<p>Forty technicians and six dispatchers in the North region, with a one-hour training session each.</p>

Your technicians on the app

<p>A report on each criterion with the evidence, and what a full rollout would need.</p>

A written result

<p><strong>Not included:</strong></p><ul><li>Your other three regions. They follow in the rollout if you subscribe.</li><li>Changes to SAP itself. Your SAP team gives us access to the test system and an interface user.</li><li>Payroll and timesheets. Technician hours stay in your current system during the test.</li></ul>

What is in the test

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Four weeks from kickoff</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">The test starts on {{START_DATE}}. Your dispatchers keep the old tool running alongside, so no customer is affected.</p>

<p>Criteria signed off, workspace configured, single sign-on and the SAP connection tested.</p>

Set up

<p>Dispatchers build each day’s schedule in both tools. Technicians use the app on real jobs.</p>

Dispatch in parallel

<p>We run the final tests with your IT team watching and write up each criterion.</p>

Results

Four weeks

<p><strong style="font-size:1.15em">{{SELLER_NAME}}</strong><br>Account executive, {{SELLER_COMPANY}}</p>
<p>Your main contact for the test and the commercial terms. With you every week:</p>
<ul><li>A solutions engineer who has run 30 proofs of concept with SAP customers</li><li>An implementation consultant who trains your dispatchers and technicians</li><li>A security engineer for your review of hosting, access and data storage</li></ul>

Who runs the test

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Results for a similar client</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">A building services company with 220 engineers, and its proof of concept last year.</p>

Results for a similar client

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Options and fees</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">Three ways to run the test. We recommend Full proof of concept.</p>

Core test

Full proof of concept

Two regions on live jobs, with the old tool switched off for the last two weeks.

Regional pilot

<p>Fees are in USD and exclude tax. A subscription after the test is quoted per technician per month, from $38. This proposal is valid until {{VALID_UNTIL}}.</p>

Options and fees

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Common questions</span></h2>

Questions

<h2 style="font-family:var(--proposal-font-heading);line-height:1.16;font-weight:600"><span style="font-size:clamp(28px,4.6cqw,52px)">Next steps</span></h2><p style="font-size:clamp(20px,2.1cqw,23px);line-height:1.5">How we start.</p>

Software Proof of Concept Proposal - Preview