Challenge

As Unify grew, the team discovered that their workflow of sending demo requests directly to Slack wasn't sustainable. What had worked for handling a few leads per week was now creating a revenue bottleneck, with the team spending hours weekly on researching, qualifying, and reaching out to inbound leads.

With just one sales rep and a founder handling sales, the inefficient routing system was already causing problems. Unify knew they needed a solution before expanding their sales team. Though the growth team created a temporary fix using a Webflow form, Calendly scheduling, and numerous Zapier automations syncing to Salesforce, it wasn't enough.

As the growth team began managing account ownership for meeting scheduling and routing, they realized they needed a more scalable solution—especially with an upcoming fundraising announcement. This is when Default stepped in.

‍

{{testimonial-1}}

‍

Solution

Use case #1: Automating inbound scheduling & routing

Unify's first major win was automating inbound with fast scheduling, accurate routing, real-time enrichment, and proper CRM data hygiene. Default captured inbound pipeline that Unify's team generated and provided a much easier way to own any routing or scheduling logic changes without managing multiple solutions.

{{testimonial-2}}

‍

Default built for Unify this workflow:

• Upon form submission, a lead is enriched, qualified, and routed to the right queue
• Default checks for existing accounts in Salesforce, then updates or creates a new one
• In just a few seconds after form submission, Default displays the right rep's calendar
• After the meeting is booked, Default creates an opportunity in Salesforce and notifies a rep on Slack
• If the meeting is not booked, Default triggers an Unify follow-up sequence

‍

Use case #2: Outbound scheduling CRM automation

After automating Unify's inbound funnel, the Default team built out additional workflows to support their outbound efforts. As reps started to book more outbound demos, routing, assignments, enrichment, and CRM data hygiene took too much of the sales teams' time.

{{testimonial-3}}

‍

Here is how Unify automated outbound scheduling:

• Once prospects schedule a time using the Default scheduling link, Default checks for an existing account
• If an existing account is found, Default updates the record with up-to-date enrichment data and rep's name
• If there is no account found, Default creates a new one based on the prospect's email and enrichment information
• Each meeting is then reflected as a Salesforce event, and a new outbound opportunity

‍

Results

Thanks to Default, Unify was able to build a scalable inbound and outbound scheduling infrastructure that helped them capitalize on a massive fundraising announcement. During the weeks following the Series A announcement, Unify scheduled and routed over 500 inbound opportunities, generating over $7M in pipeline.

By implementing a proper inbound infrastructure well ahead of the announcement, Unify was able to increase their inbound conversion rates and prepare for the most successful outcomes of marketing activity without worrying about misrouted leads, poor scheduling systems, and lack of CRM data hygiene.

Challenge

After raising their Series B, Quo (formally OpenPhone) experienced a surge in demand across all customer segments. Both individual users and large enterprises went through the same inbound process, leading to slow response times and major inefficiencies for the sales team.

The team routed all leads—whether seeking to create an account or talk to sales—directly into Salesforce. Soon their CRM became cluttered with a mix of qualified prospects and junk leads.

To address this inbound routing and scheduling challenge, Mak Reed, Quo's Senior RevOps Manager, implemented Chili Piper. While it initially helped convert "talk-to-sales" leads into meetings, the solution proved too inflexible for Quo's go-to-market strategy.

The implementation left them with a fragmented workflow split between Chili Piper, Salesforce, Zapier, and extensive custom code—yet the core problem remained. Quo's RevOps team needed engineering support for even basic routing changes. That's when Default stepped in.

{{testimonial-1}}

Solution

Use case #1: Automating inbound scheduling of high intent leads

OpenPhone's first major win came from consolidating their inbound scheduling and routing logic into a single workflow canvas. Default's team rebuilt Quo's workflow while providing RevOps support and regular Slack updates.

With real-time enrichment, Quo eliminated both custom code and unnecessary Salesforce admin work. The built-in enrichment also improved their CRM data quality.

Now, Quo's inbound workflow looks like this:

• Upon form submission, a lead is enriched, qualified, and routed to the right queue
• Default checks against leads, contacts, and accounts in Salesforce
• Default updates found records or creates new ones using enrichment and the round-robin to determine the record owner
• In just a few seconds after a form submission, Default displays the right rep’s calendar
• After the meeting is booked, Default creates an event in Salesforce and notifies a rep on Slack
• If the meeting is not booked, Default triggers an Outreach follow-up sequence

‍

{{testimonial-2}}

‍

Use case #2: Routing self-serve signups to product specialists

