The 7 systems a GTM Engineer builds first
A GTM Engineer (Go-To-Market Engineer) designs and installs the AI and automation systems that serve acquisition, sales and client relationships. I do not carry that title: it is a way of working I practise as an entrepreneur, and this is where I start. The seven below come first in a B2B or premium business because they act directly on revenue, they go live in weeks rather than quarters, and they keep the salesperson at the centre of the relationship. They follow the order of the pipeline, from the enquiry that lands to the client everyone forgot.
1. A first reply within minutes (speed-to-lead)
The symptom shows up in the shared inbox on Monday morning: enquiries from Friday evening and Saturday, still unanswered. The prospect wrote to several companies, and the first one to reply with something useful got the meeting. The time between an enquiry arriving and its first useful handling is called speed-to-lead.
The system timestamps every enquiry whatever the channel, works out what is being asked, answers with information checked against your own sources and offers a next step: a qualifying question, a slot, a call back. When the information is missing, it says so and hands over.
The salesperson keeps the substance: price, exceptional availability, a commercial gesture, anything that commits the company. The first reply opens the conversation; it does not close it.
You know it works by tracking the median time to first useful reply and the slowest tenth, per channel, week after week. Enquiries that never get an answer should trend towards zero.
The classic trap is the automatic acknowledgement. It improves the metric and gives the prospect nothing. A reply counts when it carries information or opens a next step.
2. Qualification and routing to the right salesperson
Symptom: the same prospect gets called twice by two people, or nobody calls because each assumed someone else had it. Off-target enquiries occupy your best seller while the good ones wait.
The system asks the two or three questions that decide what happens next (sector, size, need, timing, according to criteria you have written down), classifies the enquiry and assigns it to a named owner with a deadline to pick it up. The CRM receives the complete record and the history of the exchange.
Humans keep the definition of the criteria and the final say on borderline cases. An ambiguous file is passed on with a recommendation, never a verdict.
The measure: the share of enquiries assigned to the right person first time, the time between assignment and first human contact, and the number of files reassigned by hand.
The trap: the form in disguise. Ten questions before anyone talks to you, and the prospect leaves. Ask only what changes the next action.
3. Booking with confirmation and reminders
Symptom: the sales calendar shows booked slots that never took place. Each no-show cost a preparation, a time slot and, often, a prospect who will not come back to explain.
The system offers real slots taken from the calendar, confirms through the channel the prospect used, sends a reminder the day before and on the morning itself, and offers to move the meeting rather than cancel it. On the day, the salesperson has the file and the context in front of them.
Humans keep the meeting itself, and the choice of who takes it. A director who asks to meet in person should not be handed a video link by default.
The measure: meetings held as a share of meetings booked, and the time between the enquiry and the first accepted slot.
The trap: the reminder that reminds of nothing. A useful reminder restates the time, the place or the link and the name of the person, and offers an honest way out: reschedule in one click.
4. Following up open quotes and proposals
Symptom: quotes sent three weeks ago, no answer, no follow-up, because the salesperson moved on to other files. Nobody knows how many proposals are sleeping or what they add up to.
The system keeps the register of open proposals, knows the date sent and the validity date, and prepares the follow-up at the right moment with the right content: a question, a complement, an offer to talk. It flags to the salesperson every file that no longer has a next action.
Humans approve any follow-up that touches price, terms or a sensitive client. They also keep the right not to follow up.
The measure: the share of proposals that receive an answer (yes, no or later) before their validity date, and the average age of quotes still open.
The trap: the mechanical chase at day 7, day 14, day 21, identical for everyone. It shows, it irritates, and it teaches the prospect that nobody is really following their file.
5. One memory of the file across every channel
Symptom: a prospect filled in a form, rang the switchboard, exchanged two emails and then walked into the showroom. At each step they told the whole story from the start. By the fourth time, they understood the company did not remember them.
The system attaches every interaction to a single file: form, email, call, message, visit. It produces an up-to-date summary anyone on the team can read before picking up the phone or replying. The CRM becomes the single source, and it is actually filled in.
Humans keep the relationship and the judgement about what gets said. The system spares the prospect from starting the conversation over.
The measure: how often a prospect has to repeat something they already gave, observed on a sample of exchanges, and the share of interactions actually attached to the right file.
The trap: believing an installed CRM is enough. Without automatic attachment, the CRM gets filled in when someone has time, which is to say rarely.
6. An assistant before and after every exchange
Symptom: the salesperson walks into the meeting with the memory of the last call and nothing else. Walking out, they have three things to do; they write down one, and the rest lives in their head until the next file erases it.
Before the exchange, the system prepares a brief: who, what need, what has already been said, what is still open, which documents were sent. Afterwards, it drafts the meeting notes from the salesperson's notes or from the recording if the client agreed, proposes the next action and enters it in the CRM with a date. The salesperson reads, corrects, approves.
Humans keep the words and the commitment. The notes go out once they have been read, and a promise made in a meeting remains theirs.
The measure: the share of meetings with a dated next action in the CRM the same day, and the time salespeople say they spend on data entry.
The trap: the summary that invents. A synthesis must stay tied to the notes or the recording, and flag what it did not understand rather than fill the gap.
7. Reactivating dormant prospects and clients
Symptom: the database holds contacts who said "not now" a year ago, and clients whose last purchase is older than that, and nobody gets back to them, for lack of time and of a precise reason.
The system spots files with no interaction for a period you set, retrieves the context of the last exchange and offers the salesperson a reason to get back in touch: a need expressed at the time, a deadline mentioned, something new that fits the file. It drafts the message; the salesperson sends it or declines.
Humans keep the choice of contacts and the tone. A client you wake up should feel remembered, not pulled off a list.
The measure: the response rate to these renewed contacts, and the meetings or orders that follow, compared with the same base left alone.
The trap: the mass campaign in disguise. Reactivating means picking up an individual conversation. A hundred identical messages sent the same day reactivate nothing and damage the base.
Which one first?
The one that leaks most. Take one week of enquiries, quotes, meetings and dormant contacts and count: how many enquiries went more than a few hours without an answer, how many meetings did not take place, how many quotes passed their validity date without a follow-up, how many contacts were left to drift. The number that hurts most names your first system.
Each one is built alone, measured alone, and prepares the next: the first reply feeds qualification, qualification feeds the meeting, and the shared memory of the file holds the whole thing together. One system at a time: with several open at once, you will not know which one produced the result.
The next step
If one of these seven symptoms sounds familiar, the services page describes what each system contains, and the method page how it is scoped, installed and measured. One week of counting is enough to know which to open first.
Published on · Updated on