How Should I Price a Python Module License for Major Banks?

[mafellows]

I have an opportunity to license a Python module to several major banking institutions—some of the largest in the world. Typically, we offer this software as a web app, but these banks need a local module to run within their own environments.

Here's the situation:

- Product: A Python module that performs complex analysis on source code and generates a risk assessment. - Usage: It will be integrated into their CI/CD pipelines, and developers can also run it manually. - User Base: About 50 users per institution, mostly small, specialized teams. - Updates: We'll provide quarterly updates as we continue to develop the tool.

I'm trying to figure out how to price this. I don't want to set a price that's either prohibitively expensive or too low, especially since I haven't licensed source code to clients of this scale before.

For those with experience in this area:

- How did you approach pricing in similar situations? - Are there industry standards or benchmarks for licensing software modules to large banks? - What factors should I consider when negotiating pricing and terms with these institutions?

Any insights or advice would be greatly appreciated!

[quintes]

I can think of these questions

1. Who are competitors in this space and what do they charge for business or enterprise?

2. Why do these banks pick your solution over others?

3. What is a reasonable price point including your own costs that make this desirable for them and feasible for you?

4. Pricing model, will you bill like a SaaS or a yearly subscription? What about users leaving, adds and changes?

[mafellows]

1. Not many competitors, but each competitor offers about a $500/mo plan that allows ~10 users. 2. We have greater accuracy and detail in our analysis. This has been proven with sample data and they agree that this is true. 3. $500/mo seems too much on the low-end for this. I'm not sure what "high" would be for a bank.. $5k, $10k? 4. I would like to bill this as an annual contract with monthly, quarterly, or annual payments. Current SaaS users are billed monthly or annually. Since they'll be self-hosting this, they will be responsible for user management and access. I will not have access to their internal systems.

The root of the pricing problem is we charge based on usage. If they self-host, we won't be measuring that usage as the tool will run without network connectivity.

[quintes]

Price for competitive value, start where you think, but - tier it to bundle of users at least, so as more users are added any additional effort on your part has financial cover

- think about support, customer success, installation, upgrades and ensure your including that

- test the number with them. Negotiate.

Caveat - this is limited advice use at own risk etc etc

[giantg2]

Also, what is the financial risk the software is reducing or eliminating? If it massively reduces risk, it could adjust the price higher. These banks wouldn't bat an eye at $100k/yr if it has the chance to reduce a million screw-up byba sufficient amount.

[paulcole]

How many people at a bank can approve a $100k purchase order vs. a $1,000 purchase order?

[giantg2]

They're talking about an app team. The manager can likely approve 100k

[airbreather]

Probably the real cost is in providing adequate ongoing support, and possibly insurances, and I suspect the banks know this and might baulk at too low a figure.

They don't want to be left holding the bag.

So I would have thought a risk based approach to the situation would be in order, especially given the nature of the situation.

What will it cost to get external validation services performed to check the code?

What could it cost if you had to pay consultants to do what would be needed if there was an error or a breach associated with the module, in terms of analysis and rectification?

What will it cost to have people available who are familiar with the code to make any changes that might be requested?

What will it cost to develop the code further and stay in front of competitors or attackers?

What will insurances cost, given the possible losses and probability a loss could occur?

Will you be limited to exclusivity? e.g. not sell to other banks who might be competitors.

Given the above, will you need to have dedicated premises and infrastructure?

So what, 5-8 people at reasonable wages for skills and experience, plus insurance, premises, infrastructure and other factors, like keeping people interested to stay working for you in a maybe boring job? Plus actually make some profit and stash some cash for a rainy day or another development opportunity to pursue.

Starts to sound like 1-3 mill a year all up is needed to run it as a going concern, if you are going to do it properly and depending where you are based. Maybe more if insurances are expensive.

Otherwise, are you sure you can't sell them the IP and walk away?

[philomath_mn]

Do you charge for the web app version? I'd expect the module version to be somewhat close to that?

Also make sure to expect a lot of pain working with IT at the banks. I worked with some people at US Bank and their restrictions were absolutely draconian.

For example, I had to make a vanilla version of the python tool I was working on for them because they had to review every one of my dependencies! I also couldn't send any kind of zip file to them so I ended up making a plain text encoding/decoding scheme so I could attach code distributions to emails.

[eschneider]

You want to (among other things) think about these things:

1) What's the value of the software to the bank? 2) What other options do they have and what are the costs? 3) Is this a one-time license or something ongoing? 4) What level of support are they going to want/need and what will it cost to provide.

[mafellows]

1) There is certainly value, but I would consider this a vitamin, not a painkiller. 2) Options if they were to pick something off the shelf would be $500/mo minimum. Quality is slightly less than what they're getting with us. 3) Annual contract, we would provide updates at a tbd interval. 4) We definitely have an opportunity to price in additional support. Whether they choose to use it or not, it would make the license price seem more reasonable.

[wdb]

In the past I charged $100k/year per client for something similar

[brudgers]

Two engineers @ $150k/year for redundancy

  $300k

2x cost multiplier

  $600k

100% markup

  $1200k

16% discount for 5 year contract

  $5000k @ $1000k/year

Plus expenses marked up with overhead and profit in order to travel to their site.

It is not your job to save customers/clients money on your services. Charge enough so it is worth staying in business. That’s what banks want. If you aren’t making a bunch of money, you are a greater risk for theft. Good luck.

[b20000]

ask them how much money is at stake

then charge them a fraction of that