You are on page 1of 6

ISV MEMBER APPLICATION FORM

CONTACT DETAILS
Please fill in each response as completely and comprehensively as possible. After completion, please send the form to
info@machalliance.org.

Company Name Contact Name

Phone Number Email Address

C-Level Sponsor C-Level


Name + Title Sponsor Email

Website

Date

We would love you to join the MACH Alliance and become part of our global community.
Prior to welcoming you as a member there are a number of things that need to happen first.

1. A review of your company to ensure that it meets the MACH Criteria


2. A decision by your company as to what level of membership you are committing to
3. A marketing meeting to discuss contribution levels and activity

About the MACH Alliance and Membership


The MACH Alliance was formed in June 2020 to help enterprise organizations navigate the complex modern
technology landscape. It aims to guide and show the business advantage of open tech ecosystems that are
Microservices based, API-first, Cloud-native SaaS and Headless.

Our members have access to a global community of MACH vendors, SIs, Agencies and other organizations, pooling
resources to promote the MACH ecosystem, sharing knowledge and opening opportunities to collaborate.

Members are able to claim that they are MACH certified and can use the MACH trademark.
The Alliance offers multiple opportunities for members to get involved and drive the Alliance forward, from specific
councils that cover an area of activity (e.g. Marketing, Growth, Technology….) through to membership of the
Advisory Board or Executive Board depending on level.

The Alliance will organize events and attendance at conferences and exhibitions working with members to make the
most of joint marketing, but also supporting members to get the most out of these events.

Meeting the MACH Criteria


Joining the MACH Alliance is only possible on a company-wide basis. It is not possible to join as a country or region,
being part of a bigger group, or to join with a single software solution when your portfolio offers more than one
solution. All solutions you offer “as new” will be assessed from a technology and GTM perspective.

There are cases where a requirement is not applicable to your company or where there is an edge-case. We will
discuss this during the application process.

Membership Levels
The Alliance relies on contributions from members to thrive. These contributions are a mixture of content, time,
resource and financial support.
We have five Membership Levels; Startup, Standard, Enterprise, Enabler and Patron - a comparison is below:

Startup* Standard Enterprise Enabler Patron*


Small ISVs that ISVs and SIs that ISVs and SIs that Organizations that Companies that are not
offer MACH- offer MACH offer MACH are utilized by MACH MACH certified but
based product products or products or organizations to want to support
services services deliver a MACH Cannot be “failed”
< 35 employees
service; therefore, standard/enterprise
> 35 employees enabling a MACH candidates
provider Visa, PayPal, Google,
government bodies,
academics, analyst
Open To firms, etc.
Able to claim No -Will have an
MACH certification Yes Yes Yes Enabler Logo No

Use of MACH Yes - Will have an Yes – but make it clear


trademark Yes Yes Yes Enabler Logo they’re a “patron”
Access to council
seats No 1 seat 2 seats 1 seat No
Advisory board
seat No No Yes If > $100k If > $100k
Alliance-
sponsored assets 1 webinar 2 webinars
(but driven by 1 white paper 1 white paper
member) None 1 blog post 2 blog posts Varies Varies
Shared exhibition
activity By invitation By invitation Yes Varies Yes

Annual Varies Varies Varies


membership fee (target > $10k) $25k-$50** $50k-$75** (target > $100k) (target > $100k)
* By invitation only
** Depending on company size (number of employees)

In addition to ISVs and SIs, the Alliance accepts “Enablers” members. These can be companies that in some form
‘enable’ the creation of composable architectures through their solution(s). Explicit board approval is required.
Patrons and enablers do not get executive board seats
QUESTIONNAIRE RESPONSE
Please describe how you meet the following requirements/criteria by considering all solutions and packages that you
currently sell as new and fill in each response as completely and comprehensively as possible or this could lead to a
delay in your application being processed. After completion, please send the form to info@machalliance.org.

At least three different microservices that each have


their own domain (please name them)

Each with their own datastore

Applications communicate with events or through API


calls

Able to release each application independently

Only means of accessing functionality is through APIs.


Must have 100% API coverage

Customer-facing APIs must be REST and/ or


GraphQL

Internally, APIs built first. Then implementation


happens

Multi-tenant native SaaS (single instance of


application can service many different users)

No platform upgrades that customers have to apply


(hands-free/transparent to customers). Your product
isn’t versioned.

