The Lab
Where we build, test and explore what's possible
Not a portfolio. These are our own builds — the things made to answer a question, scratch an itch, or find out whether something was actually feasible before recommending it to anyone.
Every one is labelled with the state it's genuinely in — working and still being built on, or a prototype that proved a point. Saying which is more useful than implying they all shipped.
- Working
Digital Presence Command Centre
Content & marketing · Functional, still being built on
A content and digital-presence system: crawl a business's own site, turn what's verified into reusable knowledge, and generate multi-channel content grounded in it — with a human approval gate in front of anything that publishes.
- Working
OzyProject
Business software · Functional, still being built on
Project management built around contribution evidence — the board produces a defensible record of who did what, and paces work in weeks rather than arbitrary dates.
- Working
OzyNetGuard
Security · Functional, still being built on
Local network cleanup, audit and security hardening — discover what's actually on a network, document it, and tighten it up.
- Working
OzyJarvis
AI & automation · Functional, still being built on
A self-hosted, local-first AI assistant and automation platform running on a single mini-PC. JARVIS-inspired in function only — no fantasy, no cloud dependency.
- Prototype
OzyMarketAnalyst
Data & AI · Proves the idea, not production
Market intelligence that computes the numbers deterministically and uses AI only to explain them — with every score traceable and the uncertainty always visible.
- Prototype
OzyExercise
Health tech · Proves the idea, not production
AI-assisted exercise routines for people recovering from injury or surgery — generated only from a qualified clinician's documentation, never from self-description.
Why this is here
The range is the point
Business software, network security, AI automation, data analysis, health tech. Working across all of it is why we can look at a problem from more than one angle — and why we can usually tell you which layer it's actually in before anyone starts building.
It's also the honest answer to "have you done this before?" Often the answer is yes, in our own time, on our own hardware, because we wanted to know how it worked.
Got something odd?
The interesting problems usually start as "can you even do that?"
If you've got something that doesn't fit a normal brief, that's often the conversation we enjoy most. Worst case, we'll tell you honestly that it isn't worth building.
