GAT Solutions logoGAT SolutionsBook a call
Menu

Salesforce Sales Cloud Consulting

We build Sales Cloud for B2B sales and revenue teams: lead intake and routing, territories, forecasting, lifecycle email, quotes and billing sync.

What we build on Sales Cloud

We build the system a deal moves through on Sales Cloud: intake from every door, owner and territory rules, follow-up that runs on its own, stages and a forecast leadership can read, billing and product usage beside the deal, and a release path that keeps the org safe to change. Much of it runs in our own Salesforce org first, and each solution below says when it does.

  • $120K → $4.8M ARRRevenue grown on the sales pipeline we built and ran.
  • Our own orgLead intake, attribution, lifecycle email and releases run in our own Salesforce first.
  • Opt-out at sendEvery lifecycle email reads the opt-out again at the moment it is sent.

What we build for sales and revenue teams

Real systems, in the order a deal meets them. Each one ships on its own and connects to the rest. The ones marked in production run in our own Salesforce org today.

  1. Capture and route the lead
  2. Qualify and follow up
  3. Run the pipeline
  4. Bill, renew and see usage
  5. Keep the org shippable

Capture and route the lead

From the form, the calendar or the signup to a lead with an owner, a campaign and a reply.

  • Lead intake from every door

    A form fill, a booked call and a product signup all arrive as one kind of record, with the right acknowledgement and nothing typed by hand.

    • Record types that keep each brand or product's funnel apart
    • An auto reply picked by record type and sent from a verified address
    • A failed email noted on the lead instead of blocking the save
    Record TypesFlowOrg-Wide Email AddressesCal.com

    In productionRunning in our own Salesforce org: the site form, the calendar and the product signup each create a Lead sorted by record type, and a failed auto reply never stops the Lead from saving.

  • Campaign attribution by UTM

    Every paid lead is credited to the campaign that brought it, so spend is judged on pipeline instead of clicks.

    • A UTM key on each Campaign that paid links must match
    • One campaign membership per lead, never a duplicate
    • Click ids and the landing page kept on the lead for a later conversion upload
    CampaignsFlowGoogle AdsReports

    In productionRunning in our own Salesforce org: each Lead that arrives with a UTM campaign joins the Campaign whose key matches, once, and a new campaign needs a key, not a flow change.

  • Owner assignment and round robin

    Every new lead gets an owner as it saves, by rules your sales leader can read, so nothing sits in a queue nobody watches.

    • Round robin across reps, weighted by capacity and skipping anyone out of office
    • Rules by segment, region, product or account owner, kept in a table an admin edits
    • A reassignment when the owner has not touched the lead inside your response window
    FlowLead Assignment RulesQueuesCustom Metadata Types
  • Territories

    Accounts sit in the territory your sales plan says, and a territory change moves the accounts, open deals and reports together.

    • A territory model by region, segment or industry that matches the sales org
    • Assignment rules that place new and existing accounts
    • A planned move when reps join, leave or change patches
    Enterprise Territory ManagementTerritory assignment rulesReports

Qualify and follow up