With both sales-led and product-led approaches, Quo needed precise lead qualification. Default enabled the team to convert free-plan signups into qualified opportunities by properly qualifying and routing them to product specialists, significantly increasing product-led pipeline generation.

Here is how Quo leveraged Default to route signups?

• After a new form submission, check if the lead qualifies for a demo or if it should be sent to a product self-serve flow
• If the lead was prompted to sign up, Default checks against all CRM records looking for a match
• If a lead, contact, or account was found, an owner was immediately notified on Slack
• If this was a new signup, a new lead object would be created and round-robined across product specialists working in the lead's region

‍

{{testimonial-3}}

‍

Conclusion

By integrating Default into their revenue and marketing processes, Quo significantly improved the efficiency and effectiveness of their inbound operations. Default helped regain control over displaced tooling while contributing to decreased speed-to-lead and improved inbound conversion rates.

Speed-to-lead went down from 2.5 days to less than a couple of hours, proving a 67% performance improvement. Default scheduler allowed Quo to increase inbound conversion rates by 17% while spending 5x less time on fixing queues and misrouted leads in Salesforce.

Challenge

As Runway started to gain more demand from CFOs and finance leaders, the initial inbound funnel consisted of the HubSpot form and a few repeatedly breaking Zapier workflows. When Brandon Penn, the Head of Marketing, joined, he knew he needed to increase the efficiency of GTM operations as inbound was driving over 70% of pipeline.

Reps wasted time chasing leads, updating HubSpot, and requiring constant workflow troubleshooting. As Runway started scaling marketing efforts and planned to triple its sales team size, they needed a solution that would help them regain operational control and allow qualified leads to schedule a meeting with a queue of AEs.

The marketing team explored relying on HubSpot's built-in scheduling and workflow functionality but was blocked by a lack of customization and complex routing logic based on contact ownership or enrichment. Runway found themselves in a situation where they needed to hire HubSpot experts just to help manage inbound operations. This is where Default step in.

‍

{{testimonial-1}}

‍

Solution

Use case #1: Automated inbound scheduling

Within 24 hours of adopting Default, Runway created their first workflow and retired HubSpot scheduling—thanks to Default's implementation team and ongoing Slack support.

Default’s scheduling and routing allowed the Runway team to build complex routing logic, improve scheduler speed, and book more inbound meetings from demo requests. All within days of getting started on Default.

Now, Runway’s workflow looks like this:

• After a demo submission, Default enriches with Clearbit and ChatGPT to gather additional financial information about the lead’s company
• Default then qualified and looked for existing contact in HubSpot
• If the contact was owned by a rep, their calendar would pop in 1/10 of a second
• If the contact was new, the workflow would round-robin the lead and show the next person’s calendar
• After the meeting was scheduled, Default would notify the rep on Slack, create a HubSpot meeting, and create a task for a rep to review AI sales research
• If the meeting was not booked, Default would trigger an automated Outreach follow-up sequence to convert a lead into pipeline

‍

{{testimonial-2}}

‍

Use case #2: Event & webinar pipeline automation

After successfully tripling inbound lead volume with Default, Runway built another workflow that would 10x pipeline generation from events and webinars. As Runway’s marketing team scaled event effort, they needed a way to route, distribute, assign, and convert leads into demos on reps’ calendars.

Runway leveraged Default to automate lead follow-up after a new contact was added to HubSpot from an event or webinar to then enroll into custom event-specific sequences and create engagements to improve ROI tracking of each offline marketing activity.

Here is what Runway has built:

• After a contact was added from an event, Default would see if there has been any recent activity
• If the contact hasn’t been engaged, Default would route to a rep, enroll into a sequence
• If the contact had a recent engagement, Default would alter the contact owner with a customer Slack, including the necessary context for a personalized follow-up

‍

{{testimonial-3}}

‍

Results

By implementing Default, Runway was able to efficiently scale their go-to-market motion, triple the size of their sales team, and triple the number of inbound leads. Default allowed Runway to be 10x more effective in managing inbound operations and spinning up new marketing channels.

Default’s white glove onboarding experience and “one Slack away” customer success policy help Runway’s marketing focus on driving a measurable impact on inbound pipeline growth.

Strategic Challenge

Bland is a conversational AI platform that lets enterprises build voice, SMS, chat, and email agents on a self-hosted stack. In less than a year, the company went from seed to Series B and raised $65M, which translated directly into waves of inbound interest every time a product launch or announcement hit social media.

