Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More
1 contribution to Brendan's AI Community
I stopped putting business logic in prompts. Here's an insurance quote app in GHL AI Studio that gets the price right every time.
If you're building in GoHighLevel AI Studio and your pricing or calculation logic lives in a prompt, you've probably seen it: the agent gets the number slightly wrong, the app and the chatbot disagree, and debugging means guessing. I built a home insurance quote demo to show a different way: keep the logic outside the prompt, in one deterministic engine, and let GHL call it. What's in the demo: • 11 questions (ZIP, construction, coverage, roof age, claims, deductible…) • 12 lookup tables • Stacked discounts with a cap, plus a minimum premium • An approval rule that sends risky quotes to a human How it works: 1. The engine lives in Quotix (I built it, so I'm biased). 2. GHL connects to it through MCP. 3. AI Studio asks Quotix for the schema, meaning which questions to ask, and builds the app around it. 4. When a user submits, Quotix calculates the price in under a second and returns a line-by-line breakdown: base rate, every factor from every table, every discount. When something looks off, you can see exactly why. The AI never does the math, so it can't make up a price. The same engine can sit behind a GHL chatbot, Voice AI, a form or a full app, and they all give the same answer. Video chapters: 0:45 how GHL and Quotix talk to each other 1:36 the 12 lookup tables 3:26 the formula 4:30 live test with the breakdown 5:21 the app AI Studio built from the schema Test home for the app: ZIP 33432, Masonry, $500k coverage, roof 0–5 years, protection class 3, under 1 mile from the coast, no claims, Standard tier, $2,500 deductible, no security, no bundle. You should get $3,729.90. 🔗 References • Loom walkthrough (6 min): https://www.loom.com/share/51b17c2a310748ffa53cf94438d09a69 • GHL AI Studio app: https://insight-flo-9783e81c.vibepreview.app • Word doc with the insurance data (questions, 12 tables, formula): https://docs.google.com/document/d/1y1mtmsR_Hfsou_6IUn45amwxd8C7VBUPXf3wPovKLvU/edit?usp=sharing
I stopped putting business logic in prompts. Here's an insurance quote app in GHL AI Studio that gets the price right every time.
0 likes • 3d
@Zubair Aqeel Thank you for your feedback! We do have a test scenarios that user can run to check if the updates affect any logic.
0 likes • 2d
@Maya Collins Thanks Maya! To be upfront, this one is a demo with fictional rates, so I don't have real traffic numbers yet. In the demo, one rule sends a quote to a human: 3 or more claims in the last 5 years. That's a risk call an underwriter should make, not a formula. When it triggers, the engine flags the quote as approval_required instead of returning a price. The agent tells the customer "someone will review this" and never makes up a number. A few cases get stopped outright instead, like a roof over 20 years or a ZIP we don't cover. Those come back as invalid_input, so the AI can't guess a price there either. How you'd handle it. Would you route approvals to a person in the CRM, or let the AI ask follow up questions first?
1-1 of 1
Diaa Juneidi
4
77 points to level up
@diaa-juneidi-3245
Founder & builder interested in AI, SaaS, and automation. Always learning, building, and connecting with fellow makers. 🚀

Active 12m ago
Joined Nov 14, 2026
Powered by