You are
buying
judgement.
RTLS projects do not usually fail on hardware. They fail on decisions made in the first two weeks — the wrong technology for the building, zones drawn from a floor plan instead of from behaviour, a pilot scoped so narrowly it could never prove anything.
Fluidity exists because those decisions are worth getting right, and because the people making them are usually being advised by someone with a product to sell.
Dan
Founder & principal consultant
Dan has been tracking things since before the industry had a name for it — an RFID system for construction sites in the early 2000s, then Decawave's first UWB development kits, years before those chips ended up in smartphones. Twenty-something years on, he has sat on every side of the table: engineering teams, sales floors, CEO and CRO chairs, across Australia and the United States. The common thread never changed — somebody always wants to know where their things are.
Amber
Technical documentation & operations
Every Fluidity engagement produces two systems: the one on the ceiling, and the paper trail that lets your own team run it. Amber owns the second. She turns surveys, design decisions, commissioning results and operating procedures into documentation a client can genuinely work from — and keeps it accurate as the site evolves, which is where most documentation quietly dies. When we say every decision is written down with its reasoning, she is the reason that stays true.
Small, on purpose.
Fluidity is deliberately lean. You deal with the person who did your survey and designed your system, not an account manager relaying questions to an engineering team in another timezone. Delivery is supported by a small group of specialist developers who have been building this technology with us for years.
- No sales layer. The first call is with the person who will survey your building.
- A specialist bench on call. Around the core team sits a network of industry specialists — RF and antenna engineers, firmware and mechanical designers, certification and integration experts — built over twenty years and brought in when a project demands depth we do not need every day. You still deal with one accountable partner; the bench works to our design.
- Vendor-agnostic by structure. We hold partner accreditations so we can deploy properly, not so we can be obliged to recommend them.
- Candour as policy. If RTLS is the wrong answer, or the wrong answer this year, you will hear it early — when it is still cheap to change course.
- Documentation, always. Every design decision is written down with its reasoning, so a future team can understand why the system is the way it is.
Talk to the person who does the work.
No qualification call, no discovery form to fill in first.