FWIW it’s trending on huggingface papers and there is a more in-depth discussion there[1]. Seems like the early results are promising and someone replicated that independently but it still needs to be proven that the claims work also at the bigger scale.
[1] https://huggingface.co/papers/2509.26507
It’s cool that you’ve built it! It truly gets complicated, especially when at later stage you start getting venture debt (not safes), more demanding LiqPref and you’re facing an exit at a price which is not ideal.
Tbh I usually end up with bespoke excel files for each company to have a full understanding of waterfall for all parties and be able to simulate their payout and incentives at different exit price.
But I’m sure even this tool can be helpful - if you need any help with that, lmk!
This makes no sense and impacts a lot of early stage software projects.
In many cases for bootstrap ones it makes them not financially viable - 100%+ effective tax rate would do that if you optimize for early profitability.
Even for VC backed ones, those taxes just eat into your runway. I know a bunch of companies that opt for some weird international setup to try and avoid the effects but it’s really not what you should do in early days…
Yeah, at this point a bunch of European countries have this setup. As long as you don’t have a complicated source-of-revenue situation (which is true for vast majority of population), you just confirm the tax return on a governmental app and you’re done.
It’s extremely convenient, after they implemented a couple of years back, the time needed for tax return each year got down to maybe 2 min if you can use a computer.
Some take it even further. Inaction is considered approval. So you do not even need to confirm anything at all. You are likely to get tax return on your account automatically. Or a bill send at you. Or you can update details if needed.
Still, you have some years to ask for correction even after that, but as usual it is somewhat more complicated.
It's not even that hard if you have a discrepancy. Here in the UK, if you end up with a discrepancy (starting. Anew job, or benefits changes) and it's wrong, 98% of the time a single phone call will resolve the issue.
Hashi got really good at ignoring PRs if they weren't their own. They even ignored the PRs coming from the dev teams of their own customers (ie users of TF Cloud and Enterprise) which speaks volumes about their willingness to listen to the community...
I've seen people using archbee.io for similar use case. Archbee is a lightweight docs tool for developers with various integrations so should check your boxes (full disclosure - I'm an investor there :)
Rescue time, tag at the application level (obviously not fantastically accurate), and sub tag in chrome based on website.
It’s directionally correct at best, but still helpful.
Would also do a secondary form of manual evaluation by paying someone to text or call with a daily list of questions, but only have about 1.5 of years of data there. I ran the regressions and they are highly correlated in a time lagged way. In particular, sleep, for me, drove a lot of everything else. But from there it’s hard to say what the causality is (were you tired because of work to begin with? Or were you unproductive because of sleep?)