Salesforce consulting at Slalom
At Slalom, Gray worked inside multidisciplinary Salesforce delivery teams, building the consulting foundation he later carried into operating roles.
Lead intake, routing, attribution, and lifecycle, connected across Salesforce, HubSpot, and the tools bolted to them.


Tell us which number nobody believes, or which handoff keeps failing. We will reply with the first questions we would answer and where we would look.
By submitting, you agree that GAT Solutions may contact you about this request. We do not sell your information.
★★★★★“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.”
★★★★★“GAT has been a pleasure to work with, and has been instrumental in helping us build our system almost entirely from scratch. They are punctual, communicate effectively, and are thoughtful in their approach to finding solutions.”
★★★★★“Gray and GAT were a pleasure to work with, knowledgeable about Salesforce and software development in general. They were able to complete client projects and always exceeded expectations. Would highly recommend them again!!!”
★★★★★“We engaged GAT Solutions to support a complex GTM technology environment centered on Salesforce and HubSpot. The team quickly learned how our lead intake, routing, attribution, lifecycle, and integrations worked, then looked across the full process to identify root causes instead of treating every issue as a separate ticket.”

Gray is GAT’s Lead Consultant and stays hands-on with the discovery, the data model, and the decisions that change what a report means. He works across your marketing and sales tools rather than inside one of them, because that is usually where go-to-market problems actually live.
Our administrators, developers, and integration specialists own the build in their disciplines. Gray keeps the business context and acceptance criteria connected while the GAT team carries each change through testing, documentation, and production.
At Slalom, Gray worked inside multidisciplinary Salesforce delivery teams, building the consulting foundation he later carried into operating roles.
He then moved to Rula, where he architected and built patient-operations systems for patient processing and revenue operations, then owned the Salesforce workflows and operating path behind them.
After Rula, Gray joined Cribl, where his work included support operations, community access, and the production systems behind them.

After Cribl, Gray moved full time into GAT, where he leads delivery and continues to build ApexGenius, GAT’s Salesforce admin MCP for Claude and ChatGPT.
We follow a real lead through your actual stack before proposing anything. The tools differ at every company. The questions do not.
Forms, calls, chat, events, and partner sources, including the ones nobody documented.
Assignment rules, ownership, SLA timers, and the moment a lead goes quiet.
Source stamping, UTMs, dedupe, and why two systems disagree about the same account.
What each stage means, who moves it, and which transitions happen by hand.
One documented view of the revenue system, with the assumptions written down.
A revenue system your team can explain, and numbers your leadership stops arguing about.

Gray is GAT’s Lead Consultant and stays hands-on with the discovery, the data model, and the decisions that change what a report means. He works across your marketing and sales tools rather than inside one of them, because that is usually where go-to-market problems actually live.
Our administrators, developers, and integration specialists own the build in their disciplines. Gray keeps the business context and acceptance criteria connected while the GAT team carries each change through testing, documentation, and production.
At Slalom, Gray worked inside multidisciplinary Salesforce delivery teams, building the consulting foundation he later carried into operating roles.
He then moved to Rula, where he architected and built patient-operations systems for patient processing and revenue operations, then owned the Salesforce workflows and operating path behind them.
After Rula, Gray joined Cribl, where his work included support operations, community access, and the production systems behind them.

After Cribl, Gray moved full time into GAT, where he leads delivery and continues to build ApexGenius, GAT’s Salesforce admin MCP for Claude and ChatGPT.
Two systems hold overlapping records and nobody can say which one is right.
Pipeline source reporting exists, but leadership discounts it when making decisions.
Marketing hands off, sales picks up late or not at all, and the gap is invisible.
The same class of problem keeps returning because the cause was never found.
Demand generation is a different job. We fix what happens after the lead arrives.
If the work is continuous and internal, hiring usually beats engaging a firm.
We work best when GAT owns an agreed outcome, not only a block of hours.
The title usually means someone who builds and maintains the systems that carry a go-to-market motion: intake, routing, enrichment, attribution, lifecycle, and the integrations between them. That is the work we do. The difference is that GAT brings a team rather than one person, so administration, development, integration, and architecture are covered without a single hire.
Yes. Most revenue problems we are asked to fix live in the seam between a marketing platform and a CRM, so working in only one of them tends to move the problem rather than solve it. We work across both and the tools connected to them.
No. We usually work alongside an internal RevOps or marketing operations owner, take an agreed part of the system, and hand it back documented. Where there is no internal owner yet, we can carry it until there is.
With discovery and an audit before any build. We follow real records through the live systems rather than working from a diagram, because the documented process and the running process are rarely the same thing.
Then we say so. A meaningful share of what we find is process or ownership rather than software, and reporting that honestly is worth more than a build nobody needed.
We read it, reply with the first questions we would answer and where we would look, and tell you whether this work, a scoped implementation, or something else fits better. You can also pick a time on this page if you would rather talk it through.
We will follow it back through intake, routing, attribution, and lifecycle until the cause is visible. You will get a documented view of the revenue system either way, and a clear recommendation about what to change first.
Tell us which number nobody believes, or which handoff keeps failing. We will reply with the first questions we would answer and where we would look.
By submitting, you agree that GAT Solutions may contact you about this request. We do not sell your information.