The phone goes unanswered
Customers call while your team is on a job, with another customer, or off for the night. Most people who reach voicemail simply call the next business on the list.
AI and automation for growing businesses
I build systems that answer your phone when your team cannot, follow up with every lead automatically, and take the repetitive admin off your people so they can do the work that actually needs a human.
The usual suspects
Most businesses do not have a marketing problem. They have a response problem. These are the four I see most often.
Customers call while your team is on a job, with another customer, or off for the night. Most people who reach voicemail simply call the next business on the list.
An enquiry comes in and nobody gets back to them for hours, or at all. By then they have already spoken to someone else.
Copying details between systems, chasing updates, building the same document every week. Hours a day that nobody chose to spend.
Your bookings are in one place, your customer notes in another, your invoices somewhere else. Nobody can see the whole picture of a customer.
How I help
I do not sell software licences. I look at how your business runs, find where it leaks, and build the thing that stops the leak.
An AI that picks up, has a real conversation with the caller, works out what they need, takes their details, books the appointment, and passes the call to a person when the situation calls for judgement. It works nights and weekends without overtime.
Every enquiry gets answered in under a minute, gets asked the right questions, goes to the right person, and keeps getting followed up until someone actually replies. Nothing sits in an inbox going cold.
One place where every call, message, appointment, note and file about a customer lives together. Any member of your team can open a customer and see the whole story rather than piecing it together.
Dashboards, client portals, internal tools and behind-the-scenes automations built around how your business actually works, rather than forcing your business to fit someone else's software.
What changes
This is the clearest way to explain what these systems actually do.
You never find out you lost the job.
You wake up to a booked job instead of a missed call.
You paid for the lead either way.
Every lead gets the same fast, consistent treatment.
Hours a week, and mistakes when it gets rushed.
Your team handles exceptions instead of doing data entry.
You just need to know what is slowing your business down. Tell me what happens on a normal day, where things get stuck, and what your team complains about. I will work out where automation or AI genuinely helps, and where it honestly would not be worth it.
If a problem is better solved by changing a process rather than buying technology, I will tell you that too.
Selected work
Each one started as a specific business problem. Open any of them to see what was happening before, what got built, and what changed.
Why I see the problems
Before I built software, I ran customer operations teams. I have handled the escalations, sat in the quality reviews, built the schedules, and been the person a customer complains to. That is why I tend to find the bottleneck quickly: I have usually worked in one like it.
Most people who build automation have never worked a queue. It shows in what they build.
Who this suits
These are the kinds of businesses I work with most. It is not an exclusive list. If your business runs on phone calls, enquiries and follow-up, the same principles apply.
Plumbing, HVAC, roofing, electrical, pool care and landscaping. Crews are on site, the phone rings anyway, and the first business to call back usually wins the job.
Enquiries arrive at all hours and go cold fast. Qualifying, routing to the right agent, and consistent follow-up make the difference.
Enquiry intake, customer updates and project paperwork that currently lives in somebody's phone and somebody else's spreadsheet.
Appointment handling, reminders and enquiry response, with clear rules about what a system may discuss and when a human must take over.
Client communication, delivery tracking, onboarding and the internal admin that grows faster than the client list does.
Intake, scheduling, follow-up and the recurring administrative work that sits between winning a client and actually serving them.
How it works
We talk through a normal week and find where time, customers or money are leaking.
I map what should happen instead, and tell you plainly what is worth automating.
I build the system, connect it to the tools you already use, and document it.
We run real situations through it, including the awkward ones, before it goes live.
It runs in the background. I stay reachable for when something needs changing.
Questions
Mostly businesses where the phone and the follow-up matter: home services, trades, property, clinics, agencies and professional services. The common thread is not the industry, it is that enquiries arrive faster than the team can handle them.
Usually not. Most of the time the better answer is to connect what you already have so it works together. I would only suggest replacing something if it is actively costing you more than it saves.
In most cases yes. If a tool offers a way for other software to talk to it, it can usually be connected. If it genuinely cannot, I will tell you early rather than build around a dead end.
No. You need to be able to describe what happens in your business on a normal day, and what frustrates you about it. That is the part only you know. The rest is my job.
That is not what I build. These systems handle the repetitive and the after-hours work so your people spend their time on the conversations and decisions that actually need a human. The handover to a person is designed in from the start, not bolted on.
It passes the caller to a person. Knowing when to stop and hand over is one of the most important parts of the build, and it gets tested harder than anything else. A system that guesses when it should escalate is worse than no system.
It depends entirely on scope, and I would rather look at your situation than quote a timeline I cannot stand behind. The assessment is where that becomes clear.
Yes. A good part of my work is tools that do not exist off the shelf: portals, dashboards, internal systems and automations shaped around one specific way of working.
A conversation about how your business runs day to day, where things get stuck, and an honest view of which parts are worth automating and which are not. You get that view whether or not you decide to work with me.
You do not need a specification or a technical brief. Just describe what happens on a normal day and where it goes wrong. I will tell you honestly whether I can help.
rodolfo.menguis@gmail.comProject 01
An AI receptionist on a real business phone line. It holds a natural conversation, works out what the caller needs, and knows when to put a person on.
A service company with crews out on jobs was missing calls all day. Worse, when a call did get transferred and the transfer failed, the alert arrived saying "unknown caller" with no number attached, because the way their phone line was forwarded stripped out the caller's number before it ever reached the system.
So customers were calling, failing to reach anyone, and leaving no way to be called back. Nobody in the business knew it was happening. Staff were also being woken at 4am by after-hours calls being pushed straight through to their mobiles.
An AI receptionist that answers the business number around the clock. It greets the caller, works out what they actually need, and captures a callback number it has confirmed is correct rather than one it guessed at.
From there it either books the appointment, takes a properly structured message, or warm transfers to the right person with a short spoken summary first, so whoever picks up already knows who is on the line and why.
Every caller now leaves behind something a human can act on: a name, what they wanted, and a number that actually works. Failed transfers raise an alert to the right person instead of vanishing. The owner reads a morning digest with coffee rather than taking calls at 4am.
The part that matters in a voice system is how fast it responds and how it behaves when the model underneath misbehaves. Both are measured continuously rather than assumed.
If any of this sounds like your business, the assessment is free and I will tell you honestly whether it is worth building.
Project 02
Calls, texts and emails pulled into a single timeline per customer, so nothing anyone said gets lost between channels.
Customer information was scattered. A phone call lived in one system, the text thread in another, the email in somebody's personal inbox, and the notes in a spreadsheet. When a customer rang back, whoever answered had no idea what had already been said or promised.
That means repeating yourself to the customer, promises nobody knows were made, and work falling between people.
A single record per customer that gathers everything: the calls with their recordings and transcripts, the texts, the emails, the appointments, the files and the tasks. Anyone on the team can open a customer and read the whole story from the beginning.
The team runs client delivery in one system instead of five. Anyone can pick up a customer cold and see what was said, what was promised, what is due, and where the files are. New staff stop needing a tour of six different tools.
If any of this sounds like your business, the assessment is free and I will tell you honestly whether it is worth building.
Project 03
New enquiries get answered fast, sorted by how ready they are, sent to the right person, and chased until somebody actually replies.
Leads arrived from several places at once, a website form, an ad, a phone call, and all of them landed in the same undifferentiated pile. Response depended entirely on who happened to be looking. Some got a reply in minutes, some got one the next day, and some never got one at all.
Every one of those leads cost money to generate.
A layer that sits on top of the customer system and does the chasing. A new enquiry is answered within a minute, asked the questions that reveal how serious it is, scored, assigned to the right person, and then followed up on a schedule until it gets a reply.
It stops the instant someone books or responds, so nobody gets pestered after they have already said yes.
Every lead now gets the same fast, consistent treatment regardless of who is at their desk. Nothing sits in an inbox going cold, and the business can finally see which marketing actually turns into jobs.
These are real workflows running in production right now, drawn from their live definitions. Every box is a step the system takes on its own.
If any of this sounds like your business, the assessment is free and I will tell you honestly whether it is worth building.
Project 04
Websites, client portals and internal tools built to remove one particular bottleneck, rather than general software that almost fits.
Plenty of business problems do not have a product you can buy. The work is specific: a way for clients to see their own project without emailing to ask, a page that explains service tiers clearly enough that people choose one, an internal tool that removes a job somebody hates doing every week.
Forcing that into general-purpose software usually means paying for something that does eighty percent of the job and creates admin for the other twenty.
Purpose-built tools and interfaces, shaped around how the business already works.
Screenshots taken from the live sites.
Screenshots of live pages, captured from the running sites. Click any one to enlarge.





Each of these removed a specific recurring cost: a question that no longer gets asked, a report nobody builds by hand any more, an explanation the business no longer has to give on every call.
If any of this sounds like your business, the assessment is free and I will tell you honestly whether it is worth building.