The LeanScale Podcast · Episode 13

5 Ways to Optimize Salesforce

LeanScale Chief Architect Henrique Sakai on the five CRM foundations that make your revenue data trustworthy

Henrique Sakai · Chief Architect & Co-Founder, LeanScale · LeanScale Hosted by Anthony Enrico
Published Updated 00:14:33 10 min read 2,009 words
Executive Summary

The one-paragraph brief, extended

Why this conversation matters — and who should spend the hour.

Episode 13 is the first of The LeanScale Podcast's tech-side deep dives, and it hands the mic to the person Anthony Enrico calls the best Salesforce operator he knows: his co-founder and LeanScale's Chief Architect, Henrique Sakai. The two worked together at three scaling B2B tech companies before founding LeanScale, with Sakai serving as the systems architect who wired Salesforce into HubSpot, Marketo, and the rest of the go-to-market stack. The premise is simple — the CRM is the backbone of your revenue operation, and five foundational configurations decide whether the data sitting on top of it is trustworthy.

Sakai's five foundations are practical and opinionated. First, enable field history tracking — the audit trail that lets you diagnose data issues and that third-party forecasting, intelligence, and AI tools mine to predict the future. Second, timestamp your critical objects with dedicated custom fields that capture every stage and status change, because history tracking is poor at reporting and only timestamps give you clean, native sales-cycle and conversion data. Third, freeze your closed-won data behind hard locks, validation rules, automation, and weekly backups, so a single edit can't invalidate a forecast, a board number, or a commission check. Fourth, make sure lead data — lead source, lead source detail, owner, and lifecycle timestamps — flows into accounts, contacts, and opportunities on conversion, or reporting on your marketing channels becomes nearly impossible. Fifth, put validation rules in place that match your sales process and enforce data integrity at the point of entry, without overdoing the controls.

The throughline is that clean, governed CRM data is the prerequisite for everything downstream — trustworthy reporting and dashboards, reliable forecasting, accurate commissions, and any AI or third-party tool you layer on top. It's a short, foundational episode aimed at RevOps leaders, sales and marketing operators, and founders who want a CRM their team can actually trust, love using, and build the rest of their tech stack around. Anthony frames it as the first of many LeanScale conversations on getting the most out of Salesforce.

Key Takeaways

9 things worth stealing

The load-bearing ideas, each with the business implication and who should care.

01

Enable field history tracking — it's the audit trail for your entire CRM

Sakai's first foundation is turning on field history tracking so you can see how data evolved over time, diagnose issues and errors in the database, and give admins and users a historical snapshot of every change. It's the baseline of a well-tuned operation and something too many teams leave off.

Why it matters: Before you optimize anything else in Salesforce, switch on history tracking for the fields that matter. Without it you can't reconstruct what happened, and you're flying blind when data problems surface.

RevOps LeadersSales Leaders
02

History tracking is also the backbone for third-party and AI tools

Forecasting, intelligence, and productivity tools all tap into Salesforce history to understand the past — and, increasingly, AI looks at that same historical data to predict the future. Enabling history tracking isn't just good CRM hygiene; it's the precondition for layering other technology on top.

Why it matters: Treat history tracking as infrastructure for your whole tech stack. If you plan to adopt forecasting, intelligence, or AI tooling, the value of those tools is capped by how much clean historical data they have to learn from.

RevOps LeadersFoundersRevenue Executives
03

Timestamp every critical stage and status change with dedicated custom fields

Because history tracking is weak at reporting, Sakai builds dedicated custom fields that capture the date each lead status, lifecycle stage, or opportunity stage changed. That extra layer lets you report directly on the field and pull sales-cycle and conversion data natively, instead of digging through the history log.

Why it matters: Instrument your most important objects with stage-change timestamp fields. It's the only clean way to measure sales cycle length and stage-to-stage conversion in native Salesforce reports and dashboards.

