The AI front office for the trades that keep the world running
Home-service businesses live and die by the phone. Neuron gives them a number an AI answers around the clock, a CRM behind it, and a local-SEO site that produces the next call — and charges only when a job is completed.
- Pricing
- Per completed job — first ones free
- Setup
- Live in an afternoon
- Languages
- English · Spanish · Russian
Founder — Dmitry Kotov. Status: Production.
The problem is boring, which is why it is still unsolved
A missed call in field service is not a missed message — it is a customer who calls the next company on the list. Yet the person best placed to answer is on a roof, under a sink, or driving between jobs. The gap has been filled for decades by voicemail, answering services that read from a script, and family members.
The software that exists for these businesses was built for companies large enough to employ a dispatcher. It is priced per seat, takes weeks to roll out, and assumes someone in the office has time to configure it. Most operators never get past the demo.
What the platform does
Four parts, sold as one thing. The value is in the fact that they are connected: the call becomes a job, the job feeds the CRM, and the site brings the next call.
A real number, answered around the clock
Every business gets a phone number and an AI receptionist that picks up as the company, qualifies the caller, and never sends anyone to voicemail — including nights, weekends, and the hours an owner spends under a customer's sink.
The job goes straight into the calendar
The call ends with an appointment, not a note to call back. Address, service type, and time slot land in the schedule while the customer is still on the line.
A CRM the owner actually opens
Jobs, technicians, and routes on one screen. Calls, messages, and bookings collapse into a single history per customer instead of living across a phone, a notebook, and someone's memory.
A site that brings the next call
The platform generates local service pages — "AC repair" in a specific city — wired to the company's Google profile. Acquisition is part of the product, not a separate agency invoice.
The model is the point
Vertical software usually fails these customers on price and onboarding, not features. Both are design decisions here.
Priced per completed job
A small flat fee on work that actually got booked and finished — not per seat, not per minute. Revenue tracks the customer's revenue.
First jobs are free
A new business starts earning before it starts paying, which removes the reason most small operators never try software at all.
Live in an afternoon
Onboarding is a conversation, not an implementation project. Number, receptionist, CRM, and site come up the same day.
English, Spanish, Russian
The receptionist answers in the caller's language — decisive in markets where the customer and the crew often don't share one.
Distribution is built into the product
The same engine that gives a customer their site generates local service pages for their city and trade. Those pages rank, the phone rings, the AI answers, and the job completes — which is the moment the platform earns. Acquisition for the customer and revenue for the platform come from one mechanism rather than two budgets.
It also generalises. A trade and a city are parameters, not a rebuild — which is what makes going from one vertical to eight a content problem instead of an engineering one.
Talk to the founder
For investors, partners, and operators who want the detail behind the summary — unit economics, architecture, and where the platform is going next.