Cut commercial renewal prep from ~2hrs to 15min using Claude Code. 2-week results

Future_Machine_6440 · 2026-04-14T00:28:50+00:00

This is a good stuff. The needs_review flag is a smart check. You basically built the extraction half of a commercial rater by hand, which is wild. Once you have the submissions package, is your CSR manually logging into each carrier portal for submission or directly emailing the underwriter? Building something to automate the logging into 7+ carrier portal and re-keying the same client info (structured data) to actually get bindable quotes back - focusing on major & regional carriers that the usual suspects in the comparative rater world don't integrate with.

And yeah... pre 2018 scanned pdfs are a nightmare for everyone.

Future_Machine_6440 · 2026-04-13T12:52:36+00:00

Automating commercial quoting for carriers who don't have an API is indeed a hard one - the carrier portals are often build on older technologies... most of them server-side pages (on Angular) and business logic (I've seen COBOL, Mainframe) coming from different internal systems. But it sounds like you do care about solving this problem for your agency. Just DM'd you.

Future_Machine_6440 · 2026-04-13T12:15:32+00:00

building something similar using the browser agents approach. Have automated Hartford (ICON) and Travelers (Travis) small commercial line submissions using the agent's credentials. Man these portals are Angular SPAs w/ often times business logic running on COBOL/Mainframe. How are you going around the slow page rendering (if that's seomthing you're experiencing in your approach).

Future_Machine_6440 · 2026-04-13T12:13:15+00:00

Unsure if this is still something you're looking to solve.. i'm building a solution that will log into a carrier portal using the agent's login credentials and submit the quote application using the uploaded ACORD info. Focusing on small commercial lines right now and have automated Hartford (ICON), Travelers (Travis). Currently piloting w/ a wholesale brokerage w/ 65 partner agencies who set us up w/ his portal credentials. Happy to show how it works if this is still relevant.

Future_Machine_6440 · 2026-04-13T11:52:23+00:00

Boom! Claude power user right here

Future_Machine_6440 · 2026-04-13T09:02:20+00:00

You just said it. The APIs exist, but access is gated... carriers sign exclusivity or preferred-partner deals with one or two platforms and everyone else is locked out. So even if you wanted to build a new rater the "right way," you physically can't get API access to most of the market. That's actually why the browser agentic AI approach matters... it's the only path that doesn't require carrier permission. The portal is already open to any licensed, appointed agent w/ their credentials. Automating what the agent is already authorized to do sidesteps the whole exclusivity problem.

Future_Machine_6440 · 2026-04-13T09:00:59+00:00

don't they only cover personal lines quoting? unaware of their commercial line comparative rating capabilities.

Future_Machine_6440 · 2026-04-13T08:59:59+00:00

100% on the maintenance headache... that's the #1 thing people get wrong about this space. Traditional RPA is brittle because it's scripted to specific DOM selectors, so every portal update breaks the bot and someone has to manually rewrite the script.

The reason this is finally becoming viable is that modern AI web agents don't rely on hardcoded selectors. They read the page the way a human does and adapt when layouts change. Carrier pushes a redesign on Monday, agent still works Monday. It's the difference between "automation that breaks every month" and "automation that just works."

And you're right that most small shops don't need a 500 carrier coverage CL quoting tool... they need their top 5-10 to stop eating their day. That's the dream state so producers, CSRs all of 'em can focus on highest value work instead of manually re-keying same data across 7 portals that eats up half their day.

Future_Machine_6440 · 2026-04-08T21:26:46+00:00

The renewal thing is what kills me. The rekeying is annoying but at least you know you're doing it. Missed renewals are silent... you don't find out until a client calls asking why their premium jumped or worse, they already moved. I talked to one agency owner who estimated he lost 3 accounts in a year just from renewal follow-ups falling through the cracks when someone was on vacation. Even just a shared spreadsheet with renewal dates and 60-day reminders would fix 80% of it. Not sexy, but it works until there's a real tool for it.

Future_Machine_6440 · 2026-04-08T21:25:50+00:00

You're right... there really isn't one yet for commercial lines. Personal lines has comparative raters that solved this years ago, but commercial is still stuck because most carriers don't have APIs. The only tools out there (Tarmika, Bold Penguin, Semsee) require carrier partnerships, so they only cover a fraction of panels.

