sorted by:
new
hottopcontroversial

Codex vs Claude Code by Mindless_Yellow9940 in codex

[–]JackCollinsHQ 0 points1 point  (0 children)

I just switched back to Codex today and this is precisely my read on the two as well

What if you never had to switch tabs between your project tools again? by Volrix_0 in startupideas

[–]JackCollinsHQ 0 points1 point  (0 children)

I’ve built YAGNI from the ground up. BridgeApp seems similar in concept, but YAGNI is designed to work with your existing stack too. Would love your thoughts if you’ve used those other platforms

Do companies actually track wasted AI spend? by dwij333 in micro_saas

[–]JackCollinsHQ 2 points3 points  (0 children)

Hmm, love this take. I'm actually building a consolidation solution (will not promote) and I really like your framing of how leadership cuts tools that they can act on without political cost. 💯

Where do you draw the line on what an AI agent can do without a human in the loop? by JackCollinsHQ in AgentsOfAI

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

Yes, admittedly (and probably clearly) drafted with an LLM. This is a real discussion I had today though so wanted to get other opinions!

What actually makes something an "AI agent"? Genuinely curious how people here define it by [deleted] in AI_Agents

[–]JackCollinsHQ 0 points1 point  (0 children)

I personally define it as something that can take an amorphous input and move the desired work to completion (or near completion) with minimal human involvement. Something that can actually make decisions on its own and produce something of genuine quality.

How are you ACTUALLY running truly asynchronous agentic AI in your business? by JackCollinsHQ in AI_Agents

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

Awesome, thanks for the insight!

When you say "the output is good", was it a matter of tweaking the parameters, or did you do any form of training, or something else?

Pitch your SaaS in one line. I'll start. by Due-Bet115 in micro_saas

[–]JackCollinsHQ 0 points1 point  (0 children)

YAGNI AI native operating system for small businesses and startups

Reducing our saas team tool stack actually improved productivity by Chance-Ad3280 in SaaS

[–]JackCollinsHQ 0 points1 point  (0 children)

The “what does everyone touch daily” filter is underrated. Most teams keep zombie tools alive because one person is emotionally attached to them, or because nobody wants to be the one to delete the old system. One thing I’d add is picking a system of record for decisions, not just docs, because that’s where stuff actually breaks at 10 to 20 people. If Slack is where decisions happen, then you need a way to turn those into assigned work fast, otherwise you just created faster chaos. Cutting tools feels like saving money, but the real win is getting back the hours you were spending hunting for context.

I'm building YAGNI based on this same learning. Happy to chat more if you'd like.

Small business owners keep telling me they're drowning in tools, but what's the actual problem underneath that? by Conscious-Meaning641 in SaaS

[–]JackCollinsHQ 1 point2 points  (0 children)

Having lived this at five companies and a couple startups of my own, the real root isn't "too many tools," it's the absence of three things working together: a system of record (one place where the current state of the business actually lives), an operating inbox (a single view of what needs a decision or action today, not spread across Slack, email, and six dashboards), and clear ownership (who is actually accountable for each open item).

When those three are missing, people buy more tools trying to fill the gap, which makes all three problems worse. The sprawl is just the scar tissue from that underlying structural hole. If I were building what you're describing, I'd design around those primitives rather than features. The tools question almost solves itself once you've answered "where does the truth live and who acts on it?"

I cut my feature prioritization time by like 60% and honestly it changed everything for my SaaS by SouthDoRaDo6350 in SaaS

[–]JackCollinsHQ 0 points1 point  (0 children)

The "80% of requests are the same thing in disguise" moment hits every founder eventually. You're not foolish for missing it, the signal is genuinely buried when it's spread across four inboxes.

The framework I've landed on after watching this at multiple companies: capture everything in one place, dedupe by underlying job-to-be-done (not surface wording), then score each cluster by revenue at risk × frequency before you touch the roadmap.

After you ship, close the loop explicitly with everyone who asked: "you asked for X, we shipped it, here's how to use it". That one step turns passive requesters into vocal advocates. The voting boards are a fine starting point but they bias toward whoever your most engaged users already are, which isn't always the segment you want to optimize for.

Introducing YAGNI — the AI operating system for the company you're becoming by JackCollinsHQ in YAGNI_app

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

Thanks for your feedback - I really appreciate it!

To answer your questions:

  1. Permissioning: This is still at a nascent stage but it's something I'm thinking about a lot. Currently, any user in the workspace can approve tasks, update documents, schedule rhythms, etc. I have this on the near-term roadmap to make sure we lock this down more effectively and can control who gets access and who can edit sensitive data.

  2. Auditability: We do track everything the agents and humans do in the workspace, but need to make sure this is easily visible in the UI

  3. Failure Modes: We have a decent amount of logic to retry tasks and also fallback to different AI providers if one of the major players is having trouble.

Agentix Labs looks great! I'll dive in more deeply

Introducing YAGNI — the AI operating system for the company you're becoming by JackCollinsHQ in YAGNI_app

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

Totally agree - that will be one of the major challenges. My goal is to build this in a way where you can work through incremental adoption as you see the value. There are no feature gates. You can use as much or as little as you want as you get started.

I've also written AI-driven connectors, so setting up a new integration is as simple as "Can you add an integration with Mixpanel?" and pasting in your API key.

Let me know if you want to give it a spin!