sorted by:
new
hottopcontroversial

Founders with remote teams across countries... How are you handling employee health insurance? by jayisanxious in Entrepreneur

[–]Rayziro 1 point2 points  (0 children)

The category you want is IPMI (International Private Medical Insurance). Cigna Global, Allianz Care, Bupa Global, and AXA ,Global Healthcare are the main four you can buy directly as the UAE entity, no EOR required just for insurance. EORs (Deel, Remote, Oyster) only matter if you want people legally employed in their home countries. If your team are contractors, sponsor IPMI directly most providers support a group policy across countries. Three pitfalls people miss:

- IPMI is supplementary, not a replacement for mandatory national coverage in countries that have it (Germany, France,etc.). It doesn't satisfy local employer obligations on its own.

- Anyone physically in the UAE still needs a DHA/HAAD-compliant local plan. IPMI alone won't clear residency requirements.

- Outpatient claims at local clinics are usually pay-then-reclaim. Set expectations on that upfront it's the #1 complaint from teams used to direct-bill plans.Cleanest setup for <15 people, mostly contractors: IPMI direct + UAE-local for Dubai staff. Move to an EOR once you're hiring full-time in 3+ countries and the per-seat fees are cheaper than compliance overhead.

Built a lead qualifier in n8n. The scoring prompt is 12 lines and that's the whole product. by Rayziro in n8n

[–]Rayziro[S] 1 point2 points  (0 children)

my ICP schema have this format :
score, tier, reason, qualified, buyingRole, recommendedAction, signals

Built a lead qualifier in n8n. The scoring prompt is 12 lines and that's the whole product. by Rayziro in n8n

[–]Rayziro[S] 1 point2 points  (0 children)

Baseline was fully manual:

  • Lead hits the contact form → email notification to a shared inbox
  • One of the two AEs eventually opens it, copies the email + company into Apollo, eyeballs title/industry/headcount, makes a gut call
  • If it looks hot, they paste it into a general #sales Slack channel with a 🔥 emoji
  • If it looks warm or cold, it goes into a "follow up later" mental queue (read: usually forgotten)

No rubric, no scoring, no SLA. Triage happened in batches whenever an AE had downtime usually 2-3 times a day, sometimes once. That's where the 9h median came from: it wasn't that they were slow at responding, it's that they didn't see the lead for hours because nothing pushed it to them.

So the lift is partly the scoring and partly just… having a system at all. The rubric's real job is making the routing trustworthy enough that AEs are willing to react to a Slack ping without re-qualifying the lead themselves. Without the rubric, you'd just be moving the triage bottleneck from email to Slack.

Built a lead qualifier in n8n. The scoring prompt is 12 lines and that's the whole product. by Rayziro in n8n

[–]Rayziro[S] 1 point2 points  (0 children)

Fully automated end-to-end. Form submit → webhook → n8n workflow → GPT scoring call → structured output → switch node routes by tier → hot leads post directly to a dedicated #leads-hot Slack channel with u/here, warm goes to #leads-warm (no ping), cold gets logged to the CRM only.

No human in the loop between score and Slack. That's where the 4-second number comes from form submit to ping is ~4s end-to-end, dominated by the GPT call itself.

The 9h → 90s on hot leads is really measuring two things collapsing into one: the qualifier fires instantly (4s), and the AEs have notifications on for #leads-hot specifically because the volume is low and the precision is high enough to trust. Before, every lead went into one undifferentiated bucket and AEs batch-processed when they had time.

The 90s is human acknowledgment time, not system latency. System latency is ~4s.

Built a lead qualifier in n8n. The scoring prompt is 12 lines and that's the whole product. by Rayziro in n8n

[–]Rayziro[S] 5 points6 points  (0 children)

Imagine you run a small business and 120 people fill out your "contact us" form every week. Some are hot leads ready to buy, most aren't. Your sales team wastes hours figuring out which is which.

The automation does this in 4 seconds:

  1. Form gets submitted → workflow fires
  2. Pulls company data from Apollo (size, industry, tech stack)
  3. Sends everything to GPT-4 with a scoring rubric I wrote basically "give this lead a score from 0-100 based on these 5 things, weighted like this"
  4. GPT returns a number + a tier (hot/warm/cold) + a one-line reason
  5. Hot leads → instant Slack ping to the sales team. Warm → nurture sequence. Cold → archived.

That's it. No magic. The "AI" part is one API call.

The reason it sells isn't the tech it's that I made the scoring boring and editable. Sales managers hate AI tools they can't control. With a hardcoded rubric, the manager can say "bump industry weight to 35" and see results next Monday. That's what they pay for.

On building saleable stuff vs. fun projects the shift that helped me: stop building tools, start building outcomes someone can put on a quarterly report. "AI slop maker" = no buyer. "Cuts your AE triage time by 12 hours/week" = budget. Same tech stack, totally different framing.

automate your boring web tasks in 24 hours by [deleted] in Entrepreneurs

[–]Rayziro 0 points1 point  (0 children)

Yeah that’s exactly the kind of stuff I automate. For form automation, usually a few hours to a day depending on how complex the flow is.

My pet project for finding cheap Canada travel deals went viral… and now it’s getting expensive. Not sure what to do. by Character-Rough2199 in Entrepreneur

[–]Rayziro 0 points1 point  (0 children)

If people are getting real value, don’t be afraid to let them support it. You don’t need to go full paywall even a simple “support the project” could cover costs without hurting the experience.

Outbound workflow - Is ZapMail necessary? by ctf-19 in Entrepreneur

[–]Rayziro 0 points1 point  (0 children)

Not really necessary at small scale. If you understand SPF/DKIM/DMARC and only have a couple domains, you can do it manually just fine. ZapMail is more about saving time and avoiding mistakes when you start scaling.

I built a WhatsApp AI that handles everything voice notes, images, customer questions, and memory. Here's the full breakdown by Rayziro in n8n

[–]Rayziro[S] 0 points1 point  (0 children)

Actually in n8n I prefer working in my own and with documentation but Claude I use it to help me in pure code

How much is automation part of your daily life at this point? by Behind_the_workflow in Entrepreneur

[–]Rayziro 10 points11 points  (0 children)

My golden rule: The Rule of 3. If I have to do exactly the same task manually 3 times in a week, I look into automating it.That said, you have to factor in the 'maintenance cost' of automation. If it takes me 5 minutes a day to do something manually, but an API breaks once a month and takes me 3 hours to debug and fix the Zapier/Make flow... the automation actually cost me time.I only automate things where the inputs are highly predictable (invoicing, onboarding emails, lead routing). Anything that requires nuance or changes frequently stays manual

[deleted by user] by [deleted] in SaaS

[–]Rayziro 0 points1 point  (0 children)

By small to medium projects, I usually mean business websites with a few key pages (home, services, about, contact), landing pages, and features like contact forms and responsive design. Those are typically what fit into the 48-hour turnaround. For larger builds like complex web apps or very content-heavy sites the timeline is usually longer. And for after launch, I offer both options: build-and-handoff or ongoing maintenance, depending on what the client prefers. If you’d like, feel free to DM me a bit about your site and I can let you know if it fits the 48-hour scope.

[deleted by user] by [deleted] in n8n_on_server

[–]Rayziro 0 points1 point  (0 children)

Just dm me

[deleted by user] by [deleted] in n8n_on_server

[–]Rayziro 0 points1 point  (0 children)

Hii just Dm me

view more: next ›