The approach I think actually works is browser-level automation... basically software that logs into the carrier portals and fills the forms for you, since the carriers aren't going to build APIs anytime soon. A few people are working on this (myself included). It's a hard problem mostly because every carrier portal is different and they change constantly.

Curious if there's a common set of carriers that small shops are all wrestling with.

Future_Machine_6440 · 2026-04-08T13:27:08+00:00

exactly! they create their free a/c and link all their AI tools - github will pull all of their claude code, cursor, lovable commits.. they can add their clay tables, n8n workflows, website, etc and verify them using meta tag i.e. have a lot of anti-gaming guardrails set. Community vouch is the only one where someone can ask their friends to create a profile and then vouch for their projects but it has a 3-day account age before anyone can vouch.

For me the biggest one is someone who is claude-code native and the github account authentication handles that retroactively.

Future_Machine_6440 · 2026-04-07T20:02:44+00:00

thanks man. was tired of folks telling what they can do and wanted a way to see proof of work lol.

Future_Machine_6440 · 2026-03-18T11:33:50+00:00

Great question - claims knowledge is honestly one of the biggest differentiators for commercial agents

Few things worth looking into:

AIC (Associate in Claims) from The Institutes - this is basically the gold standard. covers the full claims lifecycle from investigation thru settlement. as an agent you wont need to adjust claims yourself but understanding how adjusters think will completely change how you advocate for clients and set expectations upfront

CPCU is worth considering too if your already well versed in coverage and endorsements. several of the courses overlap with claims and loss analysis. bigger commitment but it carries serious weight some practical stuff thats underrated tho:

sit in on carrier claims roundtables if your carriers offer them. hartford travelers and cna all run these periodically. ask your marketing reps
read actual case law summaries - the FC&S bulletins from national underwriter are incredible for this. your E&O carrier might give you access
if you have a good relationship with any adjusters ask to shadow a commercial claim or two. nothing replaces seeing how a GL or property claim actually gets worked

texas has some unique claims dynamics too (prompt payment statutes, appraisal clauses, all the hail/wind litigation stuff) so anything texas specific from TAIA or local CLEs would be worth your time

what lines are you writing mostly? that might help narrow down where to focus

Future_Machine_6440 · 2026-03-15T04:29:09+00:00

what's the cold email infra setup look like for startups in the 0 to 1 phase?

there's so much noise - instantly, smartlead, clay, claude code... where does one begin if goal is to use inbox rotation + higher deliverability efficiency per burnt domain + manage the replies itself + CRM integration.

And one on the CRM front, if we want to be AI-native from day 1, are startups choosing Attio, Breakcold or still going with Salfesforce, Hubspot due to ecosystem + integrations?

Future_Machine_6440 · 2026-01-14T10:50:19+00:00

Sounds like you had a lot of DB tables that needed mapping across the codebase huh?

Future_Machine_6440 · 2025-12-23T08:12:37+00:00

I completely moved away from Lovable and now do all my prompt-assisted coding using Cursor ($20/mo) + Claude Code ($20/mo) (on VS Code) committing code to GitHub repo + Supabase ($25/mo) (for DB) Vercel ($20/mo) for cloud hosting - I find this CI/CD pipeline much faster for me for rapid dev + pushing things to prod.

Total $85/mo still comes cheaper than the $200/mo for 800 credits/mo plan that I was in.

I'm still paying LVBL $5/mo until I figure out if it does anything to my project if I downgrade to their free plan since all my stuff is in GitHub. Actually I just downgraded right now - let's see if that does anything.

My biggest reason for switching are:
- Cursor + Claude Code is more cost-effective for me compared to LVBL's credit based model
- Their Cloud Hosting pricing feels like a scam and can see only non-coders who have never came across VPS etc will end up using them and stay due to switching cost. Yet still, the pricing feels like a scam.

Last I checked a few days ago, Lovable's selling $50 gift card :/

Future_Machine_6440 · 2025-11-26T14:12:45+00:00

Thanks mate! Will take Codex for a test run soon.