What happens after the first touch decides whether the lead becomes a deal.

  • Lead status and disqualification reasons

    Every lead moves through statuses that mean one thing, and a lead marked unqualified says why, so marketing can see which sources waste time.

    • A status path for each lead type, from new to qualified
    • A required reason, checked only when the status changes, so older leads stay editable
    • Follow-up tasks closed when a rep logs the email
    PathValidation RulesFlowTasks

    In productionRunning in our own Salesforce org: a Lead cannot be marked Unqualified without a reason, and logging an email to the Lead closes its oldest open follow-up task.

  • Duplicate rules and lead conversion

    A returning buyer is matched to the lead, contact and account you already have, so two reps never work the same company.

    • Matching rules on email, company domain and phone that warn or block at entry
    • Conversion that attaches to the existing account and contact
    • Lead fields mapped to the opportunity, so the deal starts complete
    Matching RulesDuplicate RulesLead field mappingFlow
  • Sales cadences

    Every rep follows the same calls and emails after a first touch, and the sequence stops when the buyer replies or books.

    • Steps of calls, emails and tasks by lead type
    • An exit on a reply, a booked meeting or a status change
    • Templates and call notes kept on the record
    Sales EngagementEmail TemplatesFlow
  • Lifecycle email from Flow

    Signups get timed emails for setup, first value and quiet spells from Salesforce itself, with no separate marketing platform.

    • Timed paths that start from dated fields on the record
    • One send step that reads the record again and checks opt-out at the moment of sending
    • A journey view of sent, opened, replied and bounced for each email
    FlowEmail TemplatesOrg-Wide Email AddressesLightning Web Components

    In productionRunning in our own Salesforce org: signup, setup, plan and quiet-user emails all go through one send step that checks opt-out at the moment of sending, and a fault marks the send failed instead of breaking the save.

Run the pipeline

Stages, forecast and quotes that mean the same thing to every rep and to leadership.

  • Opportunity stages and automation

    Each stage means the same thing to every rep, and a deal cannot move on until the step that defines it is done.

    • Stages with exit criteria and guidance on the path
    • Required fields at the stages that matter
    • Tasks, alerts and handoffs when a deal moves or stalls
    PathValidation RulesFlowOpportunity Teams
  • Forecasting

    Leadership reads commit, best case and pipeline by rep and quarter from the same numbers reps update, not from a spreadsheet.

    • Forecast categories mapped to your stages
    • Quotas by rep and period, rolled up by manager
    • Manager adjustments and a view of what changed since last week
    Collaborative ForecastsQuotasForecast hierarchyReports and dashboards
  • Quotes and approvals

    Reps build a quote from the price book, a discount past their limit goes to the right approver, and the signed quote lands on the deal.

    • Products and price books with the discount rules you sell by
    • Approval steps by discount, term or deal size
    • A quote PDF sent for e-signature, with the signed copy on the opportunity
    Products and Price BooksQuotesApproval ProcessesDocuSign
  • Pipeline views leadership reads

    One home page shows new leads, working leads, leads going cold and open deals, so the weekly meeting starts from the same numbers.

    • A going-cold report for leads with no recent activity
    • New, working and open-opportunity tiles split by brand or team
    • Disqualified leads by reason and source
    Reports and dashboardsLightning App BuilderLightning Web ComponentsApex

    In productionRunning in our own Salesforce org: a Lead Desk dashboard and a Sales home card show new, working and going-cold Leads and open opportunities, split by brand.

Bill, renew and see usage

For product companies: what the customer did in the product and pays for, beside the deal.

  • Lifecycle stages from product facts

    Sellers see whether a signup set up, reached first value or went quiet, worked out from dated facts instead of a picklist someone forgot to change.

    • Signup, connected, activated and last active as dated fields
    • A strict rule for what counts as activated
    • A product id on the record that can be set once and never edited
    External IdValidation RulesApexReports

    In productionRunning in our own Salesforce org: the product writes signup, connected, activated and last active dates on each Lead by a user id that cannot be edited, and the Sales home works out the stage from them.

  • Billing on the record

    Sellers and success see subscription status beside the pipeline, and a plan change starts the right email without anyone exporting from Stripe.

    • Subscription status and the Stripe customer id on the record
    • Stripe customers linked to the right lead from whichever side saves last
    • Paid defined by an active subscription, with Stripe kept as the billing source of truth
    StripeStripe app for SalesforceFlow

    In productionRunning in our own Salesforce org: subscription status from Stripe sits on each product Lead, and a subscription turning Active sends the welcome email for the paid plan.

  • Product usage where sellers work

    Reps see which apps a customer connected, what credit is left and when they were last active, without asking the product team for an export.

    • A few usage facts on the record for reports and flows
    • A live usage panel on the home page that stores nothing in Salesforce
    • Permission checked inside the Apex, not only on the page
    ApexNamed CredentialsLightning Web ComponentsCustom Permissions

    In productionRunning in our own Salesforce org: apps connected, credits left and last activity sit on each product Lead, and a usage tab on the Sales home reads live numbers and stores none.

