Solution Engineering Advice

Max Halford's field manual for the technical person thrust into customer-facing roles at an early-stage startup. Three phases of the customer lifecycle (presales, pilots, onboarding), each with its own ethical posture, tactical playbook, and relationship dynamics. Unusually honest about when to bend the truth, how to manage Sales, and why Extreme Ownership is the only viable mindset.

"You won't be rewarded for always telling the truth."

Halford doesn't say this with cynicism. He says it as someone who learned that startups selling to enterprise lay tracks while the train moves forward. If you trust your team to build what's needed, a bit of creative positioning to get a worried prospect over the line isn't malice — it's confidence in your own product. Still, this is the line that will divide readers. Some will see pragmatism; others, a rationalization that scales badly.

"The last thing you want is to make your work appear trivial."

This is the counterintuitive advice that separates experienced solution engineers from eager technicians. Don't just deliver results — narrate the difficulty. If integration took significant effort, explain why. The customer is buying you as much as the software, and perceived effort shapes perceived value. It's not about boasting; it's about making the invisible visible.

"Controlling the tempo makes you look professional."

Halford's advice on pilots is essentially project management disguised as salesmanship: clarify success criteria into measurable form, hold weekly catch-ups with an agenda you set, and proactively surface issues in the customer's data before they spot them. The pilot is "a race against time" — ticking criteria before the deadline, because the customer isn't tracking the timeline as closely as you are. If you slip, "they might not even notice." That's both a relief and a trap.

"The customer is buying you as much as the software."

A steady drip of small wins is more memorable than a single firehose meeting. Space out what you show. The onboarding phase tests whether the relationship built during presales holds up under the weight of actually delivering. Halford's prescription: compress the timeline, practice Extreme Ownership ("if something went wrong, it's on you"), and treat the customer as a partner on equal footing, not a superior.

"Plenty of companies still run on a swamp of ad hoc Excel files."

The parting insight: the bar is lower than it looks from inside a tech team. Data scientists and engineers underestimate their value outside purely technical roles. With AI commoditizing software, Halford argues your worth increases by becoming "a technical mind that can chat with customers." Forward Deployed Engineers and Product Engineers are the shape of things to come.

Key Themes

• #pattern — Three-phase customer lifecycle (presales → pilots → onboarding) as a reusable mental model for any customer-facing technical role
• #pattern — Vague-to-measurable criteria translation: "Measure product environmental footprint" → "Measure GHG footprint for >95% of 2025 production volume"
• #pattern — Tempo control as professionalism: weekly cadence, your agenda, proactive issue surfacing
• #concept — Extreme Ownership applied to customer relationships: if something went wrong, it's on you — blaming the customer is a dead end
• #concept — "Be economical with the truth" as a startup survival tactic: tracks laid while the train moves; Sales making impossible promises hurts everyone long-term
• #concept — Perceived value ≠ delivered value: narrate the difficulty, space out wins, don't let your work appear trivial

Critical Analysis

Halford's honesty about dishonesty is what makes this piece worth reading. Most writing about sales engineering is either sanitized corporate doctrine or cynical "always be closing" bro-culture. Halford lands in the interesting middle: he wants to be truthful, he is truthful about his own product's superiority relative to competitors, but he's also clear-eyed that rigid honesty in presales is a luxury startups can't afford. The question he doesn't fully answer: what happens when the tracks don't get laid in time? The article is written from the perspective of someone whose company survived — we don't hear from the customers who bought on promises that never materialized.

The dating metaphors (presales = flirting, pilot = first sleepover) are effective but reveal something Halford probably didn't intend: solution engineering, as he describes it, is fundamentally an exercise in managed impression. Every phase involves controlling what the customer sees and when. This isn't necessarily dishonest — it's the same filtering everyone does early in any relationship — but it means the skill of solution engineering is closer to performance than most technical people are comfortable admitting.

The most transferable insight is the three-phase structure itself. Whether you're selling software, pitching internal tools, or convincing your org to adopt a new practice, the dynamics Halford describes (anxious decision-makers in presales, criteria-racing in pilots, relationship-testing in onboarding) map cleanly. The specific tactics are startup-B2B-enterprise, but the shape of the work is universal.

The article's weakness is its silence on leaving bad deals. Halford describes how to win pilots and onboardings, but not how to recognize when you should walk away. In a small startup, every deal feels existential — but some customers cost more than they're worth, and the Extreme Ownership mindset can become a trap if you own problems you didn't create and can't solve.

Sources: My Unvarnished Guide to Solution Engineering Last updated: 2026-07-05