Join the Hint Marketplace

We pride ourselves on running a predictable launch cadence for Hint Marketplace partners. When we move forward with a partnership, our team stays engaged through go-live to guarantee a smooth rollout for mutual customers.

flowchart LR
    A[Intake<br/>Partner Application] --> B[Scoping<br/>Discovery Call]
    B --> C[Sandbox<br/>Access + Agreements]
    C --> D[Design<br/>Follow-ups]
    D --> E[Internal Testing<br/>+ Help Docs]
    E --> F[Beta Enablement]
    F --> G[GT-M Planning]
    G --> H[Production Launch<br/>+ InstantOn]
    classDef node fill:#ffffff,stroke:#3b82f6,stroke-width:1px,color:#0f172a,font-size:12px
    class A,B,C,D,E,F,G,H node

1. Getting started form

Complete the Partner Application Form with company details, integration scope, and at least one DPC practice referral. This unlocks the evaluation conversation and helps us prioritize enablement.

2. Initial scoping meeting

Once the form is approved we schedule a working session with your product and engineering leads.

• Align on partnership objectives and personas.
• Walk through Integration Best Practices.
• Whiteboard the end-to-end user experience so both teams understand the surface area.

📘

Shared customer

Identify at least one shared practice willing to run the beta. Their feedback keeps quality high and accelerates launch approvals.

3. Sandbox + agreements

Following commercial approval we countersign the Integration Partner Agreement and exchange sandbox access.

• Hint provisions your sandbox credentials (login, partner API key, example data).
• You provision a sandbox or staging tenant for Hint to test against.
• Start building immediately so we can unblock InstantOn certification sooner.

4. Integration and product follow-ups

Schedule deep dives as needed to validate data modeling, activation flows, and naming within your UI.

• Send technical questions to [email protected].
• Reach out when you are ready to begin beta testing in production.

📘

Demo video

Record a short walkthrough of the integration once it is feature complete. We use it internally for QA and may feature it on your Hint Partner Ecosystem listing (see Keragon's example).

5. Internal testing & help documentation

• Grant Hint access to a staging account or schedule a guided demo before any beta enablement.
• Show how practices discover, enable, and use the integration end-to-end.
• Collaboratively draft customer-facing documentation while testing is underway.

6. Beta testing & release management

• Hint enables the integration for each beta practice individually.

• Practices see the integration in the Hint UI under Integrations and click Integrate → Enable.

  

• The practice shares the generated authorization code with your team to finalize setup.

  

📘

Adding a beta practice

Email [email protected] with the practice name and admin contact if you need to add or remove beta sites. Hint enables each practice individually during beta.

We typically run beta programs for several weeks to collect meaningful feedback. The Hint partnerships team will reach out to practices directly; please keep us posted on major fixes so we can re-test promptly.

7. Partner launch & marketing plan

• Align on customer support content, go-to-market copy, and a Hint Partner Ecosystem page.
• Coordinate the marketing launch (webinar, newsletter, social, in-product placements).

8. Production enablement & InstantOn

• After beta feedback is addressed, we run one more end-to-end test and enable the integration for all practices.
• Launch communications go live across the Hint app and agreed marketing channels.
• Adopt InstantOn (via OAuth) as soon as possible for a fully self-serve activation experience.

📘

Why InstantOn matters

You can keep using authorization codes, but InstantOn eliminates manual credential exchange, scales better for practices, and dramatically improves Time-to-Value. Upgrade once beta is stable so every future practice can enable you in one click.