Home › Case study
Case study
A construction company in Palm Beach County came to us with a problem every small contractor recognises. The office ran on a shared inbox, a calendar, and a Drive folder. Every job lived in all three. Nobody could answer "where are we on the Ruiz house" without opening each one and reading.
They did not want new software. They wanted the software they had to answer questions. So that is what we built.
You type a question the way you would ask a person. "Anything from Tomas about the windows?" "What's on Thursday?" "Draft a reply to Marcy about the inspection." The assistant reads the inbox, the calendar and the files, finds the specific thread, event or document, and shows you what it found before it does anything.
Every action that changes something — sending, booking, moving, cancelling — is a proposal with a confirm button. The card shows the exact record it resolved: this email, to this person, on this date. Destructive actions look different from ordinary ones. Nothing goes out because the assistant guessed.
The first build was a scripted demo. It matched a handful of patterns and returned canned answers, and a formal evaluation of 228 test prompts scored it under 3 out of 10. The findings were specific and they were right: ask it to cancel a meeting and it offered to create one. Ask it to delete a draft and it showed a Send button. Ask about one person and it answered about a different one.
We rebuilt the core around three rules. Every request resolves to a specific intent and a specific target before anything happens. Every lookup returns zero, one, or many matches — one match acts, many asks which, zero says so. And nothing gets to say "sent" or "booked" unless it is holding a receipt from the system that did it. Fifteen regression tests, one per finding, make sure the old failures cannot come back quietly.
Mail, calendar and files in tabs, and the assistant in a fourth. Ask it something, it answers with the real record and a proposal. Confirm, and it does it. Leave the tab and come back, and the conversation is still there. It does not replace the tools; it sits on top of them.
The owner's summary after a week: the Tuesday-evening questions that used to wait until Wednesday morning get answered on Tuesday evening.
The rebuild took under two weeks. A system like this is priced as a project plus a monthly amount for hosting and upkeep; the numbers are on our pricing page. Connecting it to a live Google Workspace is the last step and needs the client's admin to approve the app, which is a ten-minute task on their side.
If your business runs on an inbox, a calendar and a shared drive, this is built for you. See what it costs or call 561-236-7203.