Key Concepts You’ll See in OnRamp
Last updated: December 30, 2025
Welcome to the OnRamp language session — but don’t worry, this isn’t tech jargon in disguise. These are the words and ideas that make this product actually make sense when you’re using it day to day.
🚀 Projects & Playbooks
In OnRamp, a Project is a structured, trackable way to guide a customer through a process — like onboarding, implementation, or rollout.
A Playbook is your reusable blueprint for how that process should run. It defines the tasks, structure, and expectations so you don’t have to reinvent the wheel for every customer.
Think of it this way:
Playbooks define how work should happen
Projects are live instances of that work for a specific customer
📋 Tasks & Subtasks
Projects are made up of Tasks — the individual pieces of work that move things forward.
Tasks can include Subtasks to break work down into smaller, more manageable steps.
Together, they help teams stay aligned on:
What needs to happen
Who owns it
What’s done (and what’s not)
No guessing. No digging through threads.
⚙ Administration & Configuration
This is where you control how OnRamp behaves across your organization.
Administration and configuration include things like:
Workspace and project settings
User roles and permissions
Defaults and templates
Portal behavior and access
If OnRamp is going to fit your way of working, this is where you make that happen.
🔌 Integrations & Automation
OnRamp connects with the tools you already use — especially your CRM — so your processes stay in sync without manual effort.
Integrations keep data flowing.
Automation ensures the right work starts at the right time.
Less copying. Fewer mistakes. More consistency.
🔄 Workflows vs Projects (This One’s Important)
These two are closely related — but they’re not the same thing.
Projects
A Project is the actual work being done for a customer, created using a Playbook and tracked over time.
Projects are where tasks live.
Projects are what teams and customers interact with day to day.
Workflows
A Workflow is an automation tool that controls when and how Projects get created.
Workflows guide you through:
Defining triggers
Configuring when OnRamp should create a Project
Selecting the Playbook to use
Applying rules and settings for how that Project should be created
In simple terms:
Workflows listen for events
Those events tell OnRamp to create Projects
Projects do the actual work
The relationship, simplified
A Playbook defines the structure
A Workflow decides when that structure should be used
A Project is the real, live result
Once set up, Workflows help ensure every customer starts with the right Project — automatically and consistently.
🧩 Customer Portal
OnRamp includes a customer-facing portal — a shared space where customers can:
See what’s happening
Know what’s coming next
Complete tasks or provide information
Track progress without chasing updates
It’s transparency by default — and customers tend to love that.
🆘 Support
Support is your go-to place when you need help or something doesn’t look right.
Here you’ll find:
Answers to common questions
Troubleshooting guides
Known issues and quick fixes
It’s designed to help you get unstuck fast — and know when it’s time to reach out.
📊 Reporting & Insights
OnRamp gives you visibility into how work is progressing across customers and playbooks.
You can see:
Project progress
Bottlenecks and delays
Completion trends
How well playbooks are performing over time
This is where execution turns into insight.
✔ One last thing to remember
You don’t need to learn all of this at once.
Most teams start by:
Creating a Playbook
Running a few Projects manually
Adding Workflows to automate creation
Expanding with integrations and reporting
OnRamp is designed to grow with you — not overwhelm you.
What’s next?
Now that the concepts feel familiar, you can:
👉 Set up your first Playbook
👉 Create or automate your first Project
👉 Explore Workflows to scale your process
👉 Head to Support if you get stuck
You’ve got the language down.
Now let’s put it to work.