RevOps LeadersSales Leaders
04

Freeze your closed-won data with hard locks

People assume closed-won data never changes, but salespeople make mistakes and uninformed reps go back and edit it — and the moment one small field changes on a closed opportunity, the entire analysis is invalidated. Sakai locks it down so only a super admin can change a closed opportunity.

Why it matters: Put barriers around closed-won data before it corrupts your forecasting, trend analysis, and board reporting. Closed-won should be effectively read-only for the field.

RevOps LeadersSales LeadersRevenue Executives
05

Lock it down with layers — validation rules, automation, and weekly backups

Sakai doesn't rely on a single control. He uses validation rules, automation that snaps records back to their original values, and a weekly backup of the data, so it's hard for anyone to get around the layers and break the system. The goal is data that's clean and identical every single time.

Why it matters: Defense in depth beats a single permission setting. Combine validation rules, automation, and routine backups so closed and critical data stays intact even when someone tries to edit it.

RevOps LeadersRevenue Executives
06

Protect closed data because it drives commissions and board numbers

Frozen closed-won data isn't a nice-to-have — it underpins your sales forecasting, your commissions plan, and your trend analysis. As Sakai puts it, you don't want to mess up with people's money, and you don't want to redo a board deck because someone edited a closed deal after the fact.

Why it matters: Tie the case for locking closed data to money and trust: accurate commissions and defensible board reporting. That framing usually wins the argument for stricter controls.

Revenue ExecutivesSales LeadersFounders
07

Flow lead data into every object when a lead converts

When a lead converts to an account, contact, and opportunity, the important lead-level data — lead source, lead source detail, lead owner and SDR, and lifecycle timestamps — has to carry across. If it doesn't, you lose the data at the end of the flow and inject noise into the business.

Why it matters: Map exactly which lead fields must survive conversion and build the automation to carry them onto the opportunity. Anything you drop at conversion is data you can never report on downstream.

RevOps LeadersMarketing Leaders
08

Without lead-to-opportunity flow, channel attribution is nearly impossible

A classic VP-of-ops question is 'which lead source has the most closed-won opportunities?' or 'what's the full sales cycle from marketing qualified lead to close?' If lead source lives only on the lead and never reaches the opportunity, those questions become nearly impossible to answer.

Why it matters: Getting lead source and lifecycle data onto the opportunity is what lets you understand and double down on your best marketing channels. It's foundational to any credible attribution or funnel reporting.

Marketing LeadersRevOps Leaders
09

Put validation rules in place — but don't overdo the controls

