// process.md
How it works
Five steps, the same on every job. Price and scope are fixed in writing before any code is written, and nothing is handed over until it runs on a clean machine.
- 01
Send the spec
The brief, the rubric, any starter code and the versions your marker uses. A photo of the PDF is fine to begin with.
- 02
Scope and quote in writing
We read it properly, ask what is unclear, and confirm a fixed price and delivery date. A small advance confirms the order.
- 03
Build against the brief
Work is tracked task by task against the spec. Longer projects are split into milestones you can review as they land.
- 04
Tested handover
A repo that installs from a README, run against your test cases, with the write-up if your rubric asks for one.
- 05
Fixes and walkthrough
One round of fixes if a marker flags something, and a walkthrough of how it works so you can explain it.
Before you send anything
The quote is only as accurate as the brief. The things that change a quote most are the exact requirements (the PDF, not a summary), the rubric, any starter code, the versions your marker uses, and the real deadline with its timezone.
Milestones on bigger work
Capstones, full-stack builds and anything spanning several weeks are split into milestones — design, core build, testing, report — that line up with your supervisor meetings. You review each one before the next starts, so feedback lands while it is still cheap to act on.
The handover
- Code in a repository or zip, with pinned dependencies
- A README with install and run steps
- Test results, screenshots or outputs the brief asks for
- The write-up or documentation, if your rubric requires it
After delivery
One round of fixes is included if a marker flags something against the original brief. A walkthrough call is available on request, and Technical Viva Prep covers full rehearsal if you have to defend the work.
Changes to the brief after the quote — a new feature, a different stack — are quoted separately, in writing, before any extra work.
// checklist
Every delivery is checked against this
Spec-first
Every requirement in the brief is mapped to code or a section of the report before delivery. Nothing assumed.
Tested before it ships
Run against your test cases and edge cases on a clean environment — not just on the machine it was written on.
Readable code
Consistent style, sensible names, comments where the logic is not obvious. Code you can read out loud in a viva.
A repo, not a dump
Pinned dependencies, a README with run steps, and a sensible file layout — the way a marker expects to open it.
Explained, not just handed over
A walkthrough of the approach on request, so the work is something you understand rather than something you received.
Private by default
Your brief, code and data are never shared, reused or posted. Anything we show publicly is anonymised.
./send-brief
Send the spec. Get a fixed quote.
Paste the brief into WhatsApp with the stack and the deadline. Scope, price and delivery date come back in writing before any work starts.