Anyone else hit backend walls when vibe-coding client apps?

Been noticing more agencies building custom apps for clients using Cursor, Lovable, v0, Bolt, etc. instead of forcing everything into GHL.

Quick question if you're doing this:

Where does the vibe-coded app fall apart?

The UI is easy now - you can ship a beautiful client portal in a weekend. But then what breaks?

Payments? Multi-user permissions? Scheduling logic? Job tracking? Pricing rules?

What's the backend piece you keep trying to hack together in the AI-coded app that you wish was just an API call away?

reddit.com
u/Fluffy-Resolution390 — 4 days ago

For those guys expert in handling complex pricing?

I’ve been working on a engine that fixes bot pricing hallucinations 100% of the time, no matter how complex the price book is.

Is anyone open to testing it on a sub-account and giving me some honest feedback?

Thanks in advance!

reddit.com
u/Fluffy-Resolution390 — 25 days ago

For those guys expert in handling complex pricing?

I’ve been working on a engine that fixes bot pricing hallucinations 100% of the time, no matter how complex the price book is.

Is anyone open to testing it on a sub-account and giving me some honest feedback?

Thanks in advance!

reddit.com
u/Fluffy-Resolution390 — 26 days ago
▲ 0 r/CRM

I've been building custom software for a while, and one problem keeps coming up

Pricing.

Most agencies I've spoken with end up using one of these approaches:

  • A static price list
  • A calculator in Google Sheets
  • Custom values and workflows
  • Manual quotes from a salesperson
  • Sending the lead to another quoting tool

That seems to work for simple jobs, but it gets complicated quickly.

Things like:

  • travel distance
  • emergency fees
  • different service areas
  • commercial vs. residential
  • customer-specific discounts
  • minimum margin requirements
  • technician approval for larger jobs

are difficult to manage inside a traditional CRM.

I've been building a pricing engine that sits between customer intake and CRM like GHL. The idea is that forms, AI agents, APIs, or webhooks send the request to the pricing engine, it applies the company's pricing rules, generates a proposal, and then syncs everything back into CRM.

I'm not launching or selling anything yet.

I'm trying to understand how agencies are solving this today and whether I'm solving the right problem.

A few questions:

  • How are you currently calculating quotes?
  • What causes the most mistakes?
  • If you could automate one part of your pricing process, what would it be?

If anyone is interested, I'm also looking for 5–10 agencies willing to test what we've built and give honest feedback before we officially launch.

I'd really appreciate any thoughts.

reddit.com
u/Fluffy-Resolution390 — 1 month ago

I've been building custom software for a while, and one problem keeps coming up

Pricing.

Most agencies I've spoken with end up using one of these approaches:

  • A static price list
  • A calculator in Google Sheets
  • Custom values and workflows
  • Manual quotes from a salesperson
  • Sending the lead to another quoting tool

That seems to work for simple jobs, but it gets complicated quickly.

Things like:

  • travel distance
  • emergency fees
  • different service areas
  • commercial vs. residential
  • customer-specific discounts
  • minimum margin requirements
  • technician approval for larger jobs

are difficult to manage inside a traditional CRM.

I've been building a pricing engine that sits between customer intake and CRM like GHL. The idea is that forms, AI agents, APIs, or webhooks send the request to the pricing engine, it applies the company's pricing rules, generates a proposal, and then syncs everything back into CRM.

I'm not launching or selling anything yet.

I'm trying to understand how agencies are solving this today and whether I'm solving the right problem.

A few questions:

  • How are you currently calculating quotes?
  • What causes the most mistakes?
  • If you could automate one part of your pricing process, what would it be?

If anyone is interested, I'm also looking for 5–10 agencies willing to test what we've built and give honest feedback before we officially launch.

I'd really appreciate any thoughts.

reddit.com
u/Fluffy-Resolution390 — 1 month ago

I've been building custom software for a while, and one problem keeps coming up

Pricing.

Most agencies I've spoken with end up using one of these approaches:

  • A static price list
  • A calculator in Google Sheets
  • Custom values and workflows
  • Manual quotes from a salesperson
  • Sending the lead to another quoting tool

That seems to work for simple jobs, but it gets complicated quickly.

Things like:

  • travel distance
  • emergency fees
  • different service areas
  • commercial vs. residential
  • customer-specific discounts
  • minimum margin requirements
  • technician approval for larger jobs

are difficult to manage inside a traditional CRM.

I've been building a pricing engine that sits between customer intake and CRM like GHL. The idea is that forms, AI agents, APIs, or webhooks send the request to the pricing engine, it applies the company's pricing rules, generates a proposal, and then syncs everything back into CRM.

I'm not launching or selling anything yet.

I'm trying to understand how agencies are solving this today and whether I'm solving the right problem.

A few questions:

  • How are you currently calculating quotes?
  • What causes the most mistakes?
  • If you could automate one part of your pricing process, what would it be?

If anyone is interested, I'm also looking for 5–10 agencies willing to test what we've built and give honest feedback before we officially launch.

I'd really appreciate any thoughts.

reddit.com
u/Fluffy-Resolution390 — 1 month ago

