LEO ANDRADEPERSONAL SITE / EST. 2026Selected work
Pages

02 / MY APPROACH

A CLOSER LOOK / LEO ANDRADE

How I look at
the whole problem.

I've learned from construction, sales, technology, and the people I've worked with. These are five principles I return to—not borrowed slogans, but practices I can trace to real experiences.

THE FULL STORY↓ SCROLL TO EXPLORE
THE POINT OF VIEW

I don't think a good idea is enough. I want to understand who it helps, what it depends on, and whether it survives contact with reality.

WHAT I KEEP ASKING

Who is this for?

What is actually happening?

What will make the whole thing work?

01 / 05UNDERSTANDING PEOPLE

A person is more than a buyer.

I spent years deliberately studying psychology and buyer behavior. Not because I think people can be reduced to a formula, but because the same technical offering can mean very different things to two different business owners.

One may care about staying compliant. Another may be worried about disruption, cost, or letting a team down. Their motivations matter. Good discovery starts by listening for what they are actually trying to protect, change, or accomplish.

IN THE WORK

That perspective informs how I approach discovery, service positioning, and the campaigns I build around new requirements.

See buyer-led positioning ↗
02 / 05THINKING IN SYSTEMS

The parts only matter if they work together.

Construction gave me a concrete understanding of interdependence. A finished structure hides hundreds of decisions. Every stage has its own complexity; each handoff affects the next one.

I see similar patterns in business and technology. The promise made by marketing, the price on the quote, the design of the service, the operations behind it, and the customer's actual experience form one system. A weak connection anywhere can undermine the entire result.

IN THE WORK

I carried that thinking into customer projects where I handled conversations, measurements, calculations, and sometimes deliveries.

See the complete customer journey ↗
03 / 05FINDING AN OPPORTUNITY

Make the message about a real problem.

Legislation and external requirements sometimes change what a customer has to do. Those changes can create the need for expertise, services, or a clearer plan. I look for that connection rather than starting with a product and searching for an excuse to promote it.

The first responsibility is accuracy. Does the rule apply? What does it require? What is the operational impact? Only then is it useful to ask what an organization can credibly offer.

IN THE WORK

This is how I approach regulatory-context campaigns: understand the situation, then explain how to respond without exaggerating the risk.

Read the regulatory campaigns case ↗
04 / 05LEARNING THROUGH WORK

Experience begins somewhere.

I was naturally quiet, so I went into digital marketing sales. I had never sold a complete kitchen project until I learned what was required. And I didn't have every technical answer before taking responsibility for an internal QuoteWerks interface.

That doesn't mean expertise is irrelevant. It means I take unfamiliarity as a reason to research, ask questions, test assumptions, and improve. Confidence should be matched by preparation and a willingness to revise.

IN THE WORK

The QuoteWerks interface is still in progress. I describe what I'm building, not results I haven't achieved.

See what I'm building ↗
05 / 05OWNING THE OUTCOME

A title doesn't finish the job.

I value trust and responsibility more than an impressive label. Some of the work I'm proudest of happened because I stepped into a gap, made myself useful, and stayed involved beyond the original assignment.

That means paying attention to what happens after the meeting or the sale, not simply getting credit for the part I completed. It also means being clear about what I personally owned, what others contributed, and what still needs work.

IN THE WORK

At the granite business, a contract worth over $300,000 reinforced the stakes of thoughtful bidding and follow-through.

Read the contract story ↗

A PRACTICAL FRAMEWORK

Listen. Understand. Connect. Build. Learn.

01Listen to the people
02Understand the system
03Connect the constraints
04Build a useful response
05Learn from the result

This is a way to approach work, not a promise that every problem will follow a perfectly straight line.

NEXT / WORK

The principles
have receipts.

See where those ideas came from and what they look like in actual projects.

Explore selected work