December 2024: part payments, receipts and knowing who owes you
December 2024 was about the end of the invoice: part payments, receipts, and a clear view of who owes what and how old the money is. Here is what we built and why.
Blog
Wedi'i dagio “Building TradeYoke”
How TradeYoke was built, month by month from January 2024: customers and jobs, invoicing, quoting, surveys, inspections, maps and live monitoring.
Erthyglau diweddaraf
November 2024: a ledger that cannot be quietly edited
November 2024 was about trust. The invoicing ledger only ever adds entries: a correction is a new line, not an edit. Here is why that makes the books easier to trust.
October 2024: why invoicing came next, and what it had to get right
With customers, jobs and a diary working, the next question was money. October 2024 started the invoicing work: why it followed the visit, and the three things it had to get right.
September 2024: getting an existing round in without retyping it
Nobody wants to retype four hundred customers. September 2024 was about import: check the file first, show what will happen, never silently merge, and flag the duplicates.
August 2024: a diary that fills itself from the round
August 2024 was the diary. Set a frequency once and every future visit appears on the schedule; move a visit by dragging it. Here is how the board came together.
July 2024: a library for the paperwork, filed where you will look
Once customers and jobs worked, the paperwork started to pile up: photos, certificates, notes and PDFs. In July 2024 we built a document library that files things where you will look.
July 2024: customers and jobs working end to end for window cleaning
July 2024 was the month the customer list and the job list started to work together for window cleaning. Here is what that meant, what was missing, and what we learned from using it.
One codebase and offline-first: the early engineering decisions
Two decisions made in the first half of 2024 shaped everything since: one shared codebase for the web and the apps, and a phone that keeps working when the signal drops.
Why we published our terms and privacy notice from the start
In June 2024 we first published TradeYoke's terms of service and privacy notice. Why we think a software business should write its rules down early, and how they are kept up to date.
Designing a job that repeats: every four weeks, for years
A window clean happens again and again. May 2024 was about designing a job that repeats: its frequency, its next-due date, and what happens when it is paused or skipped.
The customer record a window cleaner actually needs
April 2024 was about the customer. What does a window cleaner need on a record: the address, the price, the rhythm, how to get in, and what they owe? Here is how we designed it.
What is a round? Designing it in software
In March 2024 the question was simple and not easy: what is a round, in software? A named list of stops, each with a frequency and a next-due date, in an order you can change.