Skip to content
This repository has been archived by the owner on Apr 17, 2024. It is now read-only.

Commit

Permalink
Feature/gen 297 (#63)
Browse files Browse the repository at this point in the history
* fix: update modules

* feat: explain sales and post targets for 2024

* fix: wording
  • Loading branch information
dave-at-koor authored Jan 26, 2024
1 parent 3a1aa59 commit bcd4c77
Show file tree
Hide file tree
Showing 5 changed files with 388 additions and 263 deletions.
3 changes: 3 additions & 0 deletions docs/.vitepress/config.ts
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,9 @@ export default withMermaid(
{
text: 'Sales',
link: '/sales/',
items: [
{ text: '2024 Targets', link: '/sales/targets-2024' },
]
},
{
text: 'Security',
Expand Down
67 changes: 65 additions & 2 deletions docs/sales/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,69 @@ title: Sales

The only way Koor will stay in business is to generate enough revenue to cover our costs and fuel our growth. That's what sales is all about.

Our sales strategy is simple. Offer customers data storage using Ceph plus whatever additional software helps us manage the service at scale. Each customer gets their own storage cluster, and we take care of it for them.
## Strategy

More to come...
Our sales strategy is simple. Offer customers data storage using Ceph, plus whatever additional software helps us manage the service at desired scale. Each customer gets their own storage cluster(s), whether we use their infrastructure or provision cloud resources on their behalf. Then we take care of it for them.

## What We Sell

Our primary product offering is **Managed Ceph**. That includes anything to do with setting up and maintaining storage. The basic offering is to handle set-up and maintenance of Ceph clusters on behalf of our customers. We do this for a fixed, per month price, procured on an annual basis.

### Service levels

There are other service levels depending on the scale of the customer and how much help they need. Going bigger, we can do Managed Ceph at an **enterprise level**. That might include additional services that increase the price, and volume discounts that lower the overall price. We will scale up to match the needs of customers with lots of data storage (50+ nodes).

On the other end, we can do discrete **one-off services**. We might do a system assessment on an existing cluster and make recommendations. We might troubleshoot a performance issue and suggest a plan to improve. For these types of services, our price will be based on an hourly rate and estimate of the hours it will take.

This piecemeal work might be "off of the menu," so to speak, something we work out when the customer "just needs a little help." We would prefer an annual agreement, but might see this as a step toward a long-term engagement.

We will also do extra projects that go above and beyond. Examples of such projects and higher service levels include:

- 24/7 emergency response SLAs.
- Data migration where we set up and manage the move.
- Disaster recovery planning, practice drills, and actual recovery from data loss due to circumstances outside of normal Ceph operation
- The normal problems, like disc failures, are handled under **Managed Ceph**. These problems should not be disastrous because we are doing preventative maintenance.
- Additional security and compliance work.
- Other requests as needed...

We would either charge extra for these types of projects or include them as part of an enterprise deal.

### Hosting considerations

When we provision infrastructure for the customer, we will either change the customer a monthly *usage* fee or make that part of the overall price. As long as Koor is not set up to lose money, either can work.

For instance, we are planning to offer a "starter cluster" for customers who want to try Ceph without having to go through the learning curve. That service may be offered as a free trial, leading to a subscription when the trial period is over. Since the cluster will be a fixed size, we can factor the cost into our pricing.

If a customer has a larger operation, we might want to use a usage fee to pass along the cost, on top of our standard rates for Managed Ceph.

## How Customers Buy

There are a couple of simple steps to become a Koor customer.

1. Agree to our [Terms of Use](https://about.koor.tech/terms-of-use). These are found on the website and are part of every contract.
2. Sign a contract for an annual subscription for the product or service we are offering.
1. The contract may include a scope of work to account for any specific requests by the customer.
2. The contract will specify the number of nodes being licensed or cared for by Koor.
- Nodes are a reasonable proxy of the scale of data storage, regardless of how much actual and usable storage is available.
- Customers may have one or more clusters, each with 4 or more nodes. We have a 4-node minimum per cluster for production. Anything less is fine for non-production uses. Koor only charges for production systems.
3. Payment is typically due immediately with a net 30 grace period.
1. We take payment via Stripe and Bill. We can also take direct deposit (ACH), which saves on fees.
2. Other arrangements - such as an installment plan - are possible, especially for larger scale operations. Details should be discussed when the contract is executed.

Once we have a signed contract, work will begin. If payment is not made by the due date, work may be suspended until that is sorted out.

We have a contract template in our private, shared folder on a Google drive. Ask Dave if you need access.

## Sales Targets

See our [Sales Targets for 2024](targets-2024).

## Industry Targets

We are open to any industry. There are some that seem to use a lot of data and gravitate towards open source solutions.

- Research institutions and labs
- Robotics and automation
- AI / ML
- Entertainment
- Communications
50 changes: 50 additions & 0 deletions docs/sales/targets-2024.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
title: Sales Target from 2024
---

# 2024 Sales Targets

Our sales targets flow from our [company goals](../company/goals/annual2024).

> **Grow annual revenue to $1MM**
> **Aquire 100 new customers, including 10 enterprise customers**
The first target is about the amount of revenue we generate.

The second is about the diversity of customers we want in order to have a healthy balance of interests. We prefer to have a variety of customers in different industries and data usage profiles.

If we achieve the revenue goal with only a few large customers, that would be acceptable. If we close that many customers, we are likely to surpass the revenue goal, too, as long as our pricing structure holds up. Discounts for enterprise customers (i.e., those with 50+ nodes) are built into the revenue model.

The point of reaching these numbers is survival. We need to have enough business to prove our value in the marketplace and to raise funds for rapid company growth.

## Q1 Targets

We will revisit and adjust these targets on a quarterly basis.

For the first quarter of 2024, our targets are chosen to help sustain our business and to begin to find momentum in the market.

1. Sell $100,000 in Managed Ceph
2. Acquire 1 enterprise-scale customer (50+ nodes)

Ideally, we will close a few smaller-scale customers in addition to the one enterprise scale customer.

## Q2 Targets

1. Sell $200,000 in Managed Ceph
2. Acquire 1 enterprise-scale customer (50+ nodes)

This would be a healthy ramp and buy us more time to close funding.

## Q3 Target

1. Sell $300,000 in Managed Ceph
2. Acquire 3 enterprise-scale customers

Continue to ramp toward annual goals.

## Q4 Target

1. Sell $400,000 in Managed Ceph
2. Acquire 5 enterprise-scale customers

Growth to close the year and launch into 2025.
Loading

0 comments on commit bcd4c77

Please sign in to comment.