@Frank van Bokhorst whatever you do, don't pour $$ to top up. I pay for the pro and get a decent amount of tokens. If you structure your architecture right, you'll spend less. Claude does less thinking when it knows what you want.

@Drique Sd Currently it is a CRM program for my construction business. Trying to make a complicated program simple. Its still complicated but easier to navigate than other apps i've found. Would be great to explore company specific data entry bots as well. What are you building?

@Drique Sd That’s exactly where I think the opportunity is too. Most construction CRMs feel like they were built by software companies instead of people who’ve actually run projects on-site. Too many clicks, too much clutter, and none of the real workflow logic operators need day-to-day. The admin side is where businesses bleed time though — variations, data entry, scheduling, supplier orders, client updates, invoicing. If AI can quietly handle 70–80% of that in the background, a solo operator suddenly runs like a full office team. Your blueprint sounds aligned with where things are heading. The “one operator, fully connected systems” model is going to become massive over the next few years. I’ll definitely check your profile out 🙌

@Mark Deemer hey mark- happy to throw some ideas your way or develop some systems to help your company.

@Eva Gelion i'd say most are shipping. I've seen a lot of quasi professional apps getting around. Data breaches are a real concern if no security enabled within the architecture.

You'll need to find out what the issue is and if you need to add a new skill or built in instruction/rule for your machine. There's always a common denominator with problems and there's always a solution.

@James Lerinc sometimes that's the best way if you're not in too deep. I've found the biggest issues are always the simplest fixes. You can always revert back or trace for bugs, audit, smoke test, leak test etc. I've done this several times to get my projects back on track.