Hacker News new | past | comments | ask | show | jobs | submit login

Here’s a direct link to Capital One Software: https://www.capitalone.com/software/

And a link to the first product they launched, “Slingshot”: https://www.capitalone.com/software/solutions/

Essentially it sounds like Capital One is taking some of their internal tooling and starting to sell it, starting with their tooling for managing Snowflake instances.




I see they’ve already mastered the enterprise software technique of a “screen-by-screen video” that shows zero actual screens of the actual product, just a series of animations vaguely indicating business processes that are efficient & scale & managed etc.


Can’t express how much I hate those videos.

A higher density of utter meaningless bullshit, I couldn’t find anywhere else in marketing.


it's like our version of the "Turbo Encabulator" https://www.youtube.com/watch?v=Ac7G7xOG2Ag


My number one pet peeve in the sales cycle. We just docusigned to switch to a new platform - 50% of this was because their demo and other videos ACTUALLY SHOWED THE PRODUCT and they had youtube playlists with more!!


How else do you get people to sign and/or pay for dogshit you haven't even built or battle tested yet? (if you're offended, I'm talking about your product)


Ironically these are called "explainer" videos too. :)


I've been out of consulting for 7 years now, so I don't know how widespread or old the trend is, but I'm seeing a lot of banks moving to a product operating model for their internal/backend software. The last place I worked had been at it for a couple of years and there were a few teams that really ran with it. At some point why not turn them into a profit center?


Years ago when I was at Chase Manhattan (shudder) they were at the other end of the extreme where there were multiple teams within the bank that did the exact same thing, and they would have to undercut one another to get business from other internal teams. Somehow everyone got enough business that the teams didn’t ever merge which is good, because rivalries between the teams became so fierce that none of them could work with someone who had been on a competing team. Managers loved it because if you had dollars to spend you would have a lot of people kissing up to win your favor - you could get a lot of free lunches and end of year your office would be full of gift baskets.


Allegedly, Rocket Mortgage was built on top of an internal project + lessons learned for another large bank. One could argue that was a very specific example of the general trend you're discussing.


I've seen so many companies in multiple domains including consulting firms be so proud of their software they try to sell it on the open market. I've also never seen it succeed.

Whatever you have to say about Capital One as a bank or as a software company, they are absolutely top tier when it comes to marketing. At least B2C marketing. If they succeed at this it will be on the strength of their marketing.


Yes, this a thousand times over!

Why would I spend 100x the cost to buy an internally developed solution that is barely an MVP product when I could buy a market leading, polished, SaaS product from a vendor who takes me out to dinner and ballgames? They also have implementation and professional service teams to help install said product quickly and efficiently, and many third party consulting firms if I need even more help (they take me out to dinner too!).

Oh, also the vendor doesn't yell at me like the internal IT teams do :)

Quite the conundrum for sure!

Would love to know which execs approved this at Capital One and what happens when they leave and everyone's air cover is gone?


> Why would I spend 100x the cost to buy an internally developed solution that is barely an MVP product when I could buy a market leading, polished, SaaS product from a vendor who takes me out to dinner and ballgames?

Sooo... not Google products?


The trend of banks outsourcing software dates back decades. The "online banking" systems of most small banks and credit unions are outsourced, for example; if you have three branches and an IT staff of two people, you're going to struggle to maintain those sorts of systems yourself, never mind developing them in the first place.


Snowflake, in my circles, means something that's outside of the patterns in use and doesn't scale. It's something that's inherently bad and you want as little of it as possible, preferably make it visible and obvious, and manage it outside of your regular repositories and pipelines. Keep bringing it up at retros and planning until it's either industrialised along with the other things you support, or you drop/refactor/hand over.

Terrible name for a product!


Weird. In my circles, and the circles of people who are in the market for such a product, snowflake indicates a particular design pattern for designing data warehouses.


You’re both right. Snowflake as a technical slang/jargon generally refers to “flaky” or light-weight solutions that aren’t expected to withstand the test of time/scale.

Snowflake, the data warehousing platform, on the other hand is a juggernaut - in a league of it’s own (I suppose comparable to BigQuery and RedShift).


To be fair, neither of us even could be wrong, we both expressed things as they are within each of our contexts, and personal opinions. :)





Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: