What would stop you from trying Together Link (https://www.together.ai/link) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Harry Strackeneutral

The primary concern stopping me from immediately adopting Together Link this month is the lack of a clear, consolidated cost projection for my specific team's usage. While the product claims significant cost reduction, my current workflow involves manually tracking model usage and cost deltas in a spreadsheet. I need to understand how Together Link's per-session receipts and usage reports would integrate with or replace this, and what the actual overhead would be for a 5-person engineering team running coding agents. Without a clearer picture of potential aggregate costs and a more robust system than a spreadsheet, it's difficult to commit.

Simulated interest: 40/100

Carmen Dickinsonneutral

I'm intrigued by the idea of using open models with my existing tools, especially to reduce costs. Currently, I handle this by manually running experiments and tracking token spend in spreadsheets. The idea of an automated router is appealing, but I'd need to see how it handles complex coding tasks versus simpler ones before fully committing. I'd also want to understand how the "receipt for every session" translates into my current logging practices in Notion. For now, I'm not looking to pay for this, so my maximum would be $0 per month. I'd prefer to test its efficacy within my current workflow first.

Simulated interest: 40/100

Glen Little-Gerlachneutral

What would stop me from trying Together Link this month? Honestly, it's the "beta" label. My agency operates on tight client deadlines, so introducing untested tools, even for boilerplate or refactoring, carries a risk. We currently use custom scripts and free tools to manage our AI agent costs, meticulously tracking everything in Sheets. While the promise of cutting costs by over 50% is attractive, I'd need to see some concrete evidence of stability and reliability in a production environment before fully committing. I'd be willing to experiment with a small part of a project first, perhaps capping usage at around $50 per month initially to monitor performance and cost, but I'd need to see clear usage reports and understand the support structure during this beta phase.

Simulated interest: 50/100

Geneva Luettgenneutral

What would stop me from trying Together Link this month is really just the current integration overhead. My team is already managing our internal developer tooling, which includes a commercial agent management tool we use for comparing open models against proprietary ones. While the promise of potentially cutting costs by over 50% is attractive, integrating another tool, even with a one-command setup, means we'd need to evaluate its impact on our existing dashboards and reporting before committing. We'd need to ensure the cost and latency data it provides aligns with what we're already collecting and that it doesn't introduce new complexities. If it seamlessly integrates and provides clearer cost-performance insights without adding significant management burden, I'd consider it. Regarding price, since the product states it's 'free' and 'MIT licensed' and the core value proposition seems to be cost reduction by using open models, I wouldn't expect to pay a subscription fee for the link itself. Any costs would be for the underlying model usage. Therefore, I would pay $0 for Together Link per month.

Simulated interest: 60/100

Sean Matschkeneutral

The biggest thing that would stop me is integration complexity and whether it genuinely saves us money without introducing new failure modes. We currently manage model switching and track costs meticulously in a spreadsheet. Together Link promises to simplify that, which is appealing. However, I need to see how seamlessly it integrates with our existing CI harness and coding agents. A key concern is ensuring consistent performance, as we swap models for different tasks. If it can automate cost tracking and model routing effectively without adding operational overhead, I’d consider it. My max would be around $100 per month, given our current spend is moderate and I'm cautious about introducing new subscription costs.

Simulated interest: 50/100

Silke de Haanneutral

My main hesitation is actually trying to integrate another tool into my workflow. I currently manage my AI model calls through a simple spreadsheet, which works fine for me. I also tend to stick with free tools and local scripts where possible, and I'm always a bit wary of adding new subscription costs. The pricing model here seems to be per month, but without knowing my specific usage, it's hard to estimate. If I were to consider it, I'd probably cap it at around $20 per month to see how it goes, but honestly, I'd likely stick to my current method unless the cost savings were extremely clear and significant.

Simulated interest: 30/100

Chitraksh Pillaineutral

My current process involves manually comparing open-source models against commercial ones and meticulously tracking API costs. What would stop me from trying Together Link is the integration effort; we're a small team and time is scarce. I'd need to be convinced it simplifies, not complicates, our workflow and truly offers cost savings. The pricing model itself seems reasonable for a subscription, but I'd need to see actual usage reports before committing. I'm willing to pay up to $50 per month for a tool like this, provided it demonstrably reduces our current expenses.

Simulated interest: 60/100

Rupinder Joshineutral

My biggest concern right now is the manual tracking of AI model usage and test results because we don't have a paid orchestration tool. I spend a lot of time logging this in Jira and spreadsheets. While Together Link seems to offer automatic tracking, I'm hesitant to try anything new this month as we're trying to stabilize our current flaky test suites. Also, I need to understand the exact pricing structure for the auto-router feature – is it a flat monthly fee or pay-as-you-go for usage? The pricing page mentions amounts like '$3.00 in', which isn't clear for a monthly subscription. I would be willing to pay around $50 per month if it significantly reduces my current administrative burden and proves reliable.

Simulated interest: 60/100

Aquilin Schmittneutral

My primary hesitation is the need for thorough internal prototyping before adopting any new tool, especially one that interfaces with our existing workflows. I need to see concrete benchmarks and cost-benefit analyses specific to our use cases. Currently, I manage model comparisons and cloud spend in a spreadsheet, which provides a clear, albeit manual, view of our costs. I'd be willing to consider Together Link if it could demonstrably reduce our cloud ML infrastructure costs by at least 30-40%, as cutting costs is a significant concern for our startup. A monthly spend of $150 USD for the service seems plausible if those savings are realized.

Simulated interest: 60/100

Alva Gustafssonneutral

The main thing that would stop me from trying Together Link this month is the overhead of setting it up and ensuring it integrates smoothly with my existing scripts and editor workflow. Today, I manually track model performance and costs in a spreadsheet for each repository task, which is time-consuming but gives me direct control. I need to be sure this tool simplifies that process without introducing new complexities. If it truly automates model evaluation and cost tracking, saving me significant time, I'd consider paying for it. I'd be willing to pay up to $20 per month for this service, based on the per-token pricing model they seem to imply, as my usage is relatively low as a solo founder.

Simulated interest: 60/100