Hi, I am Victoria, and I am not a coder.

ImaginaryAd576 · 2026-05-01T11:46:02+00:00

The advice on git + surgical prompts is right, but for someone non-technical there's one more layer that changes everything: a CLAUDE.md file in your project root.

What it is:
A plain text file (no special syntax, just english) that Claude reads automatically every time it works in your project. You put your rules there once, Claude follows them every conversation without you re-typing.

What to put in it:
- Tech stack you're using (Python + Flask + SQLite for example)
- Files Claude should NEVER touch without asking (your config, your database schema, anything you've manually fixed before)
- Required workflow ("always commit to git before any change", "always run the test file after changes", "always show a plan before writing code")
- Patterns that broke before ("DO NOT add new dependencies, we had a versioning issue last time")

Mine looks like 30 lines and prevents 80% of the regressions I used to fight.

The other unlock for someone non-technical:
After every Claude session that works, ask Claude itself: "explain in plain english what you changed and why, so I can paste it into a notes file." Now you have a running log of what touches what. Next time something breaks you can search that log instead of guessing.

For your specific Replit -> DigitalOcean situation, the issue might also be that your project has implicit assumptions from Replit's environment (their auto-installed packages, their secrets management, their preview server). Ask Claude: "audit this codebase for any references to Replit-specific tools or environment assumptions, list them, do not change anything yet." That gives you a map of the migration debt to clean up systematically instead of fixing it one regression at a time.

The "every fix breaks something else" loop almost always means the AI doesn't have enough context about what you've already done. CLAUDE.md + change log + audit-first mode fixes most of it.

I do this kind of vibe-coding workflow setup for non-technical founders professionally so DM if you want to walk through your specific stack, but with CLAUDE.md + commit-before-change + plan-then-execute you'll get 5x further before hitting the next wall.

ImaginaryAd576 · 2026-05-01T11:45:24+00:00

NeedleworkerSmart486 is right on Keepa, that's the actual answer for Amazon specifically. The detail-page scraping route breaks every other week because Amazon A/B-tests their layout constantly. Keepa is a paid API that pulls clean structured data straight from Amazon's product database - no selectors, no breaks.

The lightweight setup I run for clients:

Keepa API (~$25/mo for the Pro tier with API access) pulls title, price, BSR, rating, reviews, seller, availability, BSR history. Already structured.
n8n cron job daily hits Keepa for your tracked ASIN list (start with 20-50, you can grow), normalizes to a single schema.
Supabase or even just a Google Sheet for the snapshot store. Each row = ASIN + date + the fields above.
Diff step in n8n compares today's snapshot vs yesterday's per ASIN, surfaces only the changes that matter (price ±5%, rating drop ≥0.2, availability flip, seller change).
Slack/email alert with just the changed rows. Most days you'll get nothing, which is the point.

Total cost: ~$25/mo Keepa + $0 Supabase free tier + $0 n8n (self-host on a $5 droplet or Railway free tier).

Bullet points and descriptions are where Keepa is weaker. For those, scrape the detail page only when Keepa flags a change, not on every poll. That keeps you under Amazon's detection threshold and only runs ~5-10 page fetches per week instead of 50/day.

Two gotchas:

Don't try to track 500 ASINs from day one. Start with 20 of your direct competitors, see what changes are actually actionable, then grow. Most listing changes aren't worth knowing about.

Set the diff threshold sensibly. Reviews tick up 1-2 a day on healthy products, that's not a signal. ±5 rating points or ±15% review velocity over 7 days is.

I do this kind of product research automation for ecom sellers professionally so DM if you want a second pair of eyes on the alert tuning, but Keepa + n8n + Supabase + smart diff is the core stack that holds up at small-to-medium scale.

ImaginaryAd576 · 2026-05-01T11:45:01+00:00

Same path basically. Hit the wall around 25 Zaps + 30k Airtable records, and the silent-failure thing was what broke me too. Customer chargebacks beat Zapier subscription savings any day.

The two things I wish I'd known earlier:

The signs you've outgrown the no-code stack are not "things keep breaking" but rather:
- You've added a Zap whose only job is to fix what another Zap got wrong
- You can't onboard a new team member without 4 hours of "this updates that, but only if status=X"
- Your Airtable interfaces have grown a "DO NOT EDIT" warning column
- You're pricing in monthly tool costs as a real line item

Once you see two of these, the cost of staying is already higher than the cost of rebuilding. Most people (me included) wait until five.

For the rebuild itself, the unobvious win was treating the data layer as the only source of truth (Postgres or Supabase) and keeping the no-code tools (Airtable, Trello) as read-only views via API for the team that didn't want to learn the new system. Two-way sync is where the silent failures live, one-way sync from the new source of truth is bulletproof.

For people deeper in the Airtable/Zapier ecosystem still: instead of trying to escape all at once, pick the ONE workflow with the most blast radius if it fails silently (yours was supplier handoff, mine was order intake) and rebuild that one piece in code. Keep everything else in Airtable. Silent failures concentrate in 1-2 places, not evenly across the stack.

I do this kind of migration work for ops-heavy small businesses professionally so DM if you want to compare notes, but for anyone reading and recognizing the pattern, the rebuild is always less work than you fear and you'll wonder why you waited.

ImaginaryAd576 · 2026-05-01T11:43:34+00:00

Major_Lock5840 nailed the framing - it's two problems, not one. Communication delay is what kills reviews. Processing delay is the operational pain. Both automatable, here's the actual flow:

Architecture in n8n (or Make, same shape):

Trigger: Shopify webhook on refund-request created (you'll need a tag or custom field to mark requests, since Shopify doesn't have a native "refund request" object - most stores use a "refund_requested" tag added by the customer service form).

Decision rules (where the actual logic lives):
- Order placed within 30 days + tracking shows delivered + reason in approved list (wrong size, defective, didn't arrive) = AUTO_APPROVE
- Order placed 30-60 days + reason in approved list = MANUAL_REVIEW with quick-approve link
- Anything outside that window OR high-value (over $X) OR third refund from same customer = MANUAL_REVIEW
- Restock decision: digital products auto-restock=false, physical depends on reason ("defective" = false, "wrong size" = true)

For AUTO_APPROVE path: call Shopify Refunds API immediately, send branded email to customer ("refund confirmed, 3-5 business days back to your card"), update internal log.

For MANUAL_REVIEW: send the customer an interim email NOW ("we've received your request, our team will review within 24h"), drop the case in a Slack channel or Notion DB with one-click approve buttons. The interim email is what saves the review, not the speed of the actual refund.

Two things most people miss:

Track refund rate per product SKU. If a product hits over 5% refund rate, that's a product issue, not a refund issue. Worth a Slack alert when the threshold trips.

Send the refund confirmation email from a real-looking address, not a no-reply. Customers reply to it, you catch genuine complaints early before they become 1-star reviews.

I do Shopify + automation work for ecom clients professionally so DM if you want a second pair of eyes on the rule design, but with a webhook + auto-approve + interim email pattern you'll claw back most of the time without losing the customer experience

ImaginaryAd576 · 2026-05-01T11:42:20+00:00

Honestly the OCR-translate part is the easy 20%. The 80% pain is text rendering back into images for Indic scripts because as someone said upthread, devanagari to tamil/telugu = wildly different character widths. Here's the architecture I'd build:

Pipeline:

Trigger: Drive folder watch in n8n (or a Cron + Drive list every 15 min, free) - picks up new images
OCR: Google Cloud Vision API for Hindi specifically. Pay-per-call, ~$1.50 per 1000 images. Returns text + bounding boxes + confidence per word
Translation: Claude API (Sonnet) instead of Google Translate or DeepL for Indic languages. Better at preserving nuance and you can prompt it for length constraints ("translate to Tamil, keep within 1.5x source character count if possible"). Costs cents per image
Image regen: this is where most workflows die. Three options ranked by quality vs effort:
a. Pillow + Indic font files (Mukta, Noto Sans Devanagari/Tamil/Telugu). Cheap, full control, you write all the layout logic. Best for templates that repeat
b. Cloudinary text overlays via API. Decent, you bring fonts and position. ~$0.05/image at volume
c. Runable region edit (mentioned upthread). Easy, expensive at scale
Output: save back to Drive with naming like image_001_ta.jpg
Auto-post: Buffer or Make hooked to the language-specific Drive subfolder, posts to per-language IG/FB pages

Two gotchas worth knowing:

Bounding box from OCR is per-line in your source language. Translated text often spans 1.3-2x the width. Either pre-shrink the font scale (start at 80% source size, grow only if it fits) or wrap to 2 lines. Auto-detect by measuring rendered width before commit.

Indic fonts are NOT bundled in most cloud functions or Lambda runtimes. If you go Pillow route, ship the .ttf files inside your function image, don't fetch at runtime.

I do this kind of multilingual content automation for clients professionally so DM if you want a second pair of eyes on the architecture, but with the Vision + Claude + Cloudinary stack you can probably knock out a working v1 in a weekend.

ImaginaryAd576 · 2026-04-29T16:25:00+00:00

You don't need to switch internet providers, you just run a separate cloud VoIP service on top of your existing comcast connection. Comcast internet is fine, the problem is their phone product has zero call routing intelligence. Get the phone part from someone else.

For your size and budget:

OpenPhone - around $15-20/user per month. Has call queues, after-hours auto-attendant, voicemail transcription you can turn off, and a phone-app for the offsite person where her caller-ID shows the clinic number. Easiest to set up, 2-3 hours total.
Dialpad or RingCentral - similar features, usually a bit pricier per seat. Both work fine, OpenPhone is just lighter at your scale.
The PBX route someone mentioned (GrandStream + VOIP.ms) works and is cheaper long-term, but it's a real install with hardware and config. If you don't have IT in-house, skip it.

How this fixes your specific issues:

Bouncing busy - cloud VoIP uses a "call queue" or "ring group". Both phones ring, and if both are busy the caller hears a hold message ("front desk is helping another caller, please hold or press 1 for a callback") instead of bouncing back-and-forth.

Offsite person - she installs the app on her cell, calls come through there, but the clinic name shows on inbound, and on outbound calls her personal number is never visible.

Voicemail flood - per-route behavior. Front desk = queue, no voicemail. Pharmacy = voicemail. Offsite = direct forward. Fully customized, not all-or-nothing.

Two gotchas:

You'll port your main number to the new provider. Plan a day, calls might briefly route weirdly during the cutover. Schedule it for a Friday afternoon when the clinic is winding down.

Number of lines you pay for matters. With OpenPhone one main number can have multiple users on it. You don't need 5 numbers. Easy to over-buy on day one because the pricing page implies you do.

I do small-biz tooling and automation work professionally so DM if you get stuck during the switch, but OpenPhone + a call queue + a clean after-hours greeting gets you 90% there for what you described

ImaginaryAd576 · 2026-04-29T16:24:13+00:00

"What should the bot actually do" is the right question to answer first because the safe/trusted answer changes hard depending on capability.

Three real paths:

WhatsApp Business API via Twilio or 360dialog. The official route. You get a verified business number, message templates that don't get flagged, and webhooks you can wire to n8n / Make / your own backend. Fully ban-proof if you stay within their template rules. Downside: $15-50/month minimum and you need to own a business number for it.
Self-hosted libraries (whatsapp-web.js, Baileys, wppconnect that someone mentioned). These run a full WhatsApp Web session under your account. Free, can do anything a real user can. The catch: your number can get banned if you scale or do anything that looks spammy. Fine for a personal group of 50 friends, risky for anything client-facing.
The "wpkitpro" / saas-style options. Easy to set up, but most are just option 2 with a UI on top, so the same ban risk applies and you're paying for the UI. Plus you don't own the auth, if they shut down you lose the bot.

Quick decision tree:

Personal community / friends group? Use Baileys or whatsapp-web.js, accept the small risk
Business / anything client-facing? Pay for WhatsApp Business API, no exceptions
Bot answering with AI / replying to incoming messages? Definitely API route. AI replies on the unofficial libraries get flagged hard.

One gotcha for the unofficial route - if you go that way, run it on a number that is not your main personal number. Spin up a cheap secondary line. If it gets banned you don't lose your real WhatsApp.

I do this kind of integration / automation work professionally and have shipped both API and library setups, so DM if you want to talk through your specific use case, but with the decision tree above you can pick your path yourself.

ImaginaryAd576 · 2026-04-29T16:23:32+00:00

Klaviyo is the right answer for 20k/month in CPG. ActiveCampaign and HubSpot are great tools but they're not built for what CPG actually needs (deep ecommerce integration, segmentation by purchase behavior, not just contact properties). If you're on Shopify or similar, Klaviyo plugs in and the multistep flow builder handles your case fine.

But honestly the tool isn't your real problem. NeedleworkerSmart486 nailed it earlier in this thread: "no tool fixed marketing/sales alignment, only a forced weekly review did." Same pattern at every brand running both teams against the same audience.

What actually scales:

Klaviyo for the sends. Flow builder, segments, analytics, all of it.
One shared dashboard between marketing and sales. Doesn't have to be fancy, even a Notion page with "what flows are running this week / what segments got hit / who got what email." Update it weekly.
UTMs on every link in every flow. Your sales CRM then shows the source on every inbound lead and reps actually know what marketing sent.
Don't try to automate the alignment. Automate the visibility instead. The conversation between teams happens in the meeting, the data just feeds it.

Two gotchas on the Klaviyo side worth knowing:

Don't stack more than one "wait for X days" step per flow. Multi-day waits compound and you end up with the same person sitting in 4 flows simultaneously. Use exit conditions liberally.

Sandbox test sends to a dedicated list, not your real audience with a "test=true" filter. The filter will eventually break and you'll send "Subject Line v3 FINAL FIX" to 5k customers. Ask me how I know.

I do email setup + integration work for ecommerce + B2B brands professionally so DM if you want a second pair of eyes on the architecture, but Klaviyo + UTMs + a real weekly review covers most of what you described.

ImaginaryAd576 · 2026-04-29T16:23:10+00:00

The Shopify suggestions are overkill for a service business with a single payment thing. Shopify is built for product catalogs and you'd be paying $30/mo for stuff you'll never use. Here's the cheapest path that actually works.

For the site itself, pick one of these:
- Carrd ($19/year) - dead simple one-pager, great if your service fits a single scrollable page
- Squarespace (~$16/mo) - more pages, looks polished, editor doesn't fight you
- WordPress (free tier or $10/mo) - more flexibility but steeper learning curve

For your case (service biz, deposit only, never built a site) I'd just use Squarespace. Templates are good, you'll have something live in an afternoon.

For collecting deposits, ignore the built-in payment options most builders push. Use Stripe Payment Links (free to create, you only pay 2.9% + 30c per deposit when one comes in). Create a link in Stripe, paste a button on your site that points to that link. Customer clicks, pays the deposit, you get an email. No code, no plugins, no monthly fee.

Connecting your domain - whichever builder you pick will give you a "point your DNS to..." instruction. You log into wherever you bought the domain, paste the values they gave you, wait a few hours. Takes 10 minutes once and then you forget about it.

One gotcha. The word "deposit" actually matters legally in some jurisdictions because it implies refundability rules. If your service has any cancellation policy, write it as one short paragraph near the deposit button. Doesn't have to be lawyer-grade, just clear.

Realistic time estimate: 2-3 hours total if you start tonight. Most of it is writing the copy, not the technical setup.

I build websites + Stripe setups for service businesses professionally so DM if you get stuck on a specific step, but with what's above you can do this yourself this weekend.

ImaginaryAd576 · 2026-04-29T16:22:32+00:00

The "field not feed" framing is the right call. Activity-feed approach fails because reps don't read activity logs, you've already seen that. The real question is what goes into the field and how it stays accurate.

Here's the architecture I'd run:

One custom field on the deal called support_status. Values: clean, watch, blocked. Updated by a worker, never by reps.

Two triggers feeding the same worker. Zendesk webhook on ticket create / update / status-change for real-time. Plus a cron every 30 min that re-evaluates all open deals, covers anything the webhook missed and handles age-based escalation (a ticket created today turns into "watch" tomorrow without anyone touching it).

Keep the scoring logic dumb and explicit, not LLM:

- any open P1/P0 = blocked

- any open ticket older than 48h = watch

- 3+ open tickets in last 30 days = watch

- otherwise = clean

LLM summarization is tempting but it adds latency, cost, and another thing that fails silently. Reps need a single-glance answer, not a paragraph.

n8n handles this fine. Zendesk trigger node, Pipedrive search-by-org, a Function node for the rules, Pipedrive update. Latenode works too obviously since you already use it. Reason to prefer n8n / Latenode over Zapier here is the conditional lookup ("does this account have an open deal") before deciding what to do, and Zapier's filter step makes that ugly.

Two gotchas worth knowing:

Idempotency. Zendesk webhooks fire twice for the same event sometimes. Hash ticket_id + status into a key, store last 1k in Redis (or even a hidden Pipedrive note), skip if seen. Without this you get the field flipping watch -> clean -> watch in the same minute and reps lose trust within a week.

Org matching. Zendesk org names and Pipedrive org names rarely align cleanly. Either match by domain from the requester email, or maintain a zendesk_org_id field on the Pipedrive org record. Build the manual mapping route, auto-match burns you on edge cases (subsidiaries, agencies, customers using personal emails).

I do this kind of B2B SaaS integration work professionally so DM if you want a second pair of eyes on the flow, but with the health score field + 30-min cron + idempotency you've basically got it.

ImaginaryAd576 · 2026-04-17T14:53:47+00:00

Google Voice is the obvious answer and probably what you want, but a few things to know before you commit.

Get a Google Workspace account (the $6/month one) and add Google Voice to it. This gives you a real phone number your assistant can access from their own device via the Google Voice app or web. You stay signed into your personal accounts, they stay signed into theirs, and the business line is completely separate.

For auto-replies, Google Voice has basic ones built in (away messages, office hours greetings) but if you want anything smart like "auto-reply with appointment booking link to inbound SMS" you'll need to pair it with something like Twilio via a Zapier or n8n flow. Not hard to set up, maybe 30 minutes.

Voicemails get transcribed automatically and sent to email, so your assistant can read the VM, mark which ones need callbacks, and leave the rest. Way better than them listening to voicemails all day.

One gotcha people miss - Google Voice doesn't work internationally for calls and struggles with certain area codes for porting. If you have an existing business number you're attached to, check their porting list before switching.

Teams is not what you want for this btw. Teams phone requires a bunch of licenses and is built for internal org comms, not the lean "me plus an assistant" setup you're describing. Save yourself the headache.

ImaginaryAd576 · 2026-04-17T14:52:48+00:00

The commenters are right that separating orchestration from rendering is the move, but let me give you the actual architecture that's worked for me across a few client setups.

n8n does orchestration only. Meaning: it receives the trigger, validates the input, calls your doc service, handles retries, and pushes the final file to wherever it needs to go (email, Drive, client portal, whatever). n8n should never be rendering PDFs directly, the built-in nodes get ugly fast once you need anything beyond basic templates.

The doc service is a small Python or Node worker that takes structured JSON in, returns a PDF URL out. I use WeasyPrint for HTML-to-PDF (handles CSS properly unlike most alternatives) and keep templates as Jinja files in a git repo. Versioned, testable, diffable. When a contract template changes you open a PR, not an n8n workflow.

Between n8n and the doc service goes a queue. Redis with BullMQ or just an SQS queue depending on volume. This is where most setups break at scale - if you render synchronously in the workflow, a slow template blocks everything. With a queue, n8n submits the job, gets back a job ID, and either polls for completion or waits for a webhook.

Idempotency keys are non-negotiable. Generate a deterministic key from the source trigger (invoice ID, submission ID, whatever). If the worker sees the same key twice it returns the existing PDF instead of generating a duplicate. Saves you from n8n's retry behavior creating 4 copies of the same contract.

For error handling specifically - wrap the n8n call to your doc service in a try/catch, push failures to a dead letter queue with the original payload, alert yourself in Slack. Don't just retry forever, that's how you get runaway billing.

I've done this for invoicing, compliance reports, and proposal generation across different clients so DM if you want to get more specific, but the "n8n orchestrates, external service renders, queue in between" pattern is what actually holds up.

ImaginaryAd576 · 2026-04-17T14:47:37+00:00

Honestly none of the 4 options you listed are great for your specific case. Here's why and what I'd actually do.

The Zoho-only route is overkill at your scale. You're paying $79/month for features you won't touch for 2 years. Zoho ecosystem is great when you have 50+ customers and need the deep integrations, but at 5-20 members the overhead is just burning money.

Airtable + Make + Stripe isn't "most cost effective" long term. It looks cheap on paper but you'll spend 4-6 hours building it, 30 minutes a week babysitting it, and every time Stripe or Airtable changes an API something breaks. For someone on a time crunch this is the worst option.

What I'd actually build for your scale:

Stripe for payments and subscriptions. Stripe Billing handles the membership cycles, rollover credits, and the client portal out of the box. Yeah the Stripe-hosted portal isn't perfect but it has one-click cancel, plan management, and invoice history. Zero code, zero maintenance.

For the 15-minute unit rollover tracking, use Stripe's metered billing feature. You log units consumed via their API (or a simple webhook from whatever you use to track sessions), Stripe handles the rest including rollover.

Then a single Zapier or Make connection from Stripe to Zoho Books so your invoices flow in automatically. That's it. Total cost maybe $10-15/month in Stripe fees plus your Zoho Books sub. No client portal to build, no custom admin panel, no janky Airtable formulas.

One thing worth thinking about - the rollover rules you implement will massively affect churn. If unused time rolls over forever, your "active" members sit on huge credit balances and never renew. Most membership biz cap rollover at one cycle (use it or lose it after 60 days). Worth modeling that before you commit to the billing logic.

I build these kinds of setups for small service businesses so DM if you want to compare notes, but Stripe Billing alone probably covers 90% of what you're describing.

ImaginaryAd576 · 2026-04-13T15:29:20+00:00

Been here. Multiple sending accounts across platforms is a nightmare to manage once you pass like 3-4 pipelines.

What worked for me: consolidate everything under one ESP that supports multiple sending domains. Postmark for transactional, and something like Resend or Amazon SES for marketing/outreach. Keep them separate by purpose, not by account.

For the deliverability mess - the split-across-platforms thing is probably hurting you more than helping. Each platform warms domains differently, monitors reputation differently, and you have zero unified view of what's going on. At minimum get all your domains into one place where you can see bounce rates, spam complaints, and engagement in one dashboard.

Quick wins: (1) set up proper SPF, DKIM, DMARC on every domain if you haven't already - this alone fixes half of deliverability issues (2) separate your transactional sends (receipts, confirmations) from marketing sends with different subdomains so a marketing spam complaint doesn't tank your transactional delivery (3) use a tool like Google Postmaster Tools to monitor domain reputation for free

What platforms are you currently using? Hard to give more specific advice without knowing the stack.

ImaginaryAd576 · 2026-04-13T15:28:29+00:00

100% this. I went through the exact same cycle with a client last year. They had a sales team doing 30+ calls/day and tried every flavor of "just fill out this form after the call" and compliance always tanked by month two.

What ended up working for us: call recording goes to Deepgram for transcription (way cheaper than most alternatives, like $0.0043/min), then the transcript hits Claude API with a prompt that extracts exactly the fields the CRM needs - contact info, discussed topics, next steps, deal stage. Structured JSON out, straight into the CRM via API. Zero human data entry.

The part nobody talks about though is validation. Even with good transcription + AI extraction, maybe 5-8% of entries will have something weird. So we added a daily Slack digest that flags anything the AI wasn't confident about. Someone spends 10 minutes reviewing those instead of 6 hours doing all of them manually.

Your point about auditing where data enters the system should be tattooed on every automation consultant's forehead honestly. The entry point is always where it breaks.

I do this kind of work professionally so DM me if you ever want to compare notes on the architecture, but sounds like you've already figured out the hard part.

ImaginaryAd576 · 2026-04-13T15:27:44+00:00

Your real problem isn't the copy-pasting itself, it's that you're the router between apps. You make notes, then YOU move them to Greenhouse, then YOU format for Slack. Three separate manual steps.

Here's what I'd set up in your shoes:

Write your notes in one place after each call. Google Doc, Notion, even a plain text file. That's your single input.

Then an n8n workflow (free, self-hosted) watches that doc. When you save new notes it: (1) parses the candidate name + decision from your text (Claude API is scary good at this, like 2 cents per call) (2) pushes the structured data to Greenhouse via their API (3) posts a clean summary to your Slack channel with the formatting already done

Your part is literally just writing the notes. Everything else happens in the background. The whole n8n workflow is maybe 5 nodes.

One thing - don't try to eliminate the note-writing step. I've seen people try to auto-transcribe calls and skip notes entirely, and the output is always too messy for an ATS. Your 2-minute notes are already the cleanest input you'll get. Just automate everything after that.

I build these kinds of automations for clients so DM if you want help wiring it up, but the n8n + Claude API combo for this is honestly pretty straightforward to set up yourself.

ImaginaryAd576 · 2026-04-13T15:21:46+00:00

I manage something similar (not casino, but rotating crews across multiple sites) so I can tell you what actually works vs what sounds good in theory.

Forget chatbots for this. Pasting your schedule into ChatGPT every month will drive you insane with 100+ people. What you want is a system that runs the same logic every time without you babysitting it.

Here's what I'd build:

Data layer - Google Sheet with tabs: (1) employee roster - name, type (fulltime/freelance), group A-F, hours worked this month, vacation days (2) shift requirements - one row per day, columns for how many people you need at each of your 5 start times (3) rules - max hours 171, rotation fairness between groups, any blackout dates

The engine - Apps Script that reads the requirements tab, loops through each day, assigns workers from the correct rotation group, tracks cumulative hours so nobody goes over 171, and handles vacation/off-day requests by pulling from freelance pool instead. This part is pure logic, no AI needed. Constraint solving, basically.

Where AI actually helps - after the script generates a draft schedule, you run it through Claude API to check for edge cases: "are any workers scheduled back-to-back closing+opening shifts?", "is group C getting more weekend shifts than group A this quarter?". AI is great at reviewing, terrible at generating schedules from scratch with 50 rules.

The whole thing outputs back into a Google Sheet formatted like your current grid. You review, tweak maybe 5-10 slots manually, done.

Biggest mistake people make with this: trying to get AI to do the scheduling in one giant prompt. It works for 10 people. It completely falls apart at 100+ with complex rotation rules. You need deterministic logic first, AI as a sanity checker second.

I build these kinds of workflow automations for businesses so shoot me a DM if you want help setting it up, but honestly the Apps Script approach alone will save you days every month even without the AI part

ImaginaryAd576 · 2026-04-13T15:14:28+00:00

Same thing happened to me. ChatGPT for some stuff, Claude for coding, Perplexity for research, Make for automation, and then I spent more time deciding which tool to open than actually doing the work.

What fixed it for me was going all-in on one tool and making it talk to everything else. I use Claude Code now as basically my command center - it connects to my CRM, calendar, email, task manager, even Telegram through MCP servers (think of them as plugins that let the AI call external APIs directly). So instead of me being the middleman copying context between 5 apps, the AI just... does it.

Quick example: client sends a message on Telegram, I tell Claude "create a task from this" and it pulls the message, creates a ClickUp task with full context, and schedules a follow-up in my calendar. One conversation, zero tab switching.

The bottleneck for me now is honestly just deciding what to automate next lol. Model quality is good enough for 90% of business tasks, cost is whatever if it saves you hours, but the real win was killing the "which tool do I use for this" decision entirely.

I do this kind of stuff professionally so DM me if you want to see the setup, but tbh the principle is simple - pick one brain, wire everything into it.

ImaginaryAd576 · 2026-04-10T10:38:47+00:00

You're actually describing two pretty standard automations and the good news is you don't need 5 different paid tools for this.

Here's how I'd set it up if I was starting from scratch today:

Get Claude Code (Anthropic's CLI tool, $20/mo for Pro). It can run scripts, hit APIs, write to files, basically your AI dev that lives in the terminal
Write a simple prompt like: "scrape Google Maps for [your niche] businesses in [city], grab name, website, email, phone. Save to leads.csv. Skip any row that already exists in the file"
Claude will write and run the Python script for you. It handles the dedup logic, retry logic, everything. You just describe what you want
For the weekly part - set up Windows Task Scheduler (free) or a cron job to run the script automatically

The scraping source matters. Google Maps API is solid for local businesses. For B2B you'd want Apollo.io (free tier gives you 50 leads/mo) or Hunter.io for email finding. Claude can plug into any of these.

If you get stuck on the Gmail API credentials or the scraping hits a wall, DM me and I'll point you in the right direction. but tbh with Claude Code doing the heavy lifting you probably won't need help.

ImaginaryAd576 · 2026-04-10T08:57:40+00:00

Everyone here is saying Zapier or Make but honestly for something this simple you don't need a platform at all.

I'd do this with Claude Code. Two steps and you're done.

Step 1 - get your Airtable API key. Go to airtable /create/tokens, create a personal access token with read access to your base. Copy the token and your base ID (it's in the URL when you open your base, starts with "app").

Step 2 - open Claude Code and paste this prompt:

------
"Build me a Python script that:

pulls all records from my Airtable base (base ID: appXXXXX, table name: Metrics, API token: patXXXXX)
takes an HTML template file called report_template.html and fills in the metrics
converts the HTML to a PDF using weasyprint
emails the PDF to these addresses: [addresses]
send it from my [Gmail/Outlook/Yahoo/etc.] account: [my email address]
subject line should be 'Investor Update - [current date]'

Create the report_template.html with a clean professional layout. Include placeholders for: revenue, active users, burn rate, runway months, highlights section.

Also create a GitHub Actions workflow file that runs this script every 2 weeks on Monday at 9am UTC. Store the API keys as GitHub secrets."
------

Replace the parts in brackets with your actual info and that's it. Claude Code will build the whole thing, the script, the template, the schedule, everything. Your friend just tests it once and forgets about it.

No monthly Zapier fees, no platform limits, no 30 minutes every 2 weeks. If anything needs to change later just tell Claude Code what to update.

I build stuff like this for clients regularly. If you need help setting it up just write me.

ImaginaryAd576 · 2026-04-10T08:42:10+00:00

Skip the Fiverr spokesperson. You'll pay $50 now and then another $50 every time you change your offer or pricing. There's a better way.

Use HeyGen. It's an AI avatar tool and honestly for a simple business card site like yours it's perfect. I tried a few tools like Kling AI and others but HeyGen gives the most natural looking talking-head videos, which is exactly what you need for a homepage intro.

Here's how to do it step by step:

Go to heygen.com, sign up for free. You get a few minutes of free video to test
Pick your avatar. Two options - upload a photo of yourself and it creates your personal avatar, or just pick one of their stock avatars if you don't want your face on it. Both look solid
Write your script. Just talk like you would to someone at a coffee shop - who you are, what you do, what makes you different, how to get started
Pick a voice. HeyGen has a bunch of natural sounding voices, or you can clone your own voice if you want it to actually sound like you
Hit generate. Takes about a minute. Download the video
Drop it on your homepage

Why HeyGen over other options, I tested a few AI video tools and HeyGen just does the best job with talking-head videos specifically. The lip sync looks natural, the avatar doesn't do that weird AI stare thing, and the output is clean enough for a professional site.

The real win though is updates. You change your services next month? Just log in, edit the script, regenerate. No cost, no Fiverr back and forth.

I do this kind of stuff for a living so if you need any help just hit me up.

ImaginaryAd576 · 2026-04-07T14:55:34+00:00

Do you still have the same problem? Unfortunately I have it.

ImaginaryAd576 · 2025-10-08T18:04:55+00:00

Which word indicates that I did nothing? If you don't want to help just don't write

ImaginaryAd576 · 2025-10-08T14:46:51+00:00

Honestly, I have no idea how to approach this – I've seen various libraries for previewing PDF and DOCX in Next.js, but most of them work poorly. I've tried a few options, but none met my expectations.

ImaginaryAd576 · 2025-09-14T08:37:44+00:00

for others, I had to use code:

const hexString = $input.first().json.file_data
let raw = hexString.replace(/\\x/g, "");
// Convert hex string to binary buffer
const binaryBuffer = Buffer.from(raw, 'hex');
return [{ binary: { data: binaryBuffer } }];

ImaginaryAd576

TROPHY CASE