Dilution: there is a “dilution” row that lets you specify the dilution percentage for potential future rounds/valuations. I used 20% as the default because this is roughly what you'd expect in a typical priced round, but this is user-editable.
Tax: tax modeling is hard. I haven’t attempted to do it in this version. I might add it in future versions.
Fractional share rounding during monthly vesting: it rounds the running total of shares vested to date each month, then reports each month’s vested amount as the difference between this month’s rounded total and last month’s. This way, rounding errors never accumulate and the schedule always sums exactly to the full grant.
I’m not sure what you mean by “any incentives besides having a userbase?” Are you asking why I built it? I’m a startup GC and I do this type of modeling all the time, so I wanted to build the definitive tool, and I wanted to open-source it and share it with HN for feedback.
Science (https://science.xyz/) | SF Bay Area (Alameda, CA) | Onsite | Software engineers, mechanical engineers, electrical engineers
We’re a neural engineering company that just raised $110M led by Khosla. We’re looking for exceptional software/mechanical/electrical engineers. More: https://science.xyz/careers/. Feel free to reach out at joem@[ourdomain.xyz].
Science (https://science.xyz/) | SF Bay Area (Alameda, CA) | Onsite | Software engineers, mechanical engineers, electrical engineers
We’re a neural engineering company that just raised $110M led by Khosla. We’re looking for exceptional software/mechanical/electrical engineers. More: https://science.xyz/careers/. Feel free to reach out at joem@[ourdomain.xyz].
I use G Suite for one domain (because I was grandfathered into a free plan) and Zoho for others. IMAP is a little faster in Zoho, and I haven't seen a difference in reliability. The Google web interface is much better, though.
Same here. Sometimes I'll also add the date when I entered the address in a form. For instance, the last time I registered to vote, I used YYYYMMDD-ca-voter-registration@mydomain.org. During the last election cycle, I caught a few California politicians harvesting my address and adding it to their email lists.
Ironically the CAN-SPAM Act only prevents commercial entities from doing this, however shady the practice may be. Political emails are protected free speech and AFAIK the means by which addresses are obtained is irrelevant.
That's a small chunk of the functionality most APIs need. Why write all of your API views from scratch when there's an excellent framework that handles it for you?
Dilution: there is a “dilution” row that lets you specify the dilution percentage for potential future rounds/valuations. I used 20% as the default because this is roughly what you'd expect in a typical priced round, but this is user-editable.
Tax: tax modeling is hard. I haven’t attempted to do it in this version. I might add it in future versions.
Fractional share rounding during monthly vesting: it rounds the running total of shares vested to date each month, then reports each month’s vested amount as the difference between this month’s rounded total and last month’s. This way, rounding errors never accumulate and the schedule always sums exactly to the full grant.
I’m not sure what you mean by “any incentives besides having a userbase?” Are you asking why I built it? I’m a startup GC and I do this type of modeling all the time, so I wanted to build the definitive tool, and I wanted to open-source it and share it with HN for feedback.