When you partner with a business in b2b most data is delivered through sftp channels.
Make a tool that vastly simplifies that. Be it onboarding, offboarding, alerting, emailing, the works.
When you partner with a business in b2b most data is delivered through sftp channels.
Make a tool that vastly simplifies that. Be it onboarding, offboarding, alerting, emailing, the works.
Some notes:
* facilitation of non technical ops people (sales, client success, etc)
* automates status reporting to stake holders (did we get the data yet?)
* as part of status reporting, ability to mark data as QA’d / next steps
* how to hand off data to internal team
* on prem in your cluster (think regulated industries)
* notification/dashboard of file arrivals (think did weekly file come from partner X?)
Probably some big enterprise tool out there that does all this. Always wished there was an open source “sidecar” to a sftp server that would help lighten the load of random communication overhead of moving csv’s or other flat files back and forth between clients and keeping non technical people updated.
So, you’d probably need to build both halves of the FTP chain, but each would still need to deliver the value add if only half of the new system was being used.
Or would you have been able to get this information from FTP access logs?
Or could you have done it simply by checking if files existed?
I am building something like this for data scientists (currently being used in finance) and wonder if it wouldn't also have served your team well.
I'm not involved in this project anymore, so it's not a current conundrum for me, but we had this issue a few quarters ago.