How a work order works

The five sections

Read from top to bottom. Payment unlocks only once the intake reaches 80% complete and every required section is met.

1. 01

   Domain & SKU

   Choose the technical domain and the fixed-scope deliverable you need. Each deliverable has a defined outcome and a fixed price; the priority tier sets the turnaround — overnight (under 14 hours) or standard (48 hours).

   What good input looks like

   • One domain and one deliverable — if a dependency is involved, order the primary deliverable and describe the dependency in the Target State.
   • The priority tier that matches your real deadline. Early delivery is always the goal, never a stretch.
2. 02

   Current State

   Describe what exists today: the architecture and its key components, the stack and versions, the friction you want removed, and a link to the primary repository or architecture diagram.

   What good input looks like

   • One or two plain paragraphs on the architecture and how the pieces fit together.
   • Stack and versions one per line, with versions where they matter.
   • The symptoms that prompted the order — slow, manual, fragile or failing — with sanitised error excerpts if useful.
   • A valid HTTPS clone URL or a link to the diagram or exported inventory.
3. 03

   Target State

   Describe what should exist when the work is complete: the deliverable, measurable benchmarks, the definition of done, and at least two testable acceptance criteria.

   What good input looks like

   • The end artifact, written as an outcome rather than a task list.
   • Numbers beat adjectives — latency, throughput, coverage, scan counts or cost.
   • At least two criteria a reviewer could check objectively; suggested templates are offered if you are unsure.
4. 04

   Constraints

   Set the boundaries: what must not change, which compliance standards apply, the approved regions, freeze windows, pinned versions and the target deadline.

   What good input looks like

   • Name the forbidden changes explicitly so nothing is touched by accident.
   • Select only the standards that genuinely apply — “None apply” is a valid answer.
   • Freeze windows and the deadline in the timezone you work in.
5. 05

   Access & Verification

   Hand over read-only repository access or a detailed written handover, confirm the environments in scope, and verify any required access. Tokens are encrypted in your browser before they leave the device.

   What good input looks like

   • A read-only token is sufficient; HTTPS clone URLs only.
   • List every environment the work may touch, and the source material or endpoints the team needs.
   • Your contact email is used for the private dashboard and delivery only.

• Cloud & Infrastructure as Code

  Infrastructure as Code Codification

  A logistics firm's shipment-tracking app, rebuilt as modular, version-controlled infrastructure code.

  Priority Overnight (under 14 hours)

  See the worked example

• DevSecOps & Code Hardening

  Static Analysis & SAST Integration

  A manufacturing firm's internal machine-status app, hardened with a static-analysis quality gate.

  Standard (48 hours)

  See the worked example

• Observability & Site Reliability

  Observability Stack Suite

  A streaming-media startup's ingest API, wired up with metrics, dashboards and alerts.

  Priority Overnight (under 14 hours)

  See the worked example

• APIs & Systems Integration

  API & Webhook Integration

  An environmental testing lab's results API, bridged to a partner with retries and dead-letter capture.

  Standard (48 hours)

  See the worked example

• Solutions Architecture & Technical Documentation

  Technical Documentation Suite

  A retail-analytics consultancy's internal data tool, documented into a navigable docs suite.

  Priority Overnight (under 14 hours)

  See the worked example

• Coding, Programming & Scripting

  Codebase Modernization Task

  A forestry company's legacy weekly-report scripts, modernised into one tested, installable package.

  Standard (48 hours)

  See the worked example

• DataOps: Data Engineering, Analysis & Science

  Custom ETL & Data Pipeline

  A solar farm operator's inverter-telemetry scripts, rebuilt as one orchestrated, idempotent pipeline.

  Priority Overnight (under 14 hours)

  See the worked example

• Technical & Scientific Document Writing

  Structured Literature Review

  A legal-research consultancy's structured literature review for a non-technical policy audience.

  Standard (48 hours)

  See the worked example