I've been building software around HighLevel for a while, and one problem keeps coming

Pricing.

Most agencies I've spoken with end up using one of these approaches:

  • A static price list
  • A calculator in Google Sheets
  • Custom values and workflows
  • Manual quotes from a salesperson
  • Sending the lead to another quoting tool

That seems to work for simple jobs, but it gets complicated quickly.

Things like:

  • travel distance
  • emergency fees
  • different service areas
  • commercial vs. residential
  • customer-specific discounts
  • minimum margin requirements
  • technician approval for larger jobs

are difficult to manage inside a traditional CRM.

I've been building a pricing engine that sits between customer intake and HighLevel. The idea is that forms, AI agents, APIs, or webhooks send the request to the pricing engine, it applies the company's pricing rules, generates a proposal, and then syncs everything back into HighLevel.

I'm not launching or selling anything yet.

I'm trying to understand how agencies are solving this today and whether I'm solving the right problem.

A few questions:

  • How are you currently calculating quotes?
  • What causes the most mistakes?
  • If you could automate one part of your pricing process, what would it be?

If anyone is interested, I'm also looking for 5–10 agencies willing to test what we've built and give honest feedback before we officially launch.

I'd really appreciate any thoughts.

reddit.com
u/Fluffy-Resolution390 — 1 month ago

How to build a Voice AI that does math and calculates accurate quotes

I’ve been geeking out on this lately: I’ve been working with a client in the home services space to fix their automation process, and honestly, the tech side of it was a mess.

They were losing a massive chunk of their leads because the quoting process was stuck in manual spreadsheets. By the time they got a price back to the lead, the lead had already gone cold.

I ended up building a custom layer to automate the pricing logic so they can get a quote out the second a lead hits the inbox. The client started to see much more closing rate (according to them) and seems much happier.

I’m curious, how are you guys handling this on the technical side? Are you still relying on manual entry, or has anyone built a clean way to automate the margin calculations and quoting without it being a disaster to maintain?

reddit.com
u/Fluffy-Resolution390 — 2 months ago

How to build a Voice AI that does math and calculates accurate quotes

I’ve been geeking out on this lately: I’ve been working with a client in the home services space to fix their automation process, and honestly, the tech side of it was a mess.

They were losing a massive chunk of their leads because the quoting process was stuck in manual spreadsheets. By the time they got a price back to the lead, the lead had already gone cold.

I ended up building a custom layer to automate the pricing logic so they can get a quote out the second a lead hits the inbox. The client started to see much more closing rate (according to them) and seems much happier.

I’m curious, how are you guys handling this on the technical side? Are you still relying on manual entry, or has anyone built a clean way to automate the margin calculations and quoting without it being a disaster to maintain?

reddit.com
u/Fluffy-Resolution390 — 2 months ago

Hey home service agencies

I’ve built a workflow that splits pricing into two distinct tracks:

  1. For basic flat-rate services (like a standard AC tune-up or a diagnostic visit), the bot conversationally asks 2-3 qualifying questions to give an instant, dynamic quote.
  2. For complex jobs (like a full system changeout), the bot asks the customer all the dynamic qualifying questions first to gather the core details. Then, it texts them a ballpark estimate link that stays flagged as "Pending Technician Approval."

When the technician reviews the backend quote and the customer's answers, they can decide if an on-site visit is actually required, or if they have enough info to give an estimate right away. They can open that exact same link from anywhere, tweak the scope based on reality, and click "Approve" to push the final invoice natively.

How do you guys evaluate this workflow? Does this solve the main bottleneck your clients have when it comes to letting AI talk about money?

reddit.com
u/Fluffy-Resolution390 — 3 months ago

Fixing the AI quoting problem: I built an external "math brain" webhook to stop bots from hallucinating prices in SMS/Webchat. Would love feedback.

Hey everyone, sharing my progress on a build because I know a lot of agency owners are hitting this exact same wall.

I’ve been building AI quoting bots for home service sub-accounts (HVAC, moving, etc.). GHL's native AI and standard LLMs are great for booking the appointment, but the second the bot needs to calculate complex pricing, it hallucinates. It drops base fees or makes up crazy numbers over SMS.

Routing GHL webhooks to Google Sheets to do the math was just too clunky and broke constantly. So, I built an external visual logic engine to handle the math instead.

Here is how the GHL setup works:

  1. The AI handles the SMS/chat and collects the variables (sq ft, location, service type).
  2. A GHL Workflow fires a Custom Webhook out to the engine.
  3. The engine runs the strict, deterministic math (conditional fees, distance routing, bundles).
  4. It instantly returns a clean JSON payload back to GHL to update a Custom Field and reply to the lead with an exact, hallucination-free quote.

I recorded a quick 3-minute Loom showing how the backend math builder and API handoff works:

https://www.loom.com/share/edc0ecd308124007b2f84bf777f9283d

I'm still building this out and would love your brutal feedback. Does this architecture fit how you guys are structuring your GHL webhooks and AI workflows? Where do you see it breaking?

u/Fluffy-Resolution390 — 3 months ago