About
We finish things.
Software often ships and stops there. The code goes out, the invoice goes out, and the client is left with a system they don’t fully understand and can’t run on their own. We focus on the second half: the part where the work becomes theirs.
Our name comes from τ, the constant equal to 2π. The full circle. The maths is the method.
How we work
The loop.
Every Tau project runs through the same five stages, in order, no shortcuts.
- 01
Understand the problem.
Before any proposal. Before any code. The work starts by sitting with the system, the people running it, and the history it’s grown out of. In OT and IoT this matters more than anywhere else. Buildings, factories, access networks all have decades of decisions baked in, and most of those decisions aren’t written down anywhere.
- 02
Document what’s there.
Asset registers. Engineer SOPs. Network diagrams. Protocol notes. Whatever it takes to make the site legible to someone who didn’t grow up with it. A lot of the value gets delivered here, before any new software exists.
- 03
Design the simplest thing that works.
Not the cleverest. Not the most modern. The simplest. Modern tools earn their place by being boring and well-understood, not by being new. A solution the next engineer can read on a Monday morning is worth more than one that wins an architecture review.
- 04
Build with the client steering.
Short cycles. Working software early. The client says “more of that” or “less of that” and the build adjusts. No twelve-month roadmaps that survive contact with reality for six weeks.
- 05
Hand it over properly.
Code, docs, credentials, runbooks, the lot. The client owns it. They can run it without us, change vendors without us, hire someone else without us. That’s the point of the loop closing.
Who this fits
Strong on the physical system. Thinner on the stack on top.
We work best for teams with deep domain knowledge and a thinner software bench. Master System Integrators. Smart building owners. Access control firms. Industrial companies whose strength is the physical system, not the stack on top of it.
If you have a Node app held together with hope, sitting on a BACnet network nobody fully understands, that’s the conversation.
What you won’t get
No retainers that outlive the work.
No lock-in. No juniors billed at senior rates. No twelve-week discovery phase that produces a slide deck.
We say no often. The loop only works if each stage gets the time it needs.
Get in touch
hello@tautechnology.co.uk