Five fixed-scope engagements. Most of the work is the build. Three of the others exist because software built on product data nobody can trust is expensive theatre — so if the data is the problem, we fix that first. The fifth is for the opposite situation: the product is already built, quickly and cheaply, and nobody has checked whether it was worth building.
Web platforms, the data model underneath, the integrations either side, and the field devices when the model reaches into the physical world. Rails and Next.js on the server, edge agents on the hardware, built so the model on paper actually runs in production.
02 / Claims auditAn item-by-item audit of every environmental, origin, and sustainability claim on your webshop, product pages, packaging copy, and social channels — each one sorted into keep, keep with evidence attached, or remove before the new EU rules start being enforced. The register also shows which claims are worth building on.
03 / Product dataOrigin fields, batch identifiers, immutable records, and an audit trail — designed into your product data model, webshop, or PIM, so that a claim on the product page can be traced back to the batch it actually came from — and so the same data can carry a new business model, not just a compliance answer.
04 / DocumentationOmavalvonta and origin documentation for small producers and wholesalers — generated from records you already keep, instead of retyped by hand every time a professional-kitchen buyer asks for it. Paperwork stops being the reason wholesale accounts stay closed.
05 / ValidationTwo weeks that turn “we are building X” into a written list of what has to be true, the cheapest test for each of those things, and a decision rule agreed before the data arrives. Where the fastest test is a working artefact, we build the artefact — a landing page, a clickable prototype, a thin slice that runs.
If you know what you want built, start with the build. If the product data is the thing you are unsure about, start with the audit — it is the cheapest way to size the problem. If you are not yet sure the thing should exist, start with the validation sprint.