The teams that win new business in the next few years will be the ones that reach the most of their market with messages that make sense to the people reading them. That used to be impossible. You could reach a lot of people badly or a few people well. AI changed that trade-off, and most go-to-market teams haven’t caught up yet.
Periti Digital is a HubSpot Elite Solutions Partner and a certified partner in the Anthropic Claude Partner Network. We build go-to-market engines for companies with 200 to 2,000 employees, combining HubSpot, Claude, enrichment and sending tools, and everything you already know about your customers. Our teams work across Europe and the US from Dublin, London, Rotterdam, Munich, Lisbon, Boston and New York.
This page explains how we think about go-to-market engineering, where most outreach programs go wrong, and what we do differently. It isn’t a guide to email sequencing, and it doesn’t cover phone prospecting.
For years, the expert advice on outbound was to send fewer, better messages. That advice was right. Researching an account properly took an SDR 20 minutes or more, so the only way to send good copy was to send less of it.
That constraint is gone.
Claude can read a company’s website, its job posts, its latest acquisition announcement and your own history with companies like it, then write a message that makes sense to the specific person receiving it. It can do that for ten thousand accounts as easily as for ten.
So our position is simple. If you can send excellent copy to your ideal customer profile, volume is the only way to go. Every account in your market that doesn’t hear from you is an account your competitor gets to first.
The catch is the word “excellent.” Volume with generic copy burns your domains, annoys your market and teaches buyers to ignore you. Volume is the reward for getting context right. It’s never a substitute for it.
Most of the companies we talk to already own the tools. They have Clay for enrichment, Instantly for sending, HubSpot for the CRM and maybe a few AI writing tools on top. Each one was bought by a different person to solve a different problem.
None of it shares a central theme or a business case.
Enrichment data sits in Clay tables nobody maintains. Sequences run in Instantly with copy written once and never revised. Replies don’t make it back into HubSpot, so nobody can tell which campaigns produce pipeline. Leadership sees activity numbers and no clear return.
There’s a bigger problem underneath. For the last decade, everyone bought the same tools and ran the same playbooks, so everyone sounded the same. Buyers learned to spot a templated sequence in the first line.
Tools are no longer the advantage. The advantage is the context only you have, built into a stack designed around it. Nobody else has your closed-won history, your customer relationships or your understanding of why people buy from you. When that context drives every message, your outreach can’t be copied.
That’s what we build: one engine with HubSpot at the center, Claude as the intelligence layer, and the rest of the stack chosen to serve a single business case.
Your best source of outbound messaging is the business you’ve already won.
Every deal you’ve closed tells you something: which industries buy, which job titles sign, which problems trigger a project, how long it takes, and what the customer said when they chose you. Most companies have years of this sitting in HubSpot, their ERP and their invoicing system, and almost none of it reaches the outreach team.
We change that. Our strategists work with you to get the most out of the data you already have. Everything we know about your ideal customer feeds the messaging and the shape of the ICP:
This is our wider point of view in action: Model + Context + Application. Claude is the model. Your customer history is the context. HubSpot and the sending stack are the application. Agents and automations are only as good as the context underneath them, and context is the part your competitors can’t buy.
The best time to reach a company is when something has just changed. We build trigger-based outreach that watches the market for those changes and acts on them within days, not quarters.
| Signal | What it usually means | What the outreach does |
| Hiring for revenue, operations or IT roles | A team is growing or a function is being rebuilt | Speaks to the problem the new hire is being brought in to fix |
| A new sales, marketing or RevOps leader | Budget and priorities are about to be reset | Reaches the new leader in their first 90 days, with a relevant point of view |
| Mergers and acquisitions | Systems, teams and data need to be combined | Addresses consolidation, integration and reporting across the new group |
| Divestments and carve-outs | A business needs its own systems, fast | Offers a path to standing up independent infrastructure |
| Funding rounds or new investors | Growth targets just went up | Connects the new targets to the capacity needed to hit them |
| Expansion into new markets or regions | New teams, languages and processes | Speaks to scaling the playbook without losing control |
| Technology changes | A platform is being replaced or added | Positions your offer around the change already underway |
| A former customer contact changes company | A warm relationship at a new account | Reopens the conversation with shared history |
Signals come from your enrichment tools, from HubSpot’s own data and from Claude reading public sources directly. The point isn’t to collect signals. It’s to decide in advance what each one should trigger, then let the engine act on it every time.
We build with the latest tools, and we change them when something better comes along. What stays constant is the design: HubSpot holds the truth, Claude does the thinking, and everything else serves those two.
| Layer | Tools we use | What it does |
| System of record | HubSpot Smart CRM, sequences, workflows, reporting | Holds every account, contact, touch and reply, so every campaign can be measured |
| Native HubSpot AI | Breeze Prospecting Agent, Breeze Intelligence, Breeze Data Agent | Monitors buying signals, enriches records and drafts outreach inside HubSpot |
| Intelligence layer | Claude via the Claude API and Claude Console, Claude Code | Researches accounts, interprets signals and writes copy grounded in your customer context |
| Enrichment and signals | Deepline, Clay, HubSpot Breeze Intelligence | Finds the right companies and contacts, and watches for trigger events |
| Sending at scale | Instantly and LinkedIn outreach tools | Delivers high-volume email and social touches with proper domain and deliverability management |
| Orchestration | Microsoft Azure, Amazon Web Services, Make, Zapier, Claude Code | Connects it all, with business-critical flows on Azure or AWS |
Anyone can buy this stack. Plenty of companies have. Without a strategy behind it and people executing it every week, it produces a lot of activity and very little pipeline.
The value comes from the decisions: which segment to start with, which signals matter, what the messaging should say and to whom, how many touches each account gets, and what to change when the numbers come back. That’s consulting and execution work, and it’s what we do.
HubSpot’s Breeze Prospecting Agent is a good tool, and we use it. It works best on data that already lives in HubSpot. Claude comes in when the context you need sits outside it, or when you need control over the reasoning and the copy at real volume.
| Approach | Where we use it |
| Breeze Prospecting Agent | Signal monitoring and outreach drafting on accounts already in HubSpot, for teams starting out with AI prospecting |
| Claude via the Claude API | Large addressable markets, custom research, copy grounded in context from outside HubSpot, and campaigns across thousands of accounts |
| Both together | Most mature programs, with HubSpot running the record and the sequences and Claude doing the heavy research and writing |
Everything on this page runs Periti’s own go-to-market before we build it for a client. We use Claude to research accounts, interpret signals, draw on our history with companies like the prospect and write outreach that reads like it was written for one person. When a cheaper or faster tool appears, we test it on our own pipeline and switch if it wins.
Our own tests with this stack have returned ROI in the thousands of percent. We tested the approach with our own pipeline and our own money before asking you to trust it with yours.
Our biggest GTM engineering client is the highest-spending AI credits customer in the HubSpot ecosystem.
We started by mapping their entire addressable market. Then we designed an outreach program built specifically for their buyers and laid out over 12 months, so they knew in advance how many touchpoints every account in the market would receive and when.
Before these AI tools, there was no way to do that across thousands of accounts. The research alone would have needed a building full of SDRs.
The results have been outstanding. They’ve cut their SDR and BDR overhead significantly and their bookings have risen sharply. That’s the shift we mean when we call go-to-market engineering the next generation of marketing.
This is usually the first question a CRO asks, so here’s a straight answer.
No SDR team can reach as many people, in as many relevant ways, as a well-built AI engine. The math doesn’t work. An SDR can research and write maybe a few dozen good messages a day. The engine does that for your whole market.
What the engine doesn’t have is the personal touch. That’s where your people come in. One SDR attached to a system like this delivers far more return than a full team doing the research and writing by hand. They spend their time on replies, conversations and meetings instead of tabs and templates.
For most of our clients, the result is a smaller, better-paid SDR function with much higher output. We’ll help you plan that transition honestly, including what it means for the people already on the team.
When we talk about go-to-market engineering, we mean a 12-month commitment to changing how you engage with your market. Anyone selling it as a three-week setup is selling you a tool installation.
It works like this. We form hypotheses about which segments, signals and messages will produce pipeline. We test them through campaigns. We read the results, gather feedback from your sales team, refine the messaging, and suggest new strategies when the data points somewhere unexpected. Then we do it again.
The models change too. Claude and the other frontier models improve every few months. Part of our job is upgrading your engine as they do, so you’re not running last year’s capability against competitors using this year’s.
That’s why we see GTM engineering as a partnership rather than a service. A Periti go-to-market strategist and our team work for your team on a fractional basis. You get senior GTM thinking, engineering and execution without hiring a department.
Some requests we’ll challenge, and a few we won’t take on.
A single campaign can book meetings. A go-to-market engine takes a year of testing to get right, and we’ll tell you that up front.
Every GTM engineering partnership is led by a Periti go-to-market strategist who works as part of your team. They own the strategy, the testing plan and the messaging, and they meet your sales leadership regularly to review what’s working.
Behind them, dedicated engineers and Claude Certified Architects build and maintain the engine: the Claude workflows, the enrichment and signal layers, the HubSpot configuration and the integrations that tie it together.
Our directors bring up to 30 years of CRM consulting experience and review the work to the same standard as every other Periti project.
Design and Strategy. We map your market, your ICP and your customer history. We decide which signals matter, which segments to start with and what success looks like in pipeline terms, not activity terms.
Build. We connect HubSpot, Claude, enrichment and sending tools into one engine, design the data flows and set up reporting so every touch is measured.
Launch. We start with a defined segment and a small set of signals, warm up sending infrastructure properly and get the first campaigns into market.
Test and refine. Every month, we review results with your team, retire what isn’t working, double down on what is and introduce new campaigns and strategies.
Upgrade. As frontier models and GTM tools improve, we bring the improvements into your engine.
Already on HubSpot.
Most of our GTM engineering work starts with a Design and Strategy project. If your HubSpot data isn’t in shape to power outreach, that’s where we’ll focus first.
Not on HubSpot yet.
LaunchRight, our industry-specific onboarding package, gets you onto a proven HubSpot setup fast, with a foundation that can carry a GTM engine later.
GTM engineering pays off fastest for companies with a large addressable market and a sales cycle that rewards being early.
| Situation | What the engine does |
| An expensive SDR team with flat results | Takes over research and writing, so fewer people produce more meetings |
| A large market you can’t cover | Maps every account and plans touches across all of them over the year |
| Years of customer data nobody uses | Turns closed-won history into ICP, segments and messaging |
| Tools bought separately with no business case | Ties them into one engine with HubSpot at the center |
| New leadership with aggressive growth targets | Puts a measurable outbound motion in place within the first quarter |
| Private equity portfolios | Builds a repeatable GTM playbook that can roll out across portfolio companies |
Go-to-market engineering is the work of automating and systemizing how a company communicates with its market. At Periti, it means building one engine from HubSpot, Claude, enrichment and sending tools, fed by your customer context, and running it as a 12-month program of testing and refinement.
Yes, if the copy is excellent. The old advice to send fewer messages came from a time when good research was slow and expensive. With Claude doing the research and writing, you can send relevant messages to your whole ideal customer profile, and every account you don't reach is one a competitor will.
We use Claude through the Claude API and Claude Console to research each account, interpret the signal that triggered the outreach, and write copy grounded in your own customer history and case studies. Our strategists set the messaging framework, review output and refine it based on what gets replies.
Common triggers include hiring for specific roles, new leadership, mergers and acquisitions, divestments, funding rounds, market expansion and technology changes. We agree in advance what each signal should trigger, so the engine acts on it consistently and quickly.
Mostly, at the research and writing stage. One SDR working with a well-built engine typically delivers far more than a full team working manually. What AI can't replace is the human conversation once someone replies, so most clients keep a smaller, more focused team.
Often both. The Breeze Prospecting Agent works well on data already in HubSpot. Claude is the better fit for large markets, custom research and context that sits outside HubSpot. In mature programs, HubSpot runs the record and sequences while Claude does the heavy research and writing.
HubSpot is always at the center. Around it we use Claude, Deepline, Clay, Instantly and LinkedIn outreach tools, with Microsoft Azure or AWS for business-critical connections. We choose and change tools to fit your volume, budget and goals, because the tools are never the advantage on their own.
We typically work with clients for 12 months. The first campaigns can be in market within weeks, but the real value comes from testing hypotheses, refining messaging and upgrading the engine as models improve over the full year.
Your closed-won deals, lost deals, ERP and invoicing data show exactly who buys from you and why. When that context drives the ICP and the messaging, your outreach becomes something competitors can't copy, even if they own the same tools.
It helps a lot. If the data isn't trustworthy, the engine will spread bad assumptions at scale. Where needed, we start with a Design and Strategy project to fix the foundations before switching on volume.
Yes. The same approach can become a repeatable playbook across portfolio companies, with shared definitions and reporting so operating partners can compare outbound performance across businesses.
It can, if it's done badly. We manage sending infrastructure and deliverability properly, and nothing goes out until the copy reads like a person wrote it for the reader. Every program reports back into HubSpot so problems show up early.