Takes the calls
Ivan answers the phone, handles the routine questions, and routes anything that genuinely needs a person — without callers waiting on hold for someone who is already with a client.
A locally hosted AI receptionist and assistant, built for professional practices that cannot put client data in someone else's cloud.
Ivan handles the front-of-house work a practice runs on — the calls, the scheduling, the intake, the endless small acts of organization. The difference is where it runs.
There is no API call to a third party and no client file sitting on hardware you have never seen. Ivan is installed on a machine in your office, and the confidential information it touches stays inside your own network, under your own control.
That is only practical because the models underneath are small and fast enough to run on one machine in your office. Making them that small without making them worse is exactly what Nothing Inc. researches.
Ivan answers the phone, handles the routine questions, and routes anything that genuinely needs a person — without callers waiting on hold for someone who is already with a client.
New enquiries get asked the right qualifying questions, in your order, every time. What comes back to you is a structured intake instead of a sticky note.
Scheduling, confirmations, and reschedules are handled in conversation, against your real calendar and your real availability rules.
Calls, notes, and client details land somewhere structured and searchable rather than scattered across voicemail, inboxes, and memory.
This is the foundation, not the ceiling — more of the practice workflow moves onto Ivan as the product grows.
Ivan's runtime is designed for desktop AI hardware — an NVIDIA DGX Spark or an ASUS Ascent GX10, both built on the GB10 superchip with 128 GB of unified memory. That is the whole deployment: a single machine on your network, with no rack, no datacenter, and no monthly bill for someone else's GPUs.
If your files are privileged, regulated, or simply nobody else's business, “we promise we won't look” is not an architecture. Keeping the data on your own hardware is.
Ivan is not generally available. The attorney who owns a firm wants to pilot it, and we're preparing for that now — tailoring Ivan to how a legal practice actually runs rather than how we imagined it might.
That is deliberate. A receptionist for privileged work is not something you can design in the abstract and ship; it earns its place by surviving a real front office. What we learn from that first practice is what Ivan becomes.
If your practice is the kind that can't put client files in someone else's cloud, tell us how your front office runs today — we'll keep you posted, and what you tell us shapes what Ivan becomes.