Keep the org shippable

The work above lasts only if changes reach Production safely.

  • A release path your team will follow

    Every change is tested in a sandbox before one button ships it to Production, and the team channel hears about each step.

    • Developer sandbox, then UAT, then Production, with git as the record
    • Only the tests for the code that changed, and refusals for the risky cases
    • To take a change back, revert it on a new branch and ship it like any other
    GitHub ActionsSalesforce CLISandboxesDiscord

    In productionRunning in our own Salesforce org: changes move from a developer sandbox to UAT to Production by button, run only the related tests, refuse a branch that merged UAT, and post each step to Discord.

    Screens are drawn for illustration with made-up data, and none of them shows a client's org.

    ★★★★★
    Gray has been a pleasure to work with and was instrumental in helping us build our system almost entirely from scratch. He is punctual, communicates effectively, and is thoughtful in his approach to finding solutions.
    Tort Experts

    Sales Cloud in our own org

    We run consulting, marketing and a software product from one Salesforce org, so our own Sales Cloud has to do what we build for clients. A lead from the site form, the calendar or a product signup lands with its record type, its campaign and an acknowledgement from the right brand. Product signups carry dated facts from the product, and the Sales home works out each person’s stage from them. Lifecycle emails go through one send step that checks opt-out at the moment of sending. Changes reach Production through a sandbox, UAT and one button, with a notice in Discord at each step. Read how we tie every ad lead to a campaign

    AI on Sales Cloud

    Agents and assistants work inside the same permissions and record rules as your reps. These pages cover the ones we connect to Salesforce.

    • AI and Agentforce consultingAgentforce agents on leads and cases, the Flex Credit forecast and the first use case worth shipping.
    • Claude and SalesforceConnecting Claude to Salesforce through MCP: setup steps, security and costs.
    • ChatGPT and SalesforceConnecting ChatGPT to Salesforce through MCP, with the connected user's permissions applied.
    • ApexGeniusThe Salesforce MCP product we build and run. It keeps your apps, skills and memory in one connection, so your whole setup goes with you from agent to agent.

    Works with

    Go deeper

    Questions

    Do you build Sales Cloud from scratch or fix the org we already have?

    Both. Most teams come to us with an org that grew one fix at a time, and the work starts by reading it: the flows, the assignment rules and the fields reps actually fill in. A new org starts from how leads, deals and customers move, and is configured around that.

    Can you route leads by territory, round robin and capacity at the same time?

    Yes. The rules sit in a table an admin can read and change, so a new rep or a new region is a row, not a rebuild. Territory rules pick the patch, round robin picks the rep inside it, and a reassignment catches leads nobody touched in time.

    Do we need Sales Engagement, CPQ or another add-on?

    Not always. We start with what your edition already includes and recommend an add-on only when the work needs it, for example when your quoting rules outgrow standard quotes and approvals.

    Can lifecycle and follow-up emails run from Salesforce without a marketing platform?

    Yes, for timed emails tied to what a person did. Flow sends them, every send checks opt-out at that moment, and a journey view shows what was sent, opened, replied to and bounced. A marketing platform still earns its place for large newsletters and design-heavy campaigns.

    How do changes reach Production without breaking what reps use every day?

    Each change is built in a developer sandbox, tested in a UAT sandbox and shipped by one button that runs only the related tests. To take a change back, we revert it on a new branch and ship that the same way.

    What does it cost?

    Scope sets the price. We break the work into pieces that each ship on their own, so you fund the next working piece of the system. A first call ends with a clear read on what to build first, whether or not we build it together.

    Show us where deals slip between the first lead and the close.

    Prefer to talk it through?

    Pick a 30-minute time with Gray. Bring the report nobody trusts.

    Loading available times…