Skip to main content
Quickstart
PRODUCTS · JUICE QUICKSTART

Start here.
Every step from first call
to launch, in one place.

Juice Quickstart is the first interaction our clients have with Juice: sales collateral, proposals, and product documentation, then contracting and configuration across the Use Case, Company, Contract, Branding, and Communications hubs. End-to-end client onboarding through to launch, on the same platform.

Talk to Sales→See the controls→

PROGRAM QUICKSTART
Meridian Mutual · P&C program
CONFIGURING
8% complete
IMPLEMENTATION PROJECT PLAN
01Discovery & Onboarding100%
02Configuration & Setup0%
03Legal & Compliance0%
04Brand & Operations0%

Phases fill as the hubs complete. No countdowns: your program launches when your team says so.

USE CASES HUBPICK A TEMPLATE
Pre-configured starting points, not blank pages.
COMPANY HUBDRAFT · 80%
Merchant application
COMPLETENESS80%
Business details, ownership, banking, documents. Then submit it where your team can see the status.
CONTRACTS HUBMNDA PENDING
1
Seven steps in order. The MNDA signs first, and the rest of the chain unlocks.
BRANDING HUBNOT STARTED
Juice ProJuice MobilePayments CenterReports
Logos, colors, and typography, configured once.
COMMUNICATIONS HUB3 TO REVIEW
Payment link emailClaim approved notificationDisclaimer footer
The messages payees actually receive, bundled for review in one place.
YOUR TEAM DECIDED
The use case, the application, the contract, the brand, the messages.
JUICE CARRIES
The review, the setup, and a record of all of it. Ready when your team is.

ILLUSTRATIVE SCENARIO · A REPRESENTATIVE PROGRAM MOVING THROUGH QUICKSTART

Where onboarding usually breaks

The deal is signed. Then the scavenger hunt starts.

Most payment programs do not stall on decisions. They stall on logistics: the right deck, the latest contract, the brand assets, the status.

01
Collateral lives in inboxes
The overview deck arrives as an attachment, the pricing PDF as a follow-up, and nobody is sure which version is current.
02
Proposals drift from the product
What sales promised and what actually gets configured are tracked in different places, by different people.
03
Contracts move one email at a time
MNDA, merchant application, MSA, SOW: sequential documents chasing signatures through a thread nobody can audit.
04
Branding happens twice
Logos and colors get collected for the card, then again for the portal, then again for the emails.
05
Status is a weekly call
Progress lives in someone's spreadsheet, so every stakeholder meeting starts with a recap instead of a decision.
No two programs configure alike

Onboarding is not one template

A workers' comp program and a premium collection program make different choices. The path has to bend without turning into custom work.

Incoming premium collection
Claim and benefit payouts
Provider co-payments
Partner commissions
Multi-party settlements
Card, bank, or check delivery
Approvals before release
API, batch, portal, or embedded
Consumer programs
Commercial programs
Multiple brands and entities
Your mix of all of it
The hubs

One platform, every step of onboarding

Quickstart runs the whole client journey: the welcome after the first call, through the configuration that decides how your program pays.

Welcome & resources

Sales collateral, proposals, pricing, and product documentation in one searchable library, next to your named Juice team and a direct message line. The first thing a new client sees, and the place they come back to.

Use Cases

Start from a pre-configured template: property & casualty payments, workers' comp claims, provider co-pays, commissions. Then set origination, geography, payee types, rails, and implementation method.

Company

The merchant application as a guided workflow: business details, ownership, banking, supporting documents. A completeness bar shows what is left, and the review status is visible instead of chased.

Contracts

Seven steps in order: MNDA, merchant application, MSA, SOW, pricing schedule, SLA, due diligence. Sign the MNDA and the chain unlocks. Every version and every signature stays on the record.

Branding

Logos, colors, and typography configured once and applied across Juice Pro, Juice Mobile, Payments Center, the claims and premiums portals, and reports. Your program looks like yours before it launches.

Communications

The messages payees actually receive: payment link emails and texts, reminders, approval and confirmation notices, disclaimer footers, support details. Reviewed as a bundle, not discovered after launch.

Built-in discipline

Onboarding with a record

The point of doing this in one platform is not just convenience. It is that every choice, submission, and review lands in the same place.

A real review loop

Everything you submit, from merchant application to brand package, comes back approved, rejected, or revision requested, with the reviewer and the notes attached.

Priority tasks

The dashboard names the next thing to do, in order, and links straight to the hub where you do it.

Overall progress

One percentage across contracts, branding, and communications. Anyone can answer where are we without scheduling a call.

Stage-based access

Welcome, onboarding, ongoing. Sections unlock as milestones complete, so nobody configures ahead of the paperwork.

Notifications, not archaeology

Approvals, revision requests, new resources, and messages arrive as notifications. The record does not live in an inbox.

A direct line

Built-in messaging with your Juice team on the same screen as the work, so questions attach to context.

Template libraries

Use cases, brands, communications, and contracts start from published templates: a working starting point instead of a blank page.

An activity trail

Views, downloads, and submissions leave a history. When procurement asks what was shared, the answer is a lookup.

What buyers ask

Straight answers before the first call

What does Juice Quickstart simplify?

It brings client configuration work into a structured path for branding, communications, use-case setup, and launch preparation. The point is less avoidable back-and-forth and an implementation record that is easy to follow: what was decided, what was submitted, and what is left.

How are responsibilities split during onboarding?

Your team provides the program decisions, content, data, approvals, and operating requirements it owns. Juice supports configuration, implementation guidance, product setup, and the operational handoffs defined for your program. The split is visible in the platform, not buried in a project plan.

What happens when our program needs deeper integration?

Quickstart connects to implementation discovery rather than assuming a fixed technical route. Some programs run on supported configuration; others need deeper integration across systems, data, branding, and reporting. The model bends around the workflow, and the trust and control questions get answered along the way.

Who owns what

Your team makes the calls. The platform keeps the record.

YOUR TEAM DECIDES
Program rules and use-case choices
Brand direction and content
Contract and legal review
The data and documents in your applications
Approval of what goes live
JUICE SUPPORTS
The structured configuration path
Template libraries and implementation guidance
Product setup across every surface
Submission review and operational handoffs
The implementation record, end to end

Quickstart organizes the work around your decisions. It does not make them for you.

Who feels it

When onboarding lives in one place, launch stops being a meeting series

01

Program owners

One number answers where are we, and the next task is already linked.

02

Legal and procurement

Every contract version, signature, and revision request in one chain, in order.

03

Marketing and brand

Your identity configured once, applied everywhere the program shows up.

04

Implementation teams

Decisions, submissions, and reviews attached to the work, not scattered across threads.

The first hello, through launch day.

If your last implementation lived in a shared drive and a weekly status call, come see what the same journey looks like when it is a product.