Each viral spike produced more leads than the team could safely triage, and there was no reliable way to separate serious buyers from noise before those meetings landed on AE calendars. The team had the classic inbound stack: a form, routing, and scheduling tool stitched together. When big campaigns spiked traffic, AEs risked seeing too many low-value meetings, while high-intent visitors who dropped off at the scheduler had no safety net. There was no consistent way to decide which leads should get straight to an AE, which needed more qualification, and which should go into sequences for later.

On top of that, Bland ran a strong PLG motion: prospects could “get started for free today” on self-serve. Enterprise companies would sign up, start playing with the product, and never get channeled into a sales conversation. The team knew there was “GTM alpha” hidden in these signups, but no process to quickly enrich, qualify, and route to the appropriate rep.

As the company grew, spinning up new motions added even more complexity. The team launched a marketing phone line where visitors could get a live call from “Blandy,” their AI agent—but for months, nothing happened with that call data after the demo ended. In parallel, an outbound SDR program was booking meetings, but handoffs to AEs were inconsistent and vulnerable to “cherry-picking”—selecting whoever would most easily accept a meeting as qualified.

All of this created real business risk. Inbound leads were unevenly prioritized, self-serve activity wasn’t consistently surfaced to sales, marketing line callers weren’t being followed up with systematically, and SDR-booked meetings weren’t being distributed fairly across AEs. The team could feel the drag: too much manual triage, too many “ghost” leads that no one owned, and no single place to see how all these flows worked together.

{{testimonial-1}}

‍

Default Layer

Bland brought in Default first to stabilize inbound. Over time, that decision turned Default into “a really core pillar in our go-to-market tech stack,” spanning inbound, PLG, and the marketing line. Instead of three disconnected workflows, everything now runs on a single control layer.

For inbound, the contact sales form on Bland’s website is now powered end-to-end by Default. When someone fills it out, Default enriches the record using waterfall enrichment. Conditional if/else checks then decide whether the lead is qualified, which segment it belongs to, and whether it should land on an AE’s calendar, go to a different path, or be nurtured.

“Default is powering this end to end for us from the contact sales form on our website to the scheduler, to the really important conditional logic that ultimately is what keeps the unqualified or maybe more questionable meetings from landing directly on AEs’ calendars.” said Mack Caruso, Director of Revenue Operations.

Crucially, the same logic doesn’t have to be rebuilt in ten places. Self-serve signups now use a Default-powered form as well. Every signup flows into Default, is enriched, and is evaluated using shared conditions. SDRs get Slack alerts for the highest-value signups so they can “pick up the phone within a few minutes” and ask, “Hey, I saw that you just signed up for Bland. What are you hoping to build?”

Default also became the orchestration layer for more creative workflows. Bland’s marketing line now pushes call variables from the AI agent into Default via webhook. Default enriches the caller, checks fit, and notifies sales to follow up directly after the AI demo.

In outbound, SDRs log calls in HubSpot and use a Default-powered scheduling link embedded directly on the contact record. A short form determines whether the meeting should go to enterprise or mid-market, and Default then distributes meetings equitably across AEs based on shared rules, rather than letting individuals route to their “favorite” rep.

Underneath, the team now has a single place where definitions, logic, and safeguards live. In Mack’s words, “the platform is incredibly flexible. It's allowed us to solve a number of challenges in the business as we've grown or as we've realized opportunities,” from inbound handoffs to PLG to the marketing line. Default coexists with HubSpot, Salesforce, and other tools, but it’s the layer that keeps behavior consistent—one system they can reason about and change without worrying that a tweak in one channel will unpredictably break another.

{{testimonial-2}}

‍

GTM Advantage

For Bland, Default started as a way to survive “massive waves of inbound demand” with a small team. It’s now the connective layer that runs inbound, PLG, and the marketing line—and the first place they look when they see a new GTM opportunity. As Mack puts it, “[Default] is incredibly flexible. It's allowed us to solve a number of challenges in the business as we've grown.”

Operational Wins

• Cleaner, safer routing across three motions. Default’s shared conditions now filter out “unqualified and maybe not the best use of time type of opportunities” before they hit AE calendars, while Slack alerts for scheduler drop-offs give SDRs a structured safety net for high-intent visitors who didn’t click “book.”
• Fewer manual fixes and less tool-sprawl overhead. Instead of “stitching together multiple tools… and then even more to try and understand the data picture,” Bland runs inbound, PLG, and the marketing line on one control layer. That consolidation reduces the number of brittle handoffs RevOps has to monitor and fix.
• A system they can actually reason about. Because routing, enrichment, and qualification live in Default, changes feel safer: the team can toggle conditions “in real time” as they see new patterns in demand, without wondering which hidden flow will break.

Revenue Wins

