Setting Smart Defaults in Sales Workflows

My client cut implementation time from 60 days to 21 days. We didn’t hire more onboarding specialists. We didn’t add more training sessions. We didn’t ship new features. We made one change: 𝘂𝘀𝗲 𝗰𝗮𝘀𝗲 𝘀𝗽𝗲𝗰𝗶𝗳𝗶𝗰 𝗱𝗲𝗳𝗮𝘂𝗹𝘁 𝘀𝗲𝘁𝘁𝗶𝗻𝗴𝘀 This company worked in restaurant software. Highly customizable product. Endless configuration options. And onboarding looked like most SaaS onboarding: Session after session teaching customers all the ways they *could* configure the system… Hoping they’d design the “perfect” setup. But onboarding isn’t about exploring possibilities. It’s about getting to results. We stepped back and asked: Do we already know the best configuration for most of these customers? Yes. Quick service restaurants operate differently than sit-down restaurants. Certain brands have predictable workflows. After hundreds of implementations, the patterns were obvious. So instead of starting from scratch every time, we created use case specific default settings aligned to each restaurant type. The moment a customer signed, we applied the preset that matched their model. 𝗗𝗮𝘆 𝗼𝗻𝗲: 𝘀𝘆𝘀𝘁𝗲𝗺 𝗿𝗲𝗮𝗱𝘆. Not “let’s spend three weeks deciding how to configure this.” Ready. That shifted everything. Instead of wasting time on configuration education and endless setup decisions, onboarding focused on what actually determines success: Behavior change. – How will your team use this daily? – What needs to change at the register? – What changes in the kitchen? – Who owns what? Configuration isn’t the hard part. Changing behavior is. When you remove unnecessary complexity with strong, use case specific default settings, you create space to focus on the real work. If your onboarding is dragging, ask yourself: Are we teaching customers all the ways they could set it up… Or are we locking in what works and helping them win faster? Sometimes speed to value doesn’t come from more flexibility. It comes from smarter defaults.

The biggest time sink in sales isn't the call. It's everything that happens before and after it. Pre-call: reviewing CRM history, chasing context across notes and deal stages. Post-call: updating properties, writing follow-ups, creating tasks. HubSpot's new Smart Deal Progression feature is a direct answer to this. and it's worth paying attention to because it's solving a workflow problem, not just an AI novelty. After each recorded call or meeting, reps get suggested CRM updates, drafted follow-up emails, and identified next steps, all based on the actual transcript and Deal context. Before the next meeting, they get a prep summary with deal score, risks, and buyer goals. The screenshot below is a real example of what the post-call review looks like. Four CRM property suggestions ready to approve. Next steps broken out by owner. A follow-up email draft waiting. All pulled from one conversation. This matters most at scale. A rep with 40 active deals doesn't forget to follow up because they don't care. they forget because the post-call checklist is long and manual. Automation grounded in real conversation context (not templates) changes that equation. One thing worth knowing on pricing before you dive in: → Default HubSpot properties: free → Custom properties: 10 credits per property, per transcript → Know what credits you have, how you can use them So if you're running 5 transcripts against 5 custom properties, that's 250 credits. Worth being deliberate about which properties you actually want captured before you configure it. Still early, but this is the direction the best sales tooling is heading: AI that reduces friction at the exact moments where deals stall. Available for Sales and Service Pro+ seats. On by default for all recorded calls and meetings, no additional setup required. #AIRops #HubSpot #SalesTech #RevOps #AI #DealManagement #CRM #SalesOps #HubSpotAdmin

Every product is a decision machine. Your settings screen. Your pricing page. Your checkout flow. Each one quietly asks users to choose. And how you structure those choices determines whether they act… or hesitate. This is choice architecture: the difference between users who convert and users who freeze. It allows users to feel safe and secure in their decision-making. Prompts users to take action and allows them to make better decisions. In other words, decision-making has been made easier. Here’s how strong products do it. 1️⃣ Smart defaults do most of the work. Use defaults when:  • The option is genuinely good for most users.  • The decision is complex or unfamiliar.  • You want to reduce setup friction (privacy-safe settings, essential notifications). 2️⃣ Fewer choices for better structuring. - Provide multiple options within the same general area of choice  - Use hierarchy to indicate which option would be preferred. - Limit to 3 -5 choices, and identify 3 -4 delivery methods within that. 3️⃣ Frame choices as a guide. - Use plain language, not internal jargon.  - Replace “Plan A / Plan B” with meaningful labels.  (“Recommended for most teams”, “Flexible — 7-day trial”)  - Use visual weight (size, color, layout) to guide attention. ✦ Before you add features,design how decisions are made. What's the worst choice paralysis you've seen in a product? Drop an example below. Because great UX is how confidently users choose to move forward. ♻️ Share this to help others design better. 🔔 Follow Artem Borysenko for more updates!

The most counterintuitive thing I've learned building Stella: Every feature you add that you think improves the product also confuses a percentage of your users. Sometimes a large percentage. We'll push something live that makes the tool more powerful and configurable. And within a week, support messages start rolling in: "What is this new setting?" "Should I change this?" "I entered X, was that right?" And the answer, most of the time, is that the default way we had the program set up was already the best option. They didn't need to touch anything. But because the option existed, they felt like they should. We work with very smart people. Our clients are senior ecom operators, agency leaders, marketing directors at large brands. They don't need hand-holding on most things. But incrementality testing is inherently super technical. There's a data science layer underneath every setting in our platform. And when you expose more of that layer to give power users more control, you simultaneously overwhelm the people who just want to get from point A to point B. The instinct as a builder is always "more features = better product" The reality is the best product is the most usable. What we've landed on for now: Smart defaults that work for 90% of use cases, with advanced options tucked away for the 10% who know what they're doing. It's not perfect. But it's a lot better than building a mecha godzilla cockpit when most of your users just need a steering wheel.

Your onboarding has a hidden tax. It’s not time. It’s decision fatigue. And it’s killing your activation. Most SaaS founders track:  • Time to complete  • Drop-off points  • Steps finished Almost nobody tracks:  • How many decisions users make  • How hard those decisions are  • How uncertain each step feels So they optimize speed. But users don’t quit because it’s long. They quit because it’s exhausting. Here’s a simple way to think about it: Every step in your onboarding creates: Choices × Difficulty × Uncertainty More choices More complexity More “what happens if I click this?” = More fatigue. And fatigue = abandonment. I tested this across 50+ SaaS products. Low-fatigue onboarding → 70%+ activation. High-fatigue onboarding → ~30% activation. Time wasn’t the best predictor. Fatigue was. Quick example: Before:  - 12 integration options  - 8 notification toggles  - Multiple team invite steps Activation: 34% After: - 3 recommended integrations - 3 preset notification styles  - Team invite optional Activation: 68% Same product.  Fewer decisions.  2× activation. Here’s how to reduce fatigue fast: 1️⃣ Reduce options  Don’t show 12 integrations.  Show 3 recommended. 2️⃣ Use smart defaults  Pre-select what most users choose. 3️⃣ Increase certainty  Preview what will happen after they click. 4️⃣ Defer non-critical choices  “Skip for now” is powerful. The mindset shift: Stop asking  “Is this flow too long?” Start asking  “Where are we exhausting users?” Because users don’t abandon long flows. They abandon tiring ones. If your activation rate is under 40%, It’s probably not a traffic problem. It’s a fatigue problem. Want a simple exercise? Pick your onboarding. Count the decisions in each step. Find the one that feels mentally heavy. Fix that first. That’s usually where your growth is hiding.