Validation rules make sure the data entered meets your business process, from simple checks (amount required before close, close date can't be in the past) to complex ones tied to your sales methodology so the right data is captured at the right stage. But the healthy balance is enough validation to inform the process without so many controls that reps can't work.

Why it matters: Design validation rules against your actual sales process and customer journey, capturing the right data at the right time. Aim for the minimum set that enforces integrity — over-controlling frustrates the team and slows the motion.

RevOps LeadersSales Leaders
Frameworks Discussed

6 named models

Every framework Jimmy names, defined and time-stamped.

The Five Salesforce Foundations

00:28

A five-part checklist for a trustworthy CRM: (1) enable field history tracking, (2) timestamp critical stage and status changes with custom fields, (3) freeze closed-won data, (4) flow lead data into every object on conversion, and (5) put validation rules in place.

Sakai frames these as the foundational elements that let you get the most out of your overall tech stack, have data you can trust, and create an experience your team loves. Each addresses a distinct failure mode — no audit trail, no reportable sales-cycle data, corrupted closed deals, lost attribution data, and dirty inputs.

Field History Tracking

01:41

Turning on Salesforce field history tracking to record how data evolves over time, providing an audit trail for diagnosing issues and a historical snapshot for admins, users, and downstream tools.

The first and top recommendation. Beyond in-CRM diagnostics, history tracking is what third-party forecasting, intelligence, and AI tools mine to understand the past and predict the future — so it doubles as infrastructure for the rest of the stack.

Stage-Change Timestamps

03:31

Dedicated custom fields that capture the date each important status or stage changed — lead status, lead lifecycle stage, opportunity stage, customer stage, or proof-of-concept stage — so change data is directly reportable.

History tracking records changes but reports on them poorly. Timestamp fields add a reporting layer that makes sales-cycle length and stage-to-stage conversion available in native Salesforce reports and dashboards without digging through the history log.

Freeze Closed-Won Data

06:10

Locking closed opportunity data so it can't be edited after the deal closes — restricting changes to a super admin and reinforcing it with validation rules, automation, and weekly backups.

A single edit to a closed opportunity can invalidate an entire analysis. Freezing closed-won protects sales forecasting, commissions, and board-ready trend analysis, and keeps the data clean and identical every time.

Lead-to-Object Data Flow

08:22

Ensuring that when a lead converts, its important fields — lead source, lead source detail, owner/SDR, and lifecycle timestamps — carry across to the account, contact, and opportunity records.

Leads and opportunities are separate objects that aren't typically related, so data not carried forward at conversion is lost forever. Preserving it is what makes channel attribution and MQL-to-close funnel reporting possible.

Validation Rules That Match the Process

10:38

Rules that block records from saving unless they meet your business process — from simple checks (required amount, no past close dates) to methodology-driven requirements that ask for the right data at each stage.

Validation rules enforce data integrity at the point of entry so reps can't save incomplete records. The craft is balance: enough validation to inform the process and align with the customer journey, without so many controls that the team is over-constrained.

Best Quotes

13 lines worth clipping

Pulled verbatim. Copy or share any of them.

“The CRM is the backbone of your revenue operation.”
Anthony Enrico 00:28
“The very first recommendation, top one, is enable history tracking. This is very important to understand how data evolved over time, diagnosing any issues or errors that may arise in your database.”
Henrique Sakai 01:41
“Having that enabled isn't just important for your CRM — it's also going to be the backbone to prepare for using other technology as well.”
Anthony Enrico 02:19
“Now with all the AI coming up, they're always looking to your past so they can try to predict the future a little better.”
Henrique Sakai 02:56
“History tracking is not so good at reporting. Creating the timestamps creates an additional layer of analysis that we can do for an object.”
Henrique Sakai 04:25
“You can report directly on that field and do really quick sales-cycle data and conversion data — you don't have to dig through the history tracking, you have it easily accessible for building reports and dashboards native in Salesforce.”
Anthony Enrico 05:31
“Tip number three is freeze your close opportunity data. People always assume this data will never change, but people make mistakes, or an uninformed salesperson would go and change it.”
Henrique Sakai 06:10
“It's important with your commissions plan. You don't want to mess up with people's money. The moment someone changes this small little thing in an opportunity, the entire analysis is invalidated.”
Henrique Sakai 07:01
“The way I've seen you do it is pretty much total lockdown. The only person who can make a change or close an opportunity is the super admin in your instance.”
Anthony Enrico 07:51
“I want to make sure I put actual layers of security so data is always clean, always the same every time. Plus, we back up the data every week.”
Henrique Sakai 08:22
“Which lead source has the most closed-won opportunities? If you're capturing the lead source on that lead object and you don't bring it over, it becomes nearly impossible to answer that question.”
Anthony Enrico 10:08
“Tip number five is make sure validation rules are in place. You want to make sure the data entered in your system meets your business processes.”
Henrique Sakai 10:38
“Having the right level of validation rules in place to actually inform the process, but maybe not overdoing it to add too many controls, is a really healthy balance.”
Anthony Enrico 12:11
Practical Advice

What should you actually do?

The playbook, split by the seat you sit in.

RevOps Leaders

  • Enable field history tracking on the fields that matter as a baseline — it's the audit trail you'll need to diagnose data issues and the foundation any third-party or AI tool learns from.
  • Instrument your critical objects with dedicated stage-change timestamp fields so sales-cycle and conversion data is reportable natively, instead of buried in the history log.
  • Lock down closed-won data with layered controls: restrict edits to a super admin, add validation rules and automation that revert changes, and back up the data weekly.
  • Build conversion automation that carries lead source, lead source detail, owner/SDR, and lifecycle timestamps onto the account, contact, and opportunity so nothing is lost at conversion.

Sales Leaders

  • Treat closed-won as read-only for the field — a single after-the-fact edit can invalidate a forecast, a commission calculation, or a board number.
  • Use stage-change timestamps to measure real sales-cycle length and stage-to-stage conversion, and coach off that clean data.
  • Push for validation rules that enforce your sales process at each stage, but resist over-controlling — too many rules frustrate reps and slow the motion.

Marketing Leaders

  • Insist that lead source and lead source detail survive lead conversion onto the opportunity — without it, channel attribution and MQL-to-close reporting are nearly impossible.
  • Use the preserved lead data to answer which sources actually produce closed-won revenue, and reallocate spend toward your best-performing channels.
Operations Takeaways

By function

The same conversation, filtered for RevOps, pipeline/marketing ops, and customer ops.

Revenue Operations

  • History tracking first. Enable field history tracking as the audit trail for the CRM and the historical data every downstream tool (including AI) learns from.
  • Timestamp for reporting. History tracking reports poorly — add dedicated stage-change timestamp fields to make sales-cycle and conversion data available natively.
  • Freeze closed data in layers. Restrict closed-opportunity edits to a super admin, reinforce with validation rules and automation, and back up weekly so analysis stays intact.
  • Don't lose data at conversion. Carry lead source, detail, owner, and lifecycle timestamps onto account/contact/opportunity when a lead converts — separate objects mean anything dropped is gone.
  • Validate to the process. Enforce data integrity at entry with validation rules matched to your sales process and customer journey, without over-controlling reps.

Pipeline & Marketing Ops

  • Instrument the funnel. Stage-change timestamps on leads and opportunities are what let you measure sales-cycle length and stage-to-stage conversion.
  • Attribution needs the opportunity. Lead source must reach the opportunity object or you can't answer which channels produce closed-won revenue.
  • MQL-to-close visibility. Carrying lifecycle timestamps across conversion is what makes full marketing-qualified-lead-to-close reporting possible.
  • Clean closed data. Frozen closed-won opportunities keep conversion rates and win/loss trends trustworthy for pipeline analysis.
Metrics Mentioned

The numbers, with context

5
Foundational optimizations

The episode covers five foundational Salesforce configurations every RevOps team should implement.

Weekly
Data backup cadence

Sakai backs up Salesforce data every week as a safety layer on top of validation rules and automation that lock down closed data.

3
Companies worked together

Anthony and Sakai worked together at three scaling B2B tech companies before starting LeanScale.

Super admin only
Closed-opportunity edit access

Sakai restricts the ability to change or close an opportunity to the super admin so closed-won data stays frozen.

Entities

Companies, people & tools mentioned

Auto-extracted and linked into the knowledge graph.

Companies

People

Tools & software

SalesforceCRM

The CRM the entire episode optimizes — history tracking, stage timestamps, closed-data locks, lead-to-object flow, and validation rules are all Salesforce configurations Sakai recommends.

HubSpotCRM

One of the go-to-market tools Sakai connected to Salesforce as a systems architect at earlier companies, alongside Marketo.

MarketoMarketing Automation

Named among the marketing and go-to-market tools Sakai wired into Salesforce when building integrated revenue operations before LeanScale.

Frequently Asked Questions

Straight answers

Generated from the conversation, marked up for search and AI extraction.

What are the five ways to optimize Salesforce?

LeanScale Chief Architect Henrique Sakai's five foundations are: (1) enable field history tracking, (2) add custom timestamp fields that record every important stage and status change, (3) freeze closed-won opportunity data so it can't be edited, (4) make sure lead data flows into accounts, contacts, and opportunities when a lead converts, and (5) put validation rules in place that match your sales process. Together they give you data you can trust, native reporting, and a foundation for the rest of your tech stack.

Why should you enable field history tracking in Salesforce?

Field history tracking records how data changes over time, giving admins and users an audit trail to diagnose issues and errors and a historical snapshot of the database. It's also the backbone for third-party forecasting, intelligence, and AI tools, which mine that historical data to understand the past and predict the future. Enabling it is the first thing to do before optimizing anything else in the CRM.

Why use custom timestamp fields instead of relying on Salesforce history tracking?

History tracking records changes but reports on them poorly. Dedicated custom timestamp fields capture the date each lead status, lifecycle stage, or opportunity stage changed, and because they're regular fields you can report on them directly. That's the only clean way to build sales-cycle and stage-to-stage conversion reports and dashboards natively in Salesforce, without digging through the history log.

How do you stop closed-won opportunities from being changed in Salesforce?

Freeze the data with layered controls. Restrict the ability to change or close an opportunity to a super admin, add validation rules and automation that revert unauthorized edits back to their original values, and back up the data weekly. This matters because a single edit to a closed opportunity can invalidate an entire analysis and corrupt forecasting, commissions, and board reporting.

What lead data should flow to the opportunity when a lead is converted?

The lead-level fields you'll need later: lead source and lead source detail, lead owner and the SDR, and the lead lifecycle stage timestamps. Leads and opportunities are separate objects that aren't automatically related, so anything not carried across at conversion is lost. Preserving this data is what makes marketing channel attribution and full MQL-to-close funnel reporting possible.

What are validation rules in Salesforce and how many should you use?

Validation rules block a record from saving unless it meets your business process — from simple checks like requiring an amount before closing or preventing a close date in the past, to methodology-driven requirements that ask for the right data at each stage. Use enough to enforce data integrity and inform the process, but avoid over-controlling; too many rules frustrate reps. The healthy balance aligns the rules with your sales process and customer journey.

Why is CRM data hygiene the foundation of your go-to-market tech stack?

Because everything downstream depends on it. Trustworthy reporting and dashboards, reliable forecasting, accurate commissions, and any AI or third-party tool you adopt all draw on the CRM's data. If history isn't tracked, stages aren't timestamped, closed data drifts, lead data is lost at conversion, or inputs aren't validated, the tools you layer on top inherit that noise — garbage in, garbage out.

Full Transcript

The whole conversation

Broken into chapters, searchable, verbatim from the audio. Speakers inferred (not diarized).

00:00Cold open

0:00 Data keeps changing how you can be secure of all the analysis that you've done.

00:16Welcome to The LeanScale Podcast

0:16 Welcome to The LeanScale Podcast where we talk about everything RevOps. Thank you for listening.

00:28Meet Sakai: the CRM is the backbone

0:28 The CRM is the backbone of your revenue operation and I'm really excited to dive into the five things you need to be doing with Salesforce. With my co-founder, LeanScale's chief architect, most importantly my good friend, Sakai. Sakai, thanks for being here with us today to talk through it. Fortunately, thanks. Thanks for inviting me. I was dying to come here and discuss a little bit of the tech side of the house. My private recommendations, I hope they help the listeners get the best use of their CRM.

1:04 Yeah, absolutely. I can't think of anybody who knows Salesforce better than you. For those who don't know, Sakai and I worked together at three scaling B2B tech companies before starting LeanScale. Sakai was always a systems architect connecting Salesforce with HubSpot, Marketo, the rest of our go-to-market tools and built beautiful operations. He made all my dreams come true as a VP of RevOps. I can't think of anybody who has better recommendations than you and I know it's not going to end with today. Today is just going to be the top five, but we're going to have a lot more content on how to get the most out of your CRM in the future.

01:41Tip 1: Enable field history tracking

1:41 Yep, for sure. If you're down, let's start with the very first one. Alright, yeah, let's dive in. What's the first thing people need to be doing if they're using Salesforce? Of course, the very first one recommendation, top one is, you know, enable history track. This is very important to understand how data evolved over time, diagnosing any issues or errors that may arise in your database. Of course, he also gives admins and users a historical snapshot of the data changes that you had in your CRM.

2:19 Super important for any business, important for admins, important for revenue operations. If you need to know what happened in the past, go look into the history track. You know, it's interesting too on history tracking. There's a lot of third party tools that tap into that history tracking intelligence, forecasting tools, intelligence tools, productivity tools. So having that enabled isn't, I wouldn't say it's just important for your CRM, but it's also going to be the backbone to prepare for using other technology as well.

2:56 Right. If you have a well-tuned operation, you always have to lock in some additional third party tools. They are always looking to, you know, understanding the past, what happened in your history tracking and special revenue. They really trying to understand. And also now with all the AI coming up, they are always looking to your past so they can kind of try to predict the future a little better.

03:31Tip 2: Timestamp your critical stage changes

3:31 All right. What's the second thing we need to do if we're using Salesforce? Of course. Second is ensure, you know, timestamps are added to your most important critical objects. You know, when I say timestamps, I'd say timestamps to go and look into how stages changed, statuses that you have, or any field that you use that is important for you to track an important change. So, you know, if you as an example, if you're trying to understand how a lead stage or lead status has changed over time or, you know, opportunity stages are, you know, time stamping out the timestamp through a course of opportunity lifecycle.

4:25 Here is what we do. We create custom fields that track every change you do in each of the, I don't know, stages that you have in an opportunity or any lead status that's important for the operations. They're very important for you to understand, you know, how customers interact with a person with an SDR or how the opportunity evolved over time. You know, because history tracking that we mentioned in the first place, it's not, it doesn't, it's not so, I'd say it's not so good at reporting. We can report on some of the changes, but creating the timestamps creates an additional layer of analysis that we can do for an object as an example.

5:31 Yeah, the way I've seen you do it, so we do this often for our customers. We always had this at the companies that we worked at, but you have a dedicated field. So when did this lead move to this lead lifecycle stage? When did this customer move to this customer stage? And the most common, when did this opportunity move to the next sales stage? So that way you can report directly on that field and then you can also do really quick sales cycle data, use it for conversion data, and not have to dig through the history tracking, but you have it easily accessible for building reports and dashboards native in Salesforce.

06:10Tip 3: Freeze your closed-won data

6:10 All right, Sakai, what's tip number three that people need to be following with their Salesforce instance? Well, tip number three is freeze your close opportunity data. So important for, you know, Salesforce. That seems obvious, right? Doesn't that seem like everybody would have that or it'd be like out of the box in Salesforce, but how many times do you go in with close one changes all the time? People always assume like, oh, this data will never change. But, you know, people makes mistakes or an uninformed salesperson would probably go and change.

6:50 There's all there's a series of things that may happen to your close opportunity. They're all crazy.

7:01 But you need to put, you know, all the barriers and the security in place. So they never changes. You have a good sales forecasting. You can do the best analysis that you can with the close one data. It's important with your commission's plan. You don't want to mess up with people's money. And, of course, it's important to identify trends and patterns if, you know, data keeps changing how you can be secure of, you know, all the analysis that you've done. Because, you know, the moment someone changes this small little thing and an opportunity, the entire analysis is, I don't know, invalidated, right?

7:51 Yeah. And the way the way I've seen you do it. And I don't know if this is your recommendation, but it's pretty much total lockdown. The only person who can make a change or close an opportunity is the super admin in your instance. Yeah, I like to put in place, you know, validation rules. I also like to put, how can I say, automation. People think they change it, but they always go back to what they were before you would say it.

08:22Tip 4: Flow lead data into every object on conversion

8:22 I just want to make sure I put actual layers of security so data is always clean, always the same every time. Plus, we do backup of the data every week so it's hard to go try and go over these layers and break the system that we put in place. Makes sense. Makes sense. Super important. Tip number four. Yep. Tip number four is make sure data from leads go into all the other objects after they are converted. So we are talking about leads converting to accounts, contacts, and opportunities. This is so important. You know, we always want to make sure, you know,

9:11 the lead lifecycle stage timestamps are in each object that we're touching. After it's converted, we want to make sure lead source, I don't know, lead source, lead source details as an example are, well, they flow into opportunities. And, you know, lead owner, SDRs, every piece of information that's important later in the process, they need to be added in there. So, you know, if we want to convert and the data is not at the end of the flow, we lose data, we break the system that we put in place. And, you know, it all contributes you to put noise into your business, which we try and avoid the first time. Right.

10:08 I think something a practical question I would always get as a VP of ops is which lead source has the most closed one opportunities. And if you're capturing the lead source on that lead object and then you don't bring that lead source over, it becomes nearly impossible to answer that question. And then, or what's the full sales cycle for marketing qualified lead to close. So without having everything on the same object, it makes reporting a little bit more difficult.

10:38Tip 5: Put validation rules in place

10:38 So tying those leads and the important data on that lead to that opportunity is really, really important, mainly for reporting and understanding how to get the most out of your marketing channels. So, Sakai, wrap it up for us. Tip number five. What else do you need to be doing in Salesforce if you're not doing it already? Of course, tip number five is make sure validation rules are in place. You know, you want to make sure the data entered in your system meets your business processes.

11:13 We're talking about from the very simple, you know, make sure amount is in place before you close one, an opportunity to make sure that the close date is not in the past. And all the way into like a more complex, you know, tie to your, I don't know, let's say, which sales. How do you say the sales? I lost the word, Anthony, forgot. Sales methodologies, like making sure. Yeah, sales methodology. Yeah. Yeah. Yeah. So make sure like your sale methodology is in place and you ask for the data the right time and in the right place. In each stage you're going through, there are pieces of information that are important for each of these stages.

12:11Recap: the five foundations

12:11 And, you know, you're going to end up in enforcing the data integrity is in place and accurate because you're going to prevent people from saving a record without the right pieces of information that you need. Yeah, makes a ton of sense. I mean, having the right level of validation rules in place to actually inform the process, but maybe not overdoing it to add too many controls is a really healthy balance. So just wrap it up. Five things that you need to be doing in Salesforce if you're not doing it already. Enable history tracking, get that rich out of history on the fields that are important to you.

13:00 Time stamp your staging, lead staging, opportunity staging, count staging. If you're doing proof of concepts or proof of values, add staging there and time stamp it. It's the only way you're going to get sales cycle and conversion data. Freeze your close one data. You don't need to go back to a board meeting and have to redo all the data on your close to one opportunities because somebody's been going in the past and changing things. Make sure those fields and piece of data that are important on your leads make their way to opportunities because they're separate objects. They're not typically related to each other.

13:35 So making sure you're bringing that data over is super important. And then tip number five, put the validation rules in place that align with your sales process and your customer journey to make sure you're capturing the right data at the right time. Sakai, thank you so much. I know our listeners are going to really appreciate this and I know we're going to do some more of these in the future. And I really appreciate you being here. Of course, and thanks. Looking forward for the next episodes and I hope you guys enjoy the first, the five tips on how to make successful operations from the tech perspective. Thanks, Sakai. Yeah, thanks.

14:18Outro

14:18 Thank you for listening to this episode. If you like the discussion, please like share and subscribe to wherever you listen to podcasts so you never miss a new episode.