We build production software for funded startups and SMEs, and we write down what we learn as we go. Engineering decisions, product calls, and what AI actually changes about both. One post every Tuesday, and nothing sits behind an email wall.
Latest
We ship production software with coding agents every day. That is exactly why we can be specific about the six task types they still get wrong on us.
21 July 2026 · 10 min read · ai · engineering
Read the post14 July 2026
14 min read
Yes, when you place an AI system on the EU market or its output is used in the EU. The dated timeline for a UK company selling into Europe, with what moved.
ai · regulation
7 July 2026
9 min read
Probably yes, and two pages covers it. The sections a small company's AI policy needs, a skeleton to adapt, and the agent rules we run on ourselves.
ai · regulation
30 June 2026
9 min read
Most companies owe far less AI paperwork than they fear. The five records worth keeping whatever your risk tier, who asks for each one, and when.
ai · regulation
23 June 2026
10 min read
Most SME software is not high-risk. Annex III lists eight use cases, and if yours is not one of them you can settle the question in an afternoon.
ai · regulation
16 June 2026
9 min read
Providers develop AI systems and put their own name on them. Deployers use them at work. Most UK SMEs are deployers, and the two roles owe different things.
ai · regulation
9 June 2026
13 min read
The architecture we ship for field work: local store as source of truth, an event outbox with dependency edges, foreground sync, one database per engineer.
engineering
2 June 2026
8 min read
Four failure modes: a frozen interface, a silent overwrite, a conflict found weeks later, and a request that stalls instead of failing. With the test for each.
engineering
26 May 2026
8 min read
Offline evidence survives an audit when the record keeps capture time, sync time, provenance and a change history. What an auditor asks, and what to store.
engineering · industry
19 May 2026
9 min read
How offline apps settle conflicting edits: last write wins, field-level merge on per-field timestamps, or CRDTs. What each costs, and when each is enough.
engineering
Book a free 30-minute call. We'll dig into your idea, your stack and your timeline, and give you an honest read on what it will take to build and launch. You'll leave with a clearer plan whether or not you hire us.