• Bland attributes net-new pipeline directly to the combination of Blandy + Default. They state, “we have pipeline that exists now that would otherwise not have existed,” and note that self-serve conversion to enterprise has “gone up” thanks to steering high-value signups into sales conversations.
• Revenue lift from focusing reps on the right opportunities. By cutting time on unqualified leads and turning new lead sources into structured, enriched leads, “revenue has gone up… [Default is] helping us generate pipeline… and creating that efficiency within the team.”

Strategic Wins

• A foundation for better attribution and forecasting. Default’s AI prompts now normalize messy UTM parameters and stamp them into HubSpot, giving Bland “end-to-end” visibility from Google Analytics through to their CRM and setting the stage for more reliable attribution over time.
• One platform to extend before buying the next tool. Internally, the mantra has become: “before you go and buy another tool, ask yourself, can I build it on Default? Because the answer for us most commonly has been yes.” That mindset turns Default from a point solution into a strategic layer they can keep compounding on.

{{testimonial-3}}

‍

Looking ahead

The next chapter is less about adding more tools and more about deepening this foundation: tightening attribution, layering in richer analytics on top of Default’s cleaned data, and continuing to ask “can we build this on Default?” whenever a new motion appears. With a single system to capture signals from web forms, product usage, and marketing calls, Bland is set up to turn today’s operational control into tomorrow’s compounding GTM intelligence.

Challenge

When a new marketing leader joined Rootly, the team needed to quickly implement technology to scale their marketing efforts. Liza Dukhova, RevOps Manager at Rootly, took charge of managing inbound operations.

Their process relied on a complex web of tools: HubSpot forms, Chili Piper scheduling, Salesforce workflows, and numerous Zapier automations. As marketing channels expanded, managing revenue operations became increasingly difficult. More than 5% of leads were misrouted or lost when parts of this cobbled-together workflow failed.

Each demo request followed a convoluted path: it started in HubSpot, moved to Chili Piper for rep routing based on Salesforce data, and then — after a successful booking — another workflow attempted to sync data between the CRMs and create a Salesforce opportunity. This worked in theory, but reality proved messier.

The RevOps team found themselves constantly switching between Salesforce, HubSpot, and Chili Piper — troubleshooting even simple issues required checking multiple systems. With vendors pointing fingers at each other and the team spending full days on troubleshooting, they needed a new solution that could natively support both Salesforce and HubSpot.

‍

{{testimonial-1}}

‍

Solution

Use case #1: Automate inbound scheduling

Within weeks of implementing their first workflow, the Rootly team achieved higher inbound conversions and reduced lead drop-off. The team recovered most qualified leads through Default's "meeting not booked" automations when prospects didn't schedule after form submission.

By implementing Default's inbound scheduling and lead follow-up system with automatic Outreach sequence enrollment, Rootly generated 10% more inbound demos within 4 weeks—all supported by the Default team via Slack.

Now, Rootly's inbound flow looks like this:

• After a form submission, Default enriches each lead
• Default then checks for records in Salesforce and HubSpot
• If a lead is unowned, Default round-robins and shows the next person's calendar
• If a lead is owned, the Account owner's calendar is displayed
• After the meeting is booked, Default sends a custom Slack alert with context from all systems
• If the meeting is not booked, Default enrolls a lead into an Outreach sequence and alerts the sales team on Slack

‍

{{testimonial-2}}

‍

Use case #2: Route product signups

After implementing Default, Rootly expanded its lead capture methods through content forms and free trial signups to boost pipeline generation. The RevOps team now automatically routes, enriches, and assigns product signups to specific sales representatives. This streamlined workflow has boosted Rootly's product-led pipeline by 15% within two months while enabling the team to support new marketing initiatives more quickly.

‍

{{testimonial-3}}

‍

Use case #3: Selective CRM sync

Unlike their previous scheduling tool that was limited to integrating with just one CRM system, Rootly found Default's workflow builder more versatile. The team created a selective CRM sync that automatically transfers marketing attribution data to Salesforce opportunities upon meeting bookings.

With Default, Rootly cut down several hours of weekly troubleshooting time and streamlined their revenue operations processes, boosting overall efficiency for both sales and marketing teams.

‍

{{testimonial-4}}

‍

Results

After their previous Chili Piper and Zapier workflows underperformed, Default emerged as the ideal solution for Rootly. The switch delivered impressive results: a 23% improvement in inbound conversion rates, 15% more pipeline from product-led growth, and doubled efficiency in revenue operations.

With Default, Rootly restored control over their fragmented workflows and strengthened collaboration between sales, marketing, and revenue teams.