4 ms·
AR as a service is something I've been thinking about for a while. I was thinking more "Stripe for Purchase Orders" though. I can definitely see my business usi
by chromaton 9y ago
AR as a service is something I've been thinking about for a while. I was thinking more "Stripe for Purchase Orders" though. I can definitely see my business using this. It's a billion dollar business if done correctly.
- ryanworl 9y agoI want to build this. Can you send an email to the address in my profile? I would love to talk to you for 5 minutes about it if you have time.
- gt_ 9y agoHaving come into software from creative fields, I wonder how this could be done. Blockchain? I would talk/share my experiences with you. If you are asking enough questions, I might help.
- rficcaglia 9y agoyes, I think this would be a good "smart contract" use case.
- gt_ 9y agoAnother comment mentioned invoice factoring, and this is different but I think we have to remember that the big companies are going to use invoice refactoring. This might be one for the blockchain. :O
- rficcaglia 9y agoI think blockchain factoring is interesting, though in the US there are many tax and legal issues surrounding factoring [0]. So blockchain tech alone isn't a sufficient solution long term (as we've seen vis-a-vis ICOs.) I still think there is innovation to be had here, though. [0] https://www.amazon.com/American-Factoring-Law-David-Tatge/dp/1570187924 https://www.amazon.com/American-Factoring-Law-David-Tatge/dp...
- chromaton 9y agoThe "use blockchain" people are missing it. This is for dealing with companies that handle purchases through the very traditional Quote -> Purchase Order -> Delivery -> Invoice -> Payment system.
- rficcaglia 9y agoEDIT: re-read the parent and I think I grok now. So why can't the "traditional" quote to cash be embodied on ethereum?
- chromaton 9y agoWhat does that get you?
- rficcaglia 9y agoit gets me paid in a timely fashion, without human emotion from either party mucking things up. isn't that the goal? traditional: send PDF quote, go back and forth on quoted terms and cost 1..n times, wait for signed PO, call 1..n times reminding them to sign the PO, eventually get signed PO, do work, (at this point client is your BFF and calls you every 5 minutes asking if the work is done yet!), deliver product/service, get at least 100 bug reports on things that differ from the original approved spec/quote but should have been "implied", fix "bugs", send PDF invoice 1..n times, call buyer to remind them to pay invoice 1..n times, get runaround and sent to various accounting people most of whom are on vacation 1..n times, finally get told check is in mail 1..n times, wait 30 days per cycle, sacrifice chicken, call back and find that check was never sent and invoice is lost so repeat steps again, finally check arrives, deposit check in bank eth: seller defines contract in solidity with various Oraclized callbacks for spec acceptance, delivery of work product(s), final acceptance test execution, and various failure modes that return eth back to the buyer's wallet if necessary, buyer funds contract with eth, acceptance events (e.g. signed PDFs in dropbox, or some git commit, etc) triggers payment to seller's eth wallet, OR on failure cases returns money back to the buyer's wallet lots of hand wavy stuff here but since we're just discussing ideas...so, in all sincerity, what does this not get you that you are looking for? EDIT: fix typo