AI Automation for Private Jet Charter Brokers
I build AI systems that read each new charter inquiry, research the person, log the deal in your CRM and have the reply drafted and waiting for your yes. A broker's day is inquiries, research and quotes, and the ones answered first tend to win, so the first draft shouldn't wait on you. Nothing is sent without your yes.
Built with Claude and Claude Code, in your own accounts. Each piece has a person's approval in the right place.
A lead engine
It reads each new inquiry, researches who's asking, logs the deal in your CRM and drafts the reply for you to review.
Inbox-to-draft triage
New mail is sorted and the replies are drafted, so you open your inbox to answers that are mostly written.
Pre-call briefing
Before a call, a short brief on the person and the deal so far, ready when you need it.
Post-flight review drafts
After a trip, the follow-up and the review request are drafted for you, so they stop getting dropped.
A silent-failure monitor
A daily check that each automation ran and did real work, with a backup alarm on separate infrastructure.
For a private aviation charter broker, I built a lead engine with Claude Code that reads each new inquiry, researches the person, logs the deal in HubSpot and drafts the reply for review. It was live when I handed it over. Two audit rounds found more than 14 defects before launch, and the whole system was moved to the cloud so no office PC was needed. Four automations were checked live at handover.
Anything that leaves your business or changes a record waits for a person's yes. That's written down before anything is switched on.
It starts with a plan, then a separate yes before any build. The route is on How an Engagement Runs. A build is a fixed price once the plan pins the scope, or hourly with a cap when it can't be known yet, and keeping it running afterwards is $150 or $400 a month. All of that is on What Goes Into a Build.
Can AI answer charter inquiries for me?
It can read each inquiry, pull what's known about the person and draft the reply, so the draft is waiting when you open your inbox. It doesn't send anything on its own. You read the draft, change what you want and send it yourself, because the reply is your name and your relationship.
Which CRM does it work with?
It logs each deal in the CRM you already use, in your own account. The one I built for a charter broker logged deals in HubSpot. If you're on something else, the plan checks first that it can be reached before anything is priced.
What happens if an automation fails quietly?
That's the part that hurts a broker most, because an inquiry nobody saw is a lost flight. So I build a monitor that checks each automation ran and did real work, with a backup alarm on separate infrastructure. If something stops, you hear about it instead of finding out weeks later.
Does it need an office computer left on?
It doesn't have to. The system I built was moved to the cloud so it didn't depend on any office PC, and four automations were checked live at handover. Where it runs is written down in the plan before anything is switched on.
How much does it cost?
A build comes after a plan, and the price comes out of that plan. It's a fixed price once the scope is pinned down, or hourly with a cap when it can't be known yet. Keeping it healthy afterwards is $150 or $400 a month. The details are on What Goes Into a Build.
It starts with a free conversation. Tell me where inquiries slow you down the most, and we'll work out together whether it's worth building at all.
