Suprdense Documentation
Visit websiteSign up or login
  • Welcome to Suprdense
  • Overview
    • What we do
  • Fundamentals
    • Getting set up with Suprdense
      • Workspaces
      • Members
      • Subscriptions
  • Products
    • Config
      • Getting Started with Config
      • Connecting Config to HubSpot
      • Imports
      • Implementations
      • Use cases
        • Bulk Create Properties
      • Library
      • Assets
        • Properties
      • Modules
      • Marketplace
    • Onboard
      • Getting Started with Onboard
      • Connecting Onboard to HubSpot
      • Onboarding
      • Assets
      • Modules
      • Library
      • Activity
    • Switch
      • Getting Started with Switch
      • Starting a Migration
      • Selecting your CRM
      • Mapping your Data
        • Mapping Users
        • Mapping Default Objects
        • Mapping Default Properties
        • Mapping Custom Objects
        • Mapping Custom Properties
        • Creating Custom Objects
        • Creating Custom Properties
        • Data Types
      • Associations
      • Records
      • What is a Sample Migration?
      • What is a Full Migration?
      • Status
Powered by GitBook
On this page
  • What is Config?
  • What does Config solve for?
  • Problem statement
  • How Config solves these pain points
  1. Products

Config

Learn about Config, our CRM implementation platform.

PreviousSubscriptionsNextGetting Started with Config

Last updated 6 months ago

What is Config?

Suprconfig is an acceleration platform for CRM implementation built specifically for HubSpot Solution Partners. Simply put, it allows users to import, manage, and deploy workflows, lists, forms, email templates, and any combination of these to and from HubSpot in seconds.

What does Config solve for?

Whenever a Solutions Partner works with a client for implementation (new or existing), there are certain processes and SOPs that they follow to execute certain tasks. A typical implementation includes:

  1. Discovery

  2. Implementation/Development/Building

  3. Training

Config solves for #2.

Problem statement

A large set of problems when implementing HubSpot can be fairly similar. Solution partners tend to solve these similar sets of problems day in and out, with only minimal differences. The logic of these problems remains the same.

For example, more often than not, companies need to route leads between their sales team. Routing can be based on different triggers, such as:

  1. Route all leads from New York to Salesperson X; or

  2. Route all leads from Industry Y to Salesperson Z

To achieve this, Solution Partners create workflows for routing leads in HubSpot.

The workflows include multiple nodes, where logics are defined to route leads including segmenting the leads and then assigning them to specific people based on their internal logic, or dynamic logics.

The process is largely the same every time a Solutions Partner has to create a lead routing workflow, including the logic. The only thing that changes is the users and the properties on the basis of a particular HubSpot account. The pressing issue here is that Solutions Partners create these workflows again and again, for every single client.

This has 3 pain points:

  1. They have to redo everything, things that they have done several times earlier.

  2. They have to test for quality and usability issues every time they build it again.

  3. They cannot keep their internal practices consistent as every time a different person (especially a new employee) creates it, it has chances of human-induced errors and even inconsistencies with their standard practices.

How Config solves these pain points

Once the user has created a workflow, list, form, and email template, Suprconfig makes sure they never have to start from scratch again. Time and effort spent on recreating these assets is reduced from hours to minutes or even seconds.

Config allow users to:

  1. Import all of these assets and store them in Suprconfig

  2. Manage their assets and get visibility into their existing practices

  3. Implement all these assets at the click of a button

Page cover image