Operate
Your role, iterating, the client
In this video
Everything the video says.
Lesson 1Not everyone does everything: the roles
Reality
Go-to-market engineering covers a lot: data, automation, AI, reporting, customers.
The problem
Trying to be the best at all of it at once is impossible.
What it costs
You become average at everything and excellent at nothing.
The idea
That is why roles exist. Each one takes a part of the work, and together they deliver the result.
How to do it
- Analyst: turns data into reports and decisions.
- Engineer: builds and automates, happiest with focus and no interruptions.
- Client-facing: the point of contact who understands and talks with the customer.
- Titles vary — go-to-market engineer, forward deployed engineer and others — but the parts of the work are these.
Example
On one project, the analyst finds the leak, the engineer builds the fix, and the client-facing person explains the result to the company.
Your turn
Which of these parts of the work do you enjoy most? Which do you avoid?
Lesson 2Find the role that fits your strengths
Reality
Many people pick a role for the title or the salary.
The problem
A role that goes against your nature drains you, even if you are capable.
What it costs
Low energy, slow progress, and work that never reaches its best.
The idea
Know your own values and strengths, and move toward the role where they work in your favor.
How to do it
- Notice what gives you energy: numbers, building, or people.
- Ask others what you are good at.
- Try each part of the work once, then choose on evidence.
Example
Someone analytical who hates meetings shines in reporting. Someone sociable who loves conversations becomes the client's point of contact.
Your turn
Write your top three strengths and the role they point to. Explain why.
Lesson 3Iterate: the scientific method applied to revenue
Reality
Your first version will not be perfect. Nobody's is.
The problem
Many people take a failure personally, defend the first result, or quit.
What it costs
Without iteration, the first mistake becomes the final result.
The idea
An iteration is one full cycle: try, measure, learn, adjust. A failure is not the end — it is data.
How to do it
- Change one thing at a time, so you know what caused the result.
- Write down what you tried and what happened.
- Do not marry a result. Marry the method.
Example
First version: messages sent in the morning got few replies. Iteration: send at midday. Result measured, learning recorded, next test decided.
Your turn
Describe one thing you tried that failed. What did the data teach you, and what would the next iteration be?
Lesson 4Stay ahead of the client's expectations
Reality
The client hired you with an expectation — sometimes clear, often not.
The problem
When the client finds problems before you tell them, trust breaks.
What it costs
A good result delivered as a surprise can still feel like a failure.
The idea
Always go one step ahead: set expectations early, report before they ask, and bring the bad news first.
How to do it
- Agree at the start what success looks like, in numbers.
- Send updates before the client asks for them.
- If something fails, say it first, with the data and the next iteration.
Example
"This week the contact rate dropped. We found the cause, here is the data, and this is what we are testing next." The client stays calm and trusts you more.
Your turn
Write the first update you would send a client in week one: what you did, what you found, and what comes next.
What the video doesn't have time for.
Why operating is harder than building
The first win gets attention. Keeping results coming — while experiments fail and the client expects more every week — is the real job. Role, method and communication are what keep a project alive.
The three parts of the work
- Analyst: turns data into reports and decisions.
- Engineer: builds and automates, with focus.
- Client-facing: understands the customer and explains the result.
Titles change from company to company. The parts of the work stay the same. You will be strong in one and good enough in the others.
One iteration, written down
Change one thing at a time and keep a short log: what you tried, what happened, what you will test next. That log becomes your case study later.
Staying ahead of the client
- Send a short update before they ask for one.
- Say what is not working as early as what is.
- Always end with the next test and the date you will measure it.
Common mistakes
- Defending the first version instead of improving it.
- Changing three things at once and not knowing what worked.
- Going quiet when results are bad.
Take it to a company
Offer a weekly one-paragraph update: the number, what changed, the next test. Few providers do it — and it is why clients stay.
Your role, chosen with reasons — and the record of one complete iteration.