Sales and marketing need one shared source of truth. That was the reason for bringing the Filo workflows into HubSpot: the work needed to connect across the two teams.
My background spans acquisition, CRM work, measurement and, more recently, building prototypes with AI assistance. The connection is what happens between those activities.
A campaign can create a response. Someone still needs to understand it, decide who should act and follow it through. A report needs to help someone choose what to do next. A prototype needs to give another person something meaningful to evaluate.
That is the thread I see across work that can otherwise look like a list of unrelated tools.
Following the response beyond the landing page
At Filo, my work included lead qualification, scoring and attribution workflows using Unbounce, Pipedrive, Zapier and webhooks. I later migrated and rebuilt those processes in HubSpot. Campaigns and CRM work were both part of my role.
The aim was a common operational record for sales and marketing. That does not mean an advertising platform, website analytics and a CRM will always report the same number. They observe different things. The shared record should make it easier to discuss the same enquiry and its progress, while keeping those measurement differences visible.
At KPI6, my responsibilities combined SEO, paid acquisition, HubSpot optimisation and performance reporting, alongside leading a team of three marketers. At Fitprime, the work included enterprise lead generation, outbound processes and CRM.
Those are different companies and assignments. I would not turn them into one universal playbook. But they give me a concrete starting point for discussing the connection between attracting interest and making that interest useful to a business.
If we are reviewing a campaign, I want to understand what happens after someone responds. What information arrives? What counts as a relevant enquiry? Who owns the next action? Can the team see whether the opportunity progressed?
The answer may still be to change the campaign. Following the response simply gives us a better basis for deciding.
A system that someone can actually use
My independent work has included Zoho CRM setup and automation for a tour operator, and HubSpot implementation and client training for an advisory business.
The tour-operator working guide records a practical tension: standardise the response without making a prospective customer feel they have been ignored. Its discussion calls for replies to reflect details already supplied by the customer. The proposed approach uses a structured template with room for a personal response.
That document is useful because it shows a real design question. It also contains suggestions and unresolved points; I would not present every listed automation as something that was deployed. The distinction between a process we discuss and a process people actually use belongs in the account.
I can describe those as delivery. I cannot attach a revenue increase to them without evidence that supports it.
The distinction matters. Configuration, team adoption and commercial impact are different things. A workflow may be built correctly and still depend on someone entering information, reviewing an exception or following up. Training is part of making a system usable; it is not proof that every process changed as intended.
For a new engagement, I would want the useful action to be clear before making the workflow more elaborate. That might be assigning an enquiry, preserving its source, recording qualification or making a follow-up visible. The appropriate design depends on the problem and the people who will maintain it.
Reading gives me questions to bring to the work
One idea I return to in Lean Analytics, by Alistair Croll and Benjamin Yoskovitz, is that a metric should affect a decision. Applied here, the question is whether a reported result changes what the team does next.
Casey Stanton’s The Fractional CMO Method offers another useful lens: capacity, capability and cash. A team can understand the problem and still lack the time, skills or budget to pursue every reasonable improvement.
My KPI6 working notes already contained questions about expectations, team capacity and budget limits, alongside proposed customer research and demand-generation activity. Many entries were explicitly plans. They show what I was considering, rather than establish that every initiative happened or caused a reported result.
I want to use these ideas as questions rather than claim that a framework explains every project retrospectively. Which constraint is consequential now? What evidence would change the next decision? What can we test without committing the whole team to a rebuild?
Building something people can evaluate
AI-assisted development has widened the range of things I can turn into a working example.
For the Multimodal Learning Lab concept, I directed an AI-assisted build around a learning use case. The resulting static prototype brought together a diagram, written lesson content, English and Italian variations, and guided interactions.
Its limits are important to the account: the responses were curated. It was not connected to a live model or an official research-project integration. It did not establish improved learning or commercial demand.
What it provided was a concrete experience that someone could inspect and test. A next-stage pilot would need to establish whether the experience helped its intended users and whether the work required to produce it made sense.
That is where I see the value of building alongside strategy. A working example can make assumptions visible sooner. It also creates a responsibility to explain what works, what is simulated and what remains unknown.
Connecting the work
The question I want to carry across campaigns, CRM and prototypes is: what should happen next, and what would tell us that it helped?
Sometimes the next step is a campaign test. Sometimes it is a clearer handoff or a simpler report. Sometimes it is making a small solution that another person can try.
I want my body of work to show those decisions in enough detail that someone can judge the work, including where the evidence ends.
Read about the Filo workflow, KPI6 and CRM delivery, or discuss your situation.
Reading behind this note
The discussion draws on Lean Analytics by Alistair Croll and Benjamin Yoskovitz and The Fractional CMO Method by Casey Stanton. These are attributed lenses for my present interpretation, not claims that the books caused the historical work.