mrajcok
Will have Llama 4 Maverick running in 4bit quantization (typically results in only minor quality degradation) once llama.cpp support is merged.
Total hardware cost well under $50,000.
The 2T Behemoth model is tougher, but enough Blackwell 6000 Pro cards (16) should be able to run it for under $200k.
Mystro (YC S17) says Lyft blocked popular app that helps drivers manage gigs
Mystro (YC S17) Is Hiring a Software Engineer
When the driver is not on a trip, we turn on both apps. When they are on a trip, we turn off the app not in use.
We've thought about pitching in the car but the cost doesn't work out.
It's much harder to do UI automation on iOS -- it is more locked down.
We have a pretty robust tool to keep our integration working with any app updates.
Thanks!
We have a framework built out that lets us rapidly respond to app updates and a team of testers all over the US.
We have also thought about how to best circumvent any active attempts to block us -- since we interface with the driver apps directly rather than any APIs that would be harder to do.
There is also the potential to use the data we have to optimize driver revenue even further.
Launch HN: Mystro (YC S17) – Automation for On-Demand Drivers
Hi! I'm Matt from Mystro (http://www.mystrodriver.com) and we're in the current YC batch. We're building an app for on-demand drivers to automate the process of driving for multiple platforms.My co-founder got the idea for Mystro while completing over 10,000 trips as an Uber/Lyft driver.We automate switching multiple on-demand apps on and off. This ensures that drivers are available on all...
This avoids the exercise window and acquisition concerns, is pretty tax favorable, and largely aligns your treatment with the founders. It is a bit riskier even if the company agrees to offset the loan with bonuses over time, but at lower valuations I think it is worth considering.
In any case, it's worth it to have a good lawyer look over all your options paperwork to make sure you are getting a fair deal.
I'd need to do more research to find the best solution but it looks like payment processor risk is definitely something that can be mitigated.
That said, the "self-help" takedown sounded problematic -- much better to have the option of a copyright infringement claim.
If a client pushes back on this provision you can explain that you are 100% insistent but it only comes into question if they don't pay -- that has resolved all objections in my experience, and if they pushed further I'd treat it as a major red flag.
Do fixed fee if you can -- this gives you an incentive to invest in becoming more efficient and gives your clients predictability. Jonathan Stark has some good material on moving away from hourly: https://expensiveproblem.com/
The thing that's been a huge success for my freelancing business and helped me avoid feast or famine is having ongoing, hands-off sales processes that keep going no matter how busy I am with client work.
I hired a VA and originally had her email relevant leads from lead newsletters like LetsMakeApps or Workshop, and now am shifting towards cold email towards relevant leads. Use a CRM (close.io is my personal favorite) and a drip email service like prospect.io for automatic followups -- persistence boosts conversion rates massively for this sort of sales. Block off a day or two a week to take sales meetings and use Calendly to schedule -- meetings popping up whenever is huge impediment to flow, but keeping up sales regardless of how busy you are. If you get overwhelmed, raise your prices to reduce the amount of work you are selling.
Happy to talk about building a freelancing business -- email in profile.