Handee

Handee was our own product. It was built for companies that run many sites, and the contractors who work on them. It tracked each contractor's credentials, sent out work orders, compared quotes and checked invoices.

Your business has its own version of this work: order entry, invoices matched by hand, paperwork to chase.

• Many organisations, one system. It was built so that every customer organisation would share one database. Each organisation's data had to stay apart from the others'.
• More than one country. It was built for property portfolios across Europe. Its reference data covered 37 trades, 178 credential types and 30 jurisdictions.
• One builder. Piotr Gospodarczyk wrote all 848 commits himself.

The first commit was on 12 May 2026. Version 1.0.0 went into production on 4 July 2026, 53 days later. Its launch post of 15 July 2026 said it was live in Ireland and the UK.

• Reminders before a credential expired. Contractors were reminded 30 days ahead on every plan, and 30, 14, 7 and 1 days ahead on paid plans.
• Suspension when a credential lapsed. A contractor was suspended automatically when a credential lapsed, and restored on renewal.
• Quotes side by side. It put contractors' quotes into one format and showed them side by side, for the operator to award or reject.
• Invoices checked against the quote. It drafted a contractor's invoice from the accepted quote's lines. On submission, it flagged any line more than 10% off its quote line, and each organisation could change that threshold. The operator then approved, disputed or rejected the invoice.
• Data kept apart, hosted in Ireland. Each customer organisation's data was kept apart in the database itself. Handee ran on Amazon Web Services in its Ireland region.
• Account details wiped automatically. Ninety days after an account closed, the person's name, email address and login credentials were wiped automatically. Work orders and invoices were kept for an auditor three years later.
• Legal paperwork up front. Its data processing agreement and subprocessor list were published, so a buyer need not ask for them.
• Running costs watched. By 10 July 2026, six days after the production release, its infrastructure code held a monthly cost budget with spending alerts.

Software needs tests so that a change in one place does not quietly break another. Handee's code carried its own tests.

At version 1.9.0, its last release, Handee had 552 test files. The Python tests held 8,346 test functions. Seven test files drove a browser through the app from end to end.

The first tagged release came 24 days after the first commit. Handee shipped 34 tagged releases between 5 June and 6 August 2026.

Handee had no paying customers between its production release on 4 July 2026 and 30 August 2026 (self-reported). So we stopped it on running cost: we decided and switched it off on 30 August 2026 (self-reported).

We built before we sold, and that was our mistake. Now we test demand first.

Every engagement includes a small trial on real work. Every engagement has a fixed scope and a fixed price.

If manual admin eats hours in your business, AI Automation and Agents automates one defined workflow end to end. If your team uses ChatGPT without training or an agreed policy, the AI Literacy Workshop covers safe use with company data. If you need a new product built, Product and MVP Development runs from first commit to first paying user, with weekly demos.