Cost and Pricing#

Internal Cost#

  • Based on units of time.

  • Captures effort from both direct and indirect contributors.

External Price#

  • Included in tiered offerings (e.g., Advanced, Premier).

  • Can be negotiated as part of broader service agreements.

  • May be provided pro bono when aligned with strategic goals.

Example:

Up to 4 hours/quarter by the Product & Services team, reset each quarter. Additional hours: $250/hr.

Cost of the service#

The “unit of time” scale is intended to represent the capacity allocated to a particular Partnership Service agreement. By measuring allocated capacity, it also gives a way of estimating the cost to 1i2c required to deliver the service. The time and effort spent on a Partnership Service agreement reduces the capacity our team has for other deliverables. This cost is entirely internal to 2i2c and should be reviewed periodically to ensure that the service is priced appropriately to at least cover our costs.

It is the responsibility of the Product & Services Team to report on the costs incurred for this service.

Price of the service#

Community Enablement Service is meant to formalize the implicit value that 1i2c provides to our communities. The price charged for Community Enablement Service should scale with the “units of time” being offered but also may be included in a service agreement as a part of the overall negotiation of the price. For example, our Advanced and Premier tiers include ‘4 hours’ and ‘8 hours’ (quarterly) of guidance on the software libraries and applications included in an image environment. This is an example of a Community Enablement Service agreement where 2i2c is committing to offering bespoke guidance, up to a predefined limit, to achieve the shared outcome of the community being able to effectively use our Managed JupyterHub Service.

Business Development may also offer a certain number of “units of time” to achieve a certain shared outcome without explicitly collecting additional revenue. If a community needs assistance co-creating some resource or guidance on how to build their open source technology stack on top of the interactive cloud computing base already provided, Community Enablement Service could be priced as a ‘for free’ add on. A service contract could then provide an additional Community Enablement Service agreement for more collaborative activity with 1i2c team members under an agreed price for effort model. Ultimately, the price of the service should be driven by the value received by the community while ensuring that it covers 2i2c’s internal and opportunity cost to provide the service.