2
3 Comments

Building ArchitectGBT : Are you tired of choosing the wrong AI model?

I'm building ArchitectGBT and want to validate if this is actually a problem people care about.

The Problem

Every time I start an AI project, I waste 5+ hours choosing the right model:

- Should I use Claude, GPT-4o, o3-mini?

- Which one is the cheapest?

- Which one is fastest?

- What about context window, latency, and reliability?

Then I pick one. Deploy. And realize 2 weeks later I picked wrong.

Last time: Last month i lost a good amount using GPT-4o when o3-mini would've worked perfectly.

I know I'm not alone.

My Solution (Idea)

ArchitectGBT:

- You describe your project

- AI tells you which model is best for YOUR use case

- See exact costs + performance tradeoffs

- Get starter code to deploy immediately

60 seconds instead of 5+ hours.

The Ask

I'm validating this idea with a simple landing page.

architectgbt.com

If you think this solves a real problem for you, join the waitlist.

Your email = signal to me that this is worth building.

Questions for You

1. Is this a problem you face?

2. Would you actually use this?

3. What would make you sign up?

Drop your honest thoughts in the comments 👇

posted toAvatar for product ArchitectGBT
ArchitectGBT
  1. 1

    Picking the wrong model wastes more time and money than people admit. The part I’m curious about is how deep your recommendations go. Most projects change once you hit real data or edge cases. Can it handle that or is it more of a starting point tool?

    1. 1

      Hi Bill i have implemented enhancements on the recommendations have you tired the tool now? thanks

    2. 1

      Thanks for the great feedback! You're absolutely right - projects evolve and edge cases matter. Right now, ArchitectGBT is designed as a starting point tool to help you narrow down options quickly. However, I am actively working on deeper features like:

      • Iterative recommendations (refine based on your feedback)

      • Real-world usage tracking (update recommendations as your project scales)

      • Edge case analysis (prompt for specific scenarios you might encounter)

      Your insight about model selection being costly is exactly why I am building this. Would love to hear more about what specific features would make this most valuable for your workflow.