I think we need to reframe the problem. If we think of it as JSON data that comes with a PDF (similar to what @xmprt suggests "PDFs as checksum") then we have the benefit of machine-readable data that is transportable but also the attached human-readable PDF version of the data.
This is exactly what we are trying to achieve at Anvil.
1. Provide the no-code tools to make it easy to convert existing PDF forms into web forms.
2. Share the web forms with perspective customers instead of PDF forms as email attachments
3. PDFs are generated as part of the workflow once the data is captured and represented in structured JSON.
4. (optional) request certification of the PDF via e-signatures
The end result is a JSON payload that can be shared via API as well as a static PDF that is stored for human consumption. In most cases, we find that our customers actually just use the PDF as an interface with legacy systems (IRS, Banks, Insurance Companies) that haven't yet figured out how to modernize to a data-first business model.
Of course this really only addresses PDFs that are used for information capture and transfer between two parties. But most PDFs that are not "standardized-forms" are made for consumption by humans not by machines (think ebooks, journal articles, graphics etc), and therefore having a JSON payload of the data attached doesn't really matter.
Thank you! PDF forms are why we started this company, the process of downloading, printing, filling out, scanning and then emailing drove us to build a better solution.
Other Anvil founder here. Thats great to hear! Shoot us a message at [email protected] mentioning the ShowHN and we would be happy to see what we can do for you.
The one nice thing about German taxes is that, although complicated, they make it very easy for you to know how much you owe. They essentially obfuscate the complexity from the citizens.
Also, consider what you are getting for your German taxes, and it may very well be worth it. If only the MUNI in San Francisco ran like the U-Bahn. You really have no reason to own a car in Germany.
Also note, as a Software Engineer living in California, your income tax (State and Federal) is probably close to 40%.
When I worked at a cleantech startup in the summer of 2010, the culture was less favorable to employees than in the bay area. For example, it seemed that the cultural norm was to give none, or very little equity, thus reducing the upside for any early employee.
In recent years I have interviewed as a Software Engineer and Senior Product Manager at a couple startups in Germany. However, after receiving a couple offers, I found that the costs of living in Germany as an American (US Taxes, Visa, USD -> Euro exchange rate) were not sufficiently covered by the salaries, even on the high end.
For American companies looking to hire talent in Germany, I have heard that it is was less competitive, lower cost per engineer and the talent top notch.
Hi everyone, I am the creator of Ledger. We are part of YC Startup School - Founder Track.
I built Ledger because I wanted an easy way to track and split all of my shared expenses with friends.
A lot of my spending is shared between one or more people, and I hate the awkwardness around splitting a bill or asking for repayment. Other times, I know that there will be many shared expenses and I just wanted a quick way to track the expenses over time and settle up at the end or when the difference is owed is meaningful.
With Ledger, you create a shared "Ledger" between you and your friends, each person can contribute expenses to the Ledger and we automatically calculate the difference owed. Ledger is designed to be super light weight allowing you to quickly track and split an expense so you can get back to what you were doing. We automatically pull in your transactions from your credit card and bank accounts, so you never miss an expense and never have to type in a transaction manually. Lastly, if you have close friends that you see frequently, you can just have a running Ledger between each other, use it as a quick way to determine whose getting this round of drinks or paying for dinner, you may never have to actually settle up.
Would love for you to play with the app and please reach out with any feedback!
This is exactly what we are trying to achieve at Anvil. 1. Provide the no-code tools to make it easy to convert existing PDF forms into web forms. 2. Share the web forms with perspective customers instead of PDF forms as email attachments 3. PDFs are generated as part of the workflow once the data is captured and represented in structured JSON. 4. (optional) request certification of the PDF via e-signatures
The end result is a JSON payload that can be shared via API as well as a static PDF that is stored for human consumption. In most cases, we find that our customers actually just use the PDF as an interface with legacy systems (IRS, Banks, Insurance Companies) that haven't yet figured out how to modernize to a data-first business model.
Of course this really only addresses PDFs that are used for information capture and transfer between two parties. But most PDFs that are not "standardized-forms" are made for consumption by humans not by machines (think ebooks, journal articles, graphics etc), and therefore having a JSON payload of the data attached doesn't really matter.