Live projects with at least 2 other MACH ISV member


companies. Please describe which other ISVs are part
of that project and name the customers.

Share an example of a recent MACH campaign/


content piece conducted by your organization (share
link to website, landing page or campaign)

Your entire company product(s) offering/ portfolio is


100% MACH compliant.

Three public enterprise MACH references (customers


willing to speak publicly about their use of a member's
product or service).
Please provide name and title information to enable timely
processing of the application. References will be contacted
only if the application has been successfully processed.
> 5 customers, each generating more than $100M in
annual revenue using MACH compliant product(s)

> 50 employees

Ambassador
 
As part of the onboarding process, new members are expected to put forward a potential Ambassador. An
Ambassador is a CUSTOMER contact who has actively been involved in creating a MACH Architecture for his
or her company. Example roles for a MACH Ambassador are but are not limited to CTO, Head of IT, Head of
Commerce, CMO, Product Manager, Head of Engineering, Head of Digital, CDO. 
An Ambassador commits to: 
● Writing at least one piece of content for MACH Alliance per year - blog post, white paper or a case
study, etc, that both you and the MACH Alliance will promote in our networks
● Participating in at least one MACH Alliance webinar, podcast or physical event per year
● Generating, distributing and promoting the MACH Alliance philosophy and the content of your liking
● Offering availability on an as needed basis to act as a sounding board for various council discussions 
● Attending an annual general meeting
● Agreeing to publish name, photo, and bio on digital and print materials of the MACH Alliance
 
After ISV is onboarded to the MACH Alliance, the potential Ambassador will be reviewed by the MACH
Alliance following the standard process.

Ambassador information

Name
Job Title
Company

C-Level Sponsorship
New members need an internal (C-Level) sponsor for this application, please state the name and Job Title of the Internal Sponsor here:

Name

Job Title

Members must feature the MACH Logo on their main company website.

Additional information
Additional Terms

The following is an example of the non-technical aspects that the Growth Council and Executive Board will
assess on a membership application where an ISV has legacy product or is moving to a MACH architecture:

● All products currently offered for sale must be MACH


○ "Controlled availability" or some other "gate" for selling non-MACH products isn't strong
enough. The product cannot be offered for sale anymore.
○ Non-MACH product is not on current price lists
○ Customers running non-MACH product can buy additional CPUs/capacity of existing product
but not a net new non-MACH product
■ If a customer signs a global contract with the vendor, the customer is able to roll out
the non-MACH product to other countries, lines of business, etc but only under that
contract. Not a new contract.
○ 100% of new license revenue in the past 6 months can only be from MACH-based product
■ Excludes additional CPUs/capacity from existing customers
○ Minimum of $5m/ARR in past 6 months from MACH-based product

● Non-MACH products cannot be marketed


○ No public customer references from non-MACH products
○ No case studies or anything from non-MACH products
○ The features listed on their website, feature guides, etc must all be from MACH products

● Last analyst evaluation from Gartner or Forrester must have been of MACH product(s) only

● Documentation and other technical collateral in support of existing legacy non-MACH products may
still be there but nothing in terms of thought leadership on the non-MACH product
○ Non-MACH product may still be supported

● Cannot be doing feature releases of non-MACH product


○ Can offer bug/security releases of non-MACH product

● Per Growth Council discretion, revenue figures must be signed off on by CPA

● Membership Approval after passing Technology Council assessment is subject to Growth Council and
Executive Board approval

● Members must feature the MACH Logo on their main company website

● As part of the onboarding process, new members are able to put forward a potential ambassador. An
Ambassador is a customer (ISV or SI) contact who has actively been involved in creating a MACH
architecture for his or her company. Example roles for a MACH Ambassador are, but are not limited
to: CTO, Head of IT, Head of Commerce, CMO, Product Manager, Head of Engineering, Head of
Digital, CDO. An Ambassador commits to: 
○ Writing at least one piece of content for MACH Alliance per year - blog post, white paper or a
case study, etc, that both you and the MACH Alliance will promote in our networks
○ Participating in at least one MACH Alliance webinar or physical event per year
○ Generating, distributing and promoting the MACH Alliance philosophy and the content of your
liking
○ Offering availability on an as needed basis to act as a sounding board for various council
discussions 
○ Attending an annual general meeting
○ Agreeing to publish name, photo, and bio on digital and print materials of the MACH Alliance

You might also like