Viktor Solovej

It s easy to measure latency or accuracy.

But the real costs often hide in the background- compute burn, idle tokens, redundant calls, or that temporary caching fix that quietly eats your budget.

We ve seen a wave of AI tools for building workflows but what about the actual frameworks that developers rely on?

A good framework should feel like infrastructure:

Reliable under scale

I have launched on PH twice but before launching, I always prefer to share the product with at least 20 potential users over DM. The goal is to get early feedback and testimonials. This helps me understand what s working (or not) in the copy, design, offer, value proposition, etc.
Based on those early insights, I iterate quickly and it could be small tweaks or full rewrites, depending on what people are saying.

To make it easy for them to say yes and share feedback, I create a no-brainer offer (like 70 90% discount) and DM potential users on X asking for feedback.
What s your pre launch strategy for collecting feedback and improving your product before launching on PH?
P.S. Here s a sample DM I use to get early feedback for Boringlaunch:
Hey [User Name]

We ve just launched (product name) for [Industry/Category/Domain/Target Audience]

It might be a great fit for your [product name].