Dispatch tool,
redrawn.
Nine weeks to take the dispatch screen from something operators tolerate to something they reach for at four in the morning.
What we understood
The brief in our words.
Operators mis-key 6 percent of jobs. The screen was designed for a desk and is used on a tablet, in gloves, in the dark. Nobody wants a redesign. They want the mis-keys to stop.
If this is not the problem, tell us before we start. Everything below is priced against this sentence.
Scope
Six pieces of work.
One night, one morning, on site, no interviews. We watch and write down every correction.
Every mis-key we saw, grouped by cause rather than by screen.
Built in the browser at tablet size with real job data, not pictures.
Same two shifts, same operators, measured against the inventory.
Production components in your repository, with your team pairing.
Written rules for each decision, and a week of us on call.
Not included
Said plainly.
We will not touch the dispatch API. If it needs changes we will write them up for your team.
The tablet runs a browser. If that changes, this proposal does not cover it.
After week nine we are gone. A retainer can be discussed separately and is not assumed here.
Terms
Short on purpose.
| Item | Terms |
|---|---|
| Payment | 50 percent on signature, 50 percent on handover. Thirty day terms. |
| Ownership | Everything we make is yours on final payment, including working files. |
| Changes | Scope changes are priced in writing before work starts. No change is assumed. |
| Cancellation | Either side, two weeks notice. You pay for work done, nothing more. |
| Confidentiality | We will not name you as a client without written permission. |
Sample proposal. The client, the studio and the price are invented.
Nine weeks, one number to beat.
Mis-keys below two percent, measured the same way we measured them in week two.
Accept the proposalSingle HTML file with no build step. Type: Inter Tight, served by Google Fonts under the SIL Open Font License.