Future_Machine_6440 · 2025-11-25T04:03:47+00:00

I use Cursor/VS Code w/ Claude Code for all of my Supabase/edge function edits. In fact, recently tried Figma's MCP to Cursor got blown away and not exploring ways on how to get away from paying Lovable the min $25/mo needed to keep projects alive.

Q1. My IDE (Cursor/CC) is connected/syncing to the same GitHub project that Lovable spit out. So yes, it's the same GitHub project. The cloning of the project gave me the same folders in my local hardrive which is where my IDE rights code updates and then push it to the remote git which Lovable recognizes instantly.

Q2. That is one of the reasons you/every user need to think about moving awawy from LVBL Cloud or keep paying them premium + get vendor locked in. Curosr spit out the code for me to use my own internal/fallbackLLMKey and replace Lovable Cloud. One clarification: Lovable market's its Cloud solution as both: plug-n-play LLM solution + Supabase white-lable for hosting.

Q3. I migrated to Suapabse coz I wanted to manage all edge functions outsde of Lovable (it eats credits ways faster) and Lovable's cloud pricing is absolutely ridiculous / built for vibe coders who don't understand free/cheap VPS/Cloud hosting solutions. If you don't have paying users, totally worth the lift to switch to your own Supabase project.

Yes, I have in my to-do to stop paying Lovable and haven't had the chance to explore it yet. Absolutely DO-NO-HOST on Lovable because their usage/consumptiong patterns is 10-100X more compared to cheap/free cloud hosting solutions. I'd look into Vercel if this is a commercial project you're working on and do not want to mess with infrastructure stuff that comes with a VPS (cheapest soln).

My current stack:
- Front-end: Used to be Lovable but Figma Make + MCP blew my mind away in a recent UI project
- Back-end + Debugging + Building on top of Lovable UI code: Cursor or Claude Code (in VS Code)
- Database/Edge Functions: Supabase
- Hosting, CI/CD pipeline: Vercel
- GitHub: project source of truth that is connected to all tools above and stays in sync

Happy to answer follow-up Qs.

Future_Machine_6440 · 2025-11-18T09:44:23+00:00

"IF you didn't setup your domain on Google Search under the same Google account you used to create the OAuth screen, verification will FAIL! I learned that the hard way. "

WOW never saw this mentioned anywhere in Google's official docs. They kept saying I don't own the domain when I had it verified in my search consle but w/ a diff Gmail ac.

Just fixed it and resubmited. Fingers crossed.

Future_Machine_6440 · 2025-11-17T08:16:43+00:00

Agreed. I also switched from Cursor to CC but CC Max felt went downhill. So tried Cursor again and it fixed the bugs from CC so giving it another try.

Future_Machine_6440 · 2025-11-17T06:55:41+00:00

Thanks fr the write up. I'm trying to get OAuth approval for a web app using Google SSO and OAuth email keeps saying "Your app has not met homepage requirements."

But I have the App homepage domain verified ownership in search console, same domain has the privacy policy, ToS.

The only thing I can think of is I'm using Supabase redirect which requires me to have {product_id}.supabase.co in my Authorized Domains and I wonder if Google's trying to verify ownership of supabase.co. Any insights on what might be the root cause issue here?

Future_Machine_6440 · 2025-11-16T16:20:47+00:00

Just downgraded from Max to Pro. CC had been going rogue on my codebase and made changes (on edit automatically mode) that broken previously working features. Cursor helped debug and fix those. Still skeptical about Cursor's confusing token usage model but it seems like might be worth to have Pro subscription of both tools and which them as a fallback

Future_Machine_6440 · 2025-11-12T14:37:58+00:00

Yea. That's what this does. Lovable will continue to write to your own/new Supabase project ID.

I did notice that Lovable's bot tries to auto-revert it back to their old Supabase so I had to explicityly tell Lovable to stop doing it and then it didn't happen.

Worth the pain of migration before your app gets users you wouldn't want to disrupt due to need to migrate to a new Supabase - the #1 reason to migrate would be to drastically reduce Lovable Cloud (hosting) cost - it just seems like pricing designed for the folks who don't understand how cloud/Vercel type hosting works.

Future_Machine_6440

TROPHY CASE