Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More

Owned by Hisham

Deterministic pricing engines for service businesses. No AI guessing, no hardcoded rules. Built for agencies on n8n, GHL, and vibe-coded stacks.

4 contributions to Vibe Coding Labs
$250 Community Showcase Tomorrow!
Quick reminder: our November $250 Startup Pitch Competition is tomorrow, Monday, November 16, at 4 pm ET! We’ve got some awesome founders from the community presenting what they’re building, and I know they’d love your support and feedback :) I’ll be hosting the whole thing live on Twitch, with a bunch of cool prizes for viewers too! Come hang out, check out the projects, and support the founders. See you tomorrow! https://www.twitch.tv/byjackprice
1 like • 6d
Hey Jake Is there any other open applications for startup ideas, or it’s too late?
0 likes • 5d
@Jack Price awesome!
Quick heads up if you vibe-coded a pricing calculator (your formulas might be public)
If you used Lovable, Bolt, or Cursor to build an estimate form, quote tool, or pricing calculator for a client, check where the actual math runs. Most of these tools dump the entire calculation right into the frontend JavaScript. That means anyone who inspects the page can literally read your client's exact pricing formulas, see their private margins, or tamper with the final numbers. I’m putting together a scanner specifically to check for exposed pricing logic and unvalidated math in vibe-coded apps. If you want to check your app before a client or customer notices: Drop "TEST" below (or DM me your link) and I’ll take a look and send you what I find.
0
0
If you vibe code client projects, this is the backend problem nobody talks about.
The front end is easy. Lovable, Claude, Cursor — done in hours. But the moment a client needs real pricing logic, business rules, or calculations — you're either hard-coding it into prompts or writing custom backend code. Both are a nightmare to maintain when something changes. I built a solution. Here's how it works: → You vibe code the front end (any tool) → It connects to n8n → n8n pulls the business logic from Quotix (the engine I built) → Quote calculated, result returned to the front end → Lead pushed to GoHighLevel automatically No black box. No hard-coded prices. Full control over the business logic from one place. https://www.loom.com/share/256a189b6ba74aa2bf53aeab14569bc0 I'm looking for people to test this. If you build for solar, HVAC, roofing, electrical — or any service business that needs on-site quoting — drop a comment or DM me. Free to test.
If you vibe code client projects, this is the backend problem nobody talks about.
1 like • Oct 7
@Mason Grant appreciate that. The pricing engine actually works well outside HVAC too. For e-commerce, think dynamic pricing rules, tiered shipping logic, or bundle calculators that update in real time without touching code. Happy to stay in touch. If you ever have a client with complex pricing that's hard to maintain, that's exactly what Quotix solves. Happy to show you how it works and hear your thoughts and feedback.
Looking for a builder that I can properly understand, (english)
I'm building Arete Collective, with Socratic Spark as our AI implementation arm. The broader goal is to build practical business infrastructure that combines AI, automation, knowledge systems, data, and workflows into systems that actually improve how companies operate. I'm interested in more than isolated automations. The direction is toward connected operating systems that help businesses respond faster, retain more knowledge, reduce repetitive work, make better decisions, and capture opportunities that would otherwise get lost. Right now, I'm building out the service side of the company and looking for a strong technical builder who could potentially become someone I work with repeatedly as we take on more clients. The immediate project is a lead and estimate reactivation system for remodeling companies. The business problem is simple: contractors often have old inquiries and estimates sitting in their CRM that never became jobs. We're building a system that can go back through those opportunities, re-engage them, identify people who are still interested, hand qualified opportunities back to the contractor, and track the revenue recovered. At a high level, the system needs to: - ingest an existing CRM export, spreadsheet, or database of dormant leads and estimates - clean, organize, and segment the data - run approved multi-touch reactivation sequences - manage email/SMS workflows - detect and classify responses - handle opt-outs correctly - identify genuinely interested prospects - route qualified opportunities back to the client - track handoffs, opportunities, jobs, and attributed revenue - provide simple reporting - be reusable and adaptable for future clients I'm especially interested in builders comfortable with: - n8n or similar workflow tools - APIs and webhooks - JavaScript / Python - Twilio and SMS infrastructure - email automation - CRM integrations - Google Sheets / CSV workflows - LLMs for classification and workflow logic - building reliable production systems rather than impressive-looking demos
0 likes • Sep 27
Hey Jadrien, This is exactly the kind of work I'm interested in — real systems that recover actual revenue, not demos. I'm the founder of Quotix, a pricing engine backend for service businesses. I just shipped a working HVAC field tool — 4-step technician flow, live pricing in under 2 seconds, syncs to GHL. Everything runs through n8n in production. Real clients, real leads, real executions. My stack lines up directly with what you're describing. n8n, APIs, webhooks, Twilio, GHL, Google Sheets, Python and JS. I've built LLM classification into automation flows and know how to route outcomes without things falling apart at 2am. For the reactivation system specifically — I'd keep the first build narrow. Ingest their CRM export, clean and segment by recency and job value, run a 3-touch sequence, classify responses with a lightweight LLM prompt, route interested leads back into GHL, track everything in Sheets. No over-engineering before we've seen their actual data. Deferred fee structure works for me on the right first project. I'd rather spend 20 minutes on a call looking at the first client's real CRM than write three more paragraphs here. Let me know if you want to connect.
1-4 of 4
Hisham Juneidi
1
2 points to level up
@hisham-juneidi-8604
Interested in connecting with people who has passionate about AI and technology

Active 1h ago
Joined Sep 27, 2026
Powered by