Integration Timeline

Understand how long it takes to list and sell through the cloud marketplaces with Fours, based on which cloud providers and Fours products you use.

Overview

The integration timeline to list and sell using the Fours console depends on two key factors: the cloud provider and the Fours products you use. This page walks through both factors and how they affect the time to get up and running on the Fours platform.

For the prerequisites you’ll need to complete before you start, see Marketplace Listing Requirements.

The timelines below are not cumulative — most tasks can be completed concurrently.

Timelines by Cloud Provider

AWS

Net new product listing (approx. 3 weeks)

To list and sell a new product on AWS using Fours:

  1. Create product listing details — Fours uses templates to speed this up; time-box it to about an hour.
  2. Integrate Fours with your AWS Marketplace account (AWS Marketplace Management Portal) — about 20 minutes with an AWS admin.
  3. Submit for review — about 2 weeks with AWS.

The work required from you as the project owner is roughly 2 hours. The rest is handled by the Fours and AWS teams, who test the product and make sure it goes live.

Listing migration (approx. 5 days)

To list and sell an existing AWS product using Fours:

  1. Integrate Fours with your AWS Marketplace account (AWS Marketplace Management Portal) — about 20 minutes with an AWS admin.
  2. Update fulfillment URLs — about 3 days with AWS review.

Azure

Net new product listing (approx. 3 weeks)

To list and sell a new product on Azure using Fours:

  1. Create product listing details — Fours uses templates to speed this up; time-box it to about an hour.
  2. Integrate Fours with your Azure Marketplace account (Azure Partner Center) — about 20 minutes with an Azure admin.
  3. Submit for review — about 2 weeks with Azure.

The work required from you as the project owner is roughly 2 hours. The rest is handled by the Fours and Azure teams, who test the product and make sure it goes live.

Listing migration (approx. 5 days)

To list and sell an existing Azure product using Fours:

  1. Integrate Fours with your Azure Marketplace account (Azure Partner Center) — about 20 minutes with an Azure admin.
  2. Update fulfillment URLs — about 3 days with Azure review.

GCP

Net new product listing (approx. 4 weeks)

To list and sell a new product on GCP using Fours:

  1. Create product listing details — Fours uses templates to speed this up; time-box it to about an hour.
  2. Integrate Fours with your GCP Marketplace account (GCP Producer Portal) — about 20 minutes with a GCP admin.
  3. Submit for review — about 3 weeks with GCP.

The work required from you as the project owner is roughly 2 hours. The rest is handled by the Fours and GCP teams, who test the product and make sure it goes live.

Listing migration (approx. 5 days)

To list and sell an existing GCP product using Fours:

  1. Integrate Fours with your GCP Marketplace account (GCP Producer Portal) — about 20 minutes with a GCP admin.
  2. Update fulfillment URLs — about 3 days with GCP review.

Timelines by Product

Salesforce Connector (approx. 1 hour)

Connecting Fours to your Salesforce instance lets your team send private offers and share opportunities directly from Salesforce. You can also field-map all relevant Salesforce fields to private offer and co-sell fields, so you don’t have to fill in the details for sending private offers or sharing opportunities with cloud providers.

  • Install the Fours Salesforce app from AppExchange and connect it to Fours — about 10 minutes for a Salesforce admin.
  • Add the pre-packaged widget to the opportunity object — about 5 minutes for a Salesforce admin.
  • Map relevant fields for private offer and/or co-sell creation, then test — about 45 minutes for a Salesforce admin, sales ops, or alliances lead.

HubSpot Connector (approx. 10 minutes)

Connecting to HubSpot lets you use Fours’ co-sell capabilities from the Fours console. You’ll need a HubSpot admin, and setup should take about 10 minutes.

  • Create a new dedicated HubSpot user with the required permissions — about 5 minutes.
  • Connect the Fours console to the new HubSpot user — about 5 minutes.

AWS APN for AWS Co-Sell (approx. 30 minutes)

Connecting to AWS APN for co-selling requires your alliance lead and an AWS admin.

  • Create IAM roles with an AWS admin — about 15 minutes.
  • Complete the CRM connector request in APN and connect APN to the Fours console — about 15 minutes.

Who and What You’ll Need

  • Project owner — likely the person reading this page.
  • Marketplace admin — often in the IT department at larger companies.
  • Product listing content creator — usually your alliances team or marketing department.
  • CRM admin — helps integrate Fours into your CRM if you’re sending private offers from your CRM or co-selling.
  • Sales enablement date — mark a date on the calendar to enable your sales team on what a cloud marketplace is, and on co-selling if applicable.

Sample Timeline

The scenario: You want to get a new listing up on Azure but already have a listing on AWS. You’d like to use Fours to send private offers and share opportunities with AWS through Salesforce. How long will this take?

The plan: The AWS listing can be migrated in about one week. The Azure listing takes about 3 weeks. Setting up co-sell on Salesforce, with the ability to send private offers, takes about one week. Because all of this can be done in parallel, the total time to be fully set up on Fours is about 3 weeks.

Get Help

By following these timelines and using the Fours Console, you can streamline listing and selling your products across cloud marketplaces. If you have questions or need help, reach out to our sales or support team at [email protected].

Spotted something wrong or out of date on this page? Tell us and we'll correct it.