Imagine a question, invented for this article, that reaches a support team. A customer asks whether the product can produce a specific report that their auditor now requires. Support answers as well as it can and closes the ticket.
The same question could matter elsewhere. If several customers in one sector are asking it, marketing might want to adjust how the product is positioned for that sector. Sales might want to address it when preparing for meetings with similar prospects. Product might need to decide whether it belongs on the roadmap. In many organisations none of that happens, not because people are careless, but because the question lives in one system and the decisions live in others.
More signals, not more clarity
Commercial organisations are rarely short of data. Support tickets, call notes, website behaviour, reasons for winning or losing deals, usage data and market news all generate signals. The difficulty lies in turning them into something teams can act on together, and that requires distinguishing between several things that are often blurred.
From signal to action
Incoming signals are raw observations: a ticket, a remark in a sales call, a drop in usage, a competitor’s announcement. They are useful, but on their own they say little about what is true or what matters.
Reviewed knowledge is what remains after someone has checked, combined and interpreted signals. “Several customers in regulated sectors need this report” is knowledge; a single ticket mentioning it is not. Knowledge needs an owner and a date, because it goes out of date.
Go-to-market (GTM) choices are the decisions that guide commercial work: which customers to target, how to position the offering and what the proposition promises. They should draw on knowledge, but they remain choices, made by people with the authority to make them.
Prepared actions are concrete pieces of work that follow: a draft support response, a briefing for a sales meeting, a summary of feedback for a product review. They can be prepared with software, including AI, provided they are grounded in the right knowledge and choices.
Human approval and feedback close the loop. Someone accountable decides whether a prepared action is sent or used, and the outcome, whether the customer was helped, the meeting went well or the feature was adopted, feeds back into the knowledge.
Why a CRM record is not a strategy
Customer relationship management (CRM) systems and support tools remain essential. They record interactions, manage pipelines and keep track of cases. But a CRM record describes what happened with a customer. It does not establish what the organisation has decided about target segments, positioning or priorities. Where that shared basis is missing, each team fills the gap with its own interpretation, and the same customer may hear different stories from marketing, sales and support.
The GoToM8 approach
GoToM8, a venture in development at Xablu Venture Studio, is built around this gap. Its approach is a shared GTM foundation that combines strategy, validated knowledge and current signals, and sits above the existing software stack rather than replacing it. Teams keep using their CRM and support tools; the foundation is intended to give them a common reference for what signals mean and what to prepare next, with people approving the actions that matter. View GoToM8
GoToM8 currently has an interactive product prototype and is in commercial validation. Which workflows, teams and integrations it suits best is part of what that validation is meant to establish.
Quality before automation
It is tempting to start with automation and let software draft responses or briefings straight away. But automated preparation is only as good as what it draws on. If source data is incomplete, knowledge is unreviewed or nobody owns the GTM choices, automation spreads inconsistency faster.
Three questions are worth answering first. Which sources are reliable enough for this purpose? Who reviews knowledge before it is used, and how often? And who owns each GTM choice, so that prepared actions can be checked against something agreed?
Where to start
A practical starting point is one workflow that crosses team boundaries. Support-response preparation is one candidate: which knowledge should a response draw on, which signals show that a question is recurring, and who approves responses that touch on positioning or commitments? Turning customer feedback into product insights is another: which feedback counts, who combines and reviews it, and how does the product team report back on what it decided?
Starting small makes the requirements visible. It shows which knowledge is missing, where ownership is unclear and whether shared context actually changes what teams do.
Is there a workflow in your organisation where marketing, sales, support or product depend on each other but work from different information? Choose one, and identify the knowledge, signals and review responsibilities it needs. That is where a useful conversation with us can start.
Discuss a cross-team workflow →