Built by Novigent.
Two kinds of work live here: products we built and operate ourselves, and custom systems built for a client's own operation. Both start from the same place — understanding how the work actually happens before writing any technology.
Every case study starts with the same three questions: what did the operation look like before, what does the system handle now, and what changed as a result? Wherever possible, we support the answer with measurable operational data. Client information is published only with permission — which is why some of the work below is described by what it does rather than by numbers we haven't been given permission to publish yet.
AgentFlow AI
The operating system built for real-estate agents and brokerages. It started as an internal tool, built to solve Co-Founder Patrick Tohme's own problem working the Dubai secondary market, before Novigent turned it into a standalone product. That origin matters: every workflow in AgentFlow AI was shaped by a real desk running real listings, not a spec sheet.
Today it connects five parts of the job that used to live in separate tools — lead generation, owner outreach, day-to-day communication, follow-up, and property matching — into one CRM layer, so a broker's pipeline stays visible instead of scattered across calls, WhatsApp threads and spreadsheets.
Developed by Novigent. Built from real secondary-market operations.
ABOUT AGENTFLOW AI → OPEN THE APP ↗
Joujou
A custom operational platform for an NDIS support-coordination business in Australia, bringing participant information, compliance, documentation, care-team coordination, funding oversight and reporting into one connected system.
NDIS coordination work is unusually document-heavy: every participant carries a funding plan, a compliance file and an ongoing record of support delivered. Joujou's AI-assisted workflows are built to turn everyday communication — calls, notes, updates from the care team — into structured records automatically, so required actions stay visible instead of buried in someone's inbox.
Currently in development, following the same Diagnose → Build → Operate process as every Novigent engagement.
Both of these started the same way.
Diagnose
We mapped how the operation actually worked — its workflows, communication, responsibilities and repetitive work — before writing a line of code.
Build
The blueprint became technology: custom systems, automation, AI and integrations designed around the requirement, not a template.
Operate
We stayed involved after launch, maintaining the system and keeping it aligned with how the business kept evolving.
See what a system like this could look like inside your business.
Discuss Your Project