# work order

A template for describing a job well enough that I can price it and start it
without three rounds of clarifying emails. Delete anything that doesn't apply —
a short honest answer beats a padded one.

You can paste this straight into the form at oddjob.justin06lee.dev/request, or
fill it in here and attach the file.

---

## the one-liner

_What is it, in a sentence a stranger would understand?_

## the problem

_What is happening today, without this thing? Who does it annoy, and how often?
This is the part I actually work from — be concrete. "We copy bookings from a
Google Form into a calendar by hand, about 20 a week" is worth more than
"we need better booking."_

## what "done" looks like

_How will you know it worked? A number, a workflow that disappears, a page that
exists. If you can't tell me when to stop, I can't tell you what it costs._

## who uses it

_Just you? A team? The public? Roughly how many, and on what — phone, desktop,
both?_

## what already exists

_Repos, designs, a half-finished version, a spreadsheet doing the job today.
Links are fine. Say if there's nothing._

## constraints

_Anything that isn't negotiable: a stack you're locked into, a host, a
compliance rule, a date tied to something external, a brand to match._

## explicitly not this

_The most useful section on this page. What are you NOT asking for? Naming the
edges is how a quote stays a quote._

## budget

_A band is fine: under 1k / 1k–5k / 5k+. If you genuinely don't know, say what
the problem costs you today and we'll work backwards._

## timing

_When do you need it, and what happens if it's late? "Whenever" is a real
answer and often the cheapest one._

## anything else

_Context that doesn't fit above. Previous attempts, opinions you hold strongly,
things that have gone wrong before._

---

_Template from oddjob.justin06lee.dev — book a call instead at
coffee.justin06lee.dev._