We replaced conversations with dashboards.
A dashboard reports what you already knew to measure. It cannot report the thing nobody thought to instrument.
GiFOC · Get in Front of Customers
In the age of AI, your only
moat is your customer.
Everyone now has the same models, the same tooling, and the same speed. The one asset nobody can copy is what your customers actually know — and most organizations are arranged, structurally, never to hear it.
The diagnosis
Every large mistake traced back to one variable.
Twenty years leading customer-facing teams in Silicon Valley, and the pattern held every time — mine included. Not talent. Not budget. Not speed. Distance from the customer. It is the one input that quietly determines the quality of every other decision, and the only one nobody puts on a dashboard.
A brief history of being wrong
We mistook personas for actual users.
A persona is an average. Nobody has ever filed a ticket, churned, or renewed as an average.
We copied competitors instead of asking customers.
Copying a roadmap imports someone else’s assumptions — including the ones their customers already rejected.
We shipped what engineers loved and customers ignored.
Enthusiasm inside the building is not demand outside it. The two feel identical from a conference room.
The principle
Two missions. That is the whole framework.
GiFOC is not a methodology with certifications. It is a correction — a deprogramming for capable leaders who drifted into spreadsheet thinking because the spreadsheet was closer than the customer.
01
Seek the ground truth.
Lead your team out of the dashboard bunker. Metrics describe; they do not confess. Hold strategic conversations, not check-ins — the kind that surface hard truths, hidden needs, untapped wins, and the opportunity nobody had a field for.
Done consistently, your customer-facing teams stop being a cost line and become the sharpest intelligence function in the company.
02
Connect the front line to the code.
Truth that dies in a Slack thread is theater. The second mission is plumbing: build the system that carries frontline insight into product, strategy, and the boardroom — with the customer's name still attached to it.
The goal is a roadmap that is a direct reflection of customer reality rather than internal assumption.
Without it
Customer ──▶ Front line ──▶ a Slack thread ──✕ nothing
With it
Customer ──▶ Front line ──▶ the system ──▶ Product · Strategy · Board
Field notes
Twenty years, distilled.
The principle did not arrive as a framework. It accumulated one wrong call at a time — across support, success, product, engineering, and hiring. Each of these is the whole lesson; the essay behind it is optional depth.
01 / Seek the ground truth
Comfort metrics are a mirage.
CSAT samples the loudest two percent and calls it the voice of the business. Manage from that and you are not leading — you are squinting.
Extra credit ↗I would rather be talking to customers than evaluating another tool.
The tooling question is almost always a proxy for a conversation nobody wants to have.
Extra credit ↗A locked feedback loop is itself the answer.
When there is no honest channel left, the silence tells you what no survey ever will. I have left a company over exactly this.
Extra credit ↗Know precisely who you are for.
An ideal customer profile is not marketing decoration. It is the alignment between what you build and who it is actually for.
Extra credit ↗02 / Connect the front line to the code
Customer Success belongs inside Product and Engineering.
Not adjacent to them, passing findings across a wall. Inside, where the roadmap is actually decided.
Extra credit ↗Support is not the goalkeeper.
Played at the back it can only ever react. Move it to the midfield and it starts shaping the game.
Extra credit ↗The front line gets a product veto.
The people who absorb the consequences of a bad decision should have a say before it is made, not a ticket queue afterwards.
Extra credit ↗Your product is your best CSM.
Every answer a human has to repeat is something the product failed to say for itself.
Extra credit ↗03 / Hold the balance
You cannot empathize your way out of a stack trace.
Customer-facing technical orgs are their own discipline. Generic customer advice breaks on contact with them — which is why AI aimed at them needs different judgment.
Extra credit ↗Developers do not want help. They want a jam partner.
Technical customers judge you on whether you are useful inside the work, never on how the interaction made them feel.
Extra credit ↗New tech, old truths.
AI arrives every few years wearing a new name. Customers stay exactly the same. Budget for the first, build for the second.
Extra credit ↗Hire for the complexity you cannot see yet.
Technical depth ages better than any job description you are able to write today.
Extra credit ↗The distance test
How far are you from the customer?
Six statements. Check only the ones that are honestly true right now — the value of this is entirely in refusing to round up.
Your smartest collaborators are your customers.
Start listening.
Want this running in your org?
▎ GiFOC is how I rebuild customer-facing technical orgs.
▎ Support · SE · Solutions Architecture · CS · FDE