We'll occasionally flag accounts that have dormant API activity in our development tier, but as long as you're still using the API we're happy to cover the cost of the free account.
202 karma · joined June 29, 2012
charley at plaid.com
allthefintech.com
We'll occasionally flag accounts that have dormant API activity in our development tier, but as long as you're still using the API we're happy to cover the cost of the free account.
Once you want to add more than 100 accounts, we recommend reaching out to learn more about pricing at scale; it depends on what APIs are being used, how much data is being pulled, how often, etc. Feel free to shoot me an email directly if you have any questions! (charley@plaid.com)
For SMBs, there's a self service model that's low touch but for enterprises, the sales + customer service is very high touch and requires a lot more customization.
BI tools such as Periscope, Looker, Mode, Tableau, etc are also a bit of a hybrid. Usually starts off with an individual playing around or looking for a tool (pretty self service), but a full company deployment is much more hands on and high touch.
Following the framework that Patrick provides, odds are that any company that has "sales engineering" or "integration engineering" for a SaaS will likely be high touch (unless they're doing it wrong =D)
The other appealing draw for me was also high interest rate, but curious to hear what are the killer features for a digital bank.
Love the logic built around pairing transactions to external wallets and tracking the cost basis, how has your experience been working with the various exchange APIs and getting those integrated?
If you have any other questions, feel free to reach me directly at charley@plaid
A lot of the comparison is also dependent upon the use case, but I usually bring up coverage, performance, and simplicity.
Coverage - Custom integrations with the largest banks in the US that's also supplemented by "longtail" providers to give comprehensive coverage across the US.
Performance & Quality - 12 seconds or less to connect a user's bank account and begin to pull down data, which is particularly important for a mobile experience. We've also completely optimized our drop-in module used for onboarding bank accounts! (I think it looks pretty sweet: plaid.com/docs/quickstart)
Simplicity - Check out the docs yourself! (plaid.com/docs/api) usually takes only a few days to integrate, rather than a few months.
Few questions that came to mind for me: - What's the incentive on the advisor to offer the add-on service? Is it to eventually increase AUM and encourage more 401k savings from the users? Would be curious to learn if there are any numbers around this or users taking loans out, etc
- What does the platform look like? White-labeled self-hosted? What does an integration look like for the advisor
- What would be the general distribution plan and target market for getting advisors on board?
Additionally, the large banks are trying to influence the rules and requirements; for example, clearXchange + early warning system merging under a (large) bank consortium
http://blog.charleyma.com/square-cash-initial-thoughts-scree...
Overall though, extremely impressed with Square's offering and it was also instantly debited to my account. Curious to see if the value increases to a somewhat significant amount if this "instant transfer" translates into 1-2 business days.
Most obvious long-run plan would be for user/debit card acquisition (which has lower interchange rates) to support their bread and butter business (merchant tools) as this would increase their profit margins by reducing processing expenses, especially since Square simply charges a single rate to merchants...
however the primary concern that I always have with any sort of version control programs is the fact that the documents must be completely internal and within our firewall, any sort of external hosting is usually not secure enough, and most solutions seem to lack easy implementation due to the speed of technology at large banks.