guide
  • Introduction
  • Guiding Principles
    • Mission Statement
    • Conflict Resolution Process
  • Operating Model
    • Working Together
    • Holacracy
      • Meetings
      • Specific Roles
      • Terms and Definitions
      • Finer Points
      • Holacracy-Asana Key
    • Getting Things Done
      • Daily, Weekly, Monthly, and Annual Reviews
      • GTD-Asana Key
    • Transparency
    • Language
    • Budgeting
    • By Department
      • Engineering Operations
  • General Guidelines
  • Employment Policies
    • Equal Opportunity Employment
    • At-Will Employment
    • Code of Conduct in the Community
    • Complaint Policy
    • Drug and Alcohol Policy
    • Vacation, Holiday, and Paid Time Off (PTO) Policy
    • Supplemental Policies for Remote Employees and Contractors
    • Supplemental Policy for Bonus, Commissions, and other Performance-based Payments
    • Supplemental Policies for Hourly International Contractors or Workers
    • Supplemental Policies for Hourly International Contractors or Workers
    • Disputes and Arbitration
  • Benefits and Perks
    • Health Care
    • Vacation, Holiday and Paid Time Off (PTO) Policy
    • Holiday List
  • Hiring Documents
    • Acknowledgement of Receipt
    • Partner Proprietary Information and Inventions Agreement
  • Engineering Wiki
    • Code Snippets
      • Front End Code Snippets
    • Setup
      • 1: Overview of development using Audienti
      • 2: How to setup your dev environment on Docker
      • 2a: Setting up on our cloud your dev server
      • 3: Connect to Production using the VPN
      • 4: Import data into your development environment
    • Deployment
      • Docker based deployment of back end (manual)
    • Culture
      • How our development team works
      • Code Best Practices
    • Tips
      • Setting up a new development machine
      • Importing data to Development environment
      • GIT workflow and work tracking
      • Using Slack
      • Using Rubocop
      • Our Code Standards
      • General suggested best practices
      • Tracking your time
      • Naming Iterations
    • Migrations
      • Postgres
      • ElasticSearch
      • Redis
    • Database and System Maintenance
      • Redis Howtos
      • Elasticsearch HowTos
      • Postgres HowTos
      • Administration recipes
      • App maintenance crash course notes
    • Front End
      • 2016 Plan
      • Deploy
      • Assets
      • SearchLogic
      • How to create UI components
      • OMA Standard Tables
    • Monitoring and Alerting
      • Monitoring Systems
      • Monitoring individual controller actions
      • Get notified when a metric reaches a certain threshold
      • Instrumenting your models using Oma Stats
      • Configuring Graphite Charts
      • Tracking your results with StatsD
      • Logging Fields
      • Updating Kibana Filtering
    • Testing
      • Coverage
      • Elasticsearch mapping config synchronization
      • Testing Gotchas
      • Rspec Preloader
      • Test Best Practices
    • Models
      • Backlinks
    • Queueing and Worker System
      • Queueing and Job Overview
    • Processors
      • Rebuilding Spot Instances
      • Deploying processors
      • Running processors in development
      • Reverting to the previous build on a failed deployment
    • Processors / Opportunity Pipeline
      • Opportunity Pipeline
      • Diagram
    • Processors / Enrichment Pipeline
      • Diagram
      • Clustering
    • Processors / Backlink Pipeline
      • Diagram
      • Backlink Pipeline external APIs
      • Backlink pipeline logic
    • Processors / Automation Pipeline
      • Diagram
      • Automation Pipeline Overview
      • Agents
      • Running in development
    • Messaging and Social Accounts
      • Overview
    • API
      • Audienti API
    • Algorithms
    • Troubleshooting
      • Elasticsearch
    • Big Data Pipeline Stuff
      • Spark
    • Our Product
      • Feature synopsis of our product
    • Research
      • Backend framework comparison
      • Internet marketing Saas companies
    • Code snippets
      • Commonly Used
      • Not Used
    • Miscellaneous
      • Proxies and Bax
    • Legacy & Deprecated
      • Search criteria component
      • Classes list
      • Target Timeline
      • Twitter processor
      • Asset compilation
      • Test related information
      • Interface to EMR Hadoop jobs
      • Mongo Dex Indexes to be Built
      • Mongodb errors
      • Opportunity pipeline scoring
      • Graph Page
      • Lead scoring
      • Insights
      • Shard keys
      • Setting up OMA on local
      • Clone project to local machine
      • Getting around our servers in AWS
  • Acknowledgements
  • Documents That Receiving Your First Payment Triggers Acknowledgement and Acceptanace
Powered by GitBook
On this page
  1. Employment Policies

Supplemental Policy for Bonus, Commissions, and other Performance-based Payments

For partners that have a performance-component to their payments made by OMAlab, the following policies apply.

All payment are based on performance of an established metric, documented in a Management by Objective Plan ("MBO Plan" or "MBOs") or Sales Commission Plan ("Sales Plan") that specifically defines the metrics of these payments.

Any jointly executed MBO, Sales Plan, Commission Plan, or other agreement is to be considered in all cases a guideline for payment. In all cases, any and all payments of any bonus or commisions are absoutely at the discretion of the CEO.

With or without a Sales Plan, if the commissions produced from your sales on a monthly basis do not surpass your base salary, you will not be entitled to a commission payment(s).

If the Monthly Recurring Revenue (MRR) from your sales is less than your Monthly Salary (MS), then no commissions will be due and payable to you.

Any draws that are defined, even stated in your offer letter, are payable (or not payable) at the discretion of the CEO.

For Sales Plans, OMAlab pays commission payments based on sales recognized payments received from the customer and paid in full as revenue, and only on final, collected sales.

Most Sales Plans calculate commission only on ANNUAL Recurring Revenue, based on a committed, non-cancellable annual agreement executed by the customer, selling software or software-as-a-service products. If your sale includes terms that are shorter than an ANNUAL commitment by the customer, the company has the right to pay reduced commissions or withhold commissions for these payments until the customer reaches their 13th month (12 months completed and paid) for commissions to be paid and due.

If the sales deal includes other types of revenue, such as support, consulting, web development, or other service types with a different Cost of Goods Sold, then commission payments for these types of deals, and these revenue components are at the discretion of the CEO.

OMAlab will make payments within one pay period of receipt of funds by the customer/client, in the case of Commission payments that are recognized as commissionable.

All commission payments (or lack of payment for commission) will be considered final after 30 days. No changes to payouts in favor of the partner can be made after 30 days. The company reserves the right to make changes in the company favor for errors, omissions, and other items at any point the incorrect payment is recognized, up to three (3) years.

PreviousSupplemental Policies for Remote Employees and ContractorsNextSupplemental Policies for Hourly International Contractors or Workers

Last updated 7 years ago