Conviction before velocity
Speed without direction is expensive noise. We move when the thesis is sharp — not when the calendar demands theatre.
Ask why before how fast.
Renato Xhaferaj
A manifesto for engineers who care about craft — and investors who care about conviction. Written for the people who can tell the difference between a system built to last and a system built to be sold.
Judgment over volume
Fewer bets, argued properly, carried to the end.
Legible systems
Architecture a good team can still explain at midnight.
Reality, early
Bad news travels first here. That is the whole trust model.
A point of view on craft, capital, and the kind of work worth doing together.
I am not here to impress you with jargon. I am here because the best engineers and the best investors share one instinct: they can tell when something is built to last — and when it is built to be sold.
For several years, that instinct has guided how I work. Not as a performer on a stage, but as someone in the room when the hard calls get made: what to build first, what to refuse, when to move fast, and when to hold the line.
Most of what fails does not fail loudly. It fails quietly, months earlier, in a decision nobody wrote down — a shortcut taken to hit a date, a disagreement smoothed over instead of settled, a number reported the way it should have been rather than the way it was. By the time the failure is visible, it is only arithmetic.
The ventures I touch are meant to compound. That means respect for the people who write the code, respect for the people who allocate the capital, and zero tolerance for complexity that exists only to sound smart.
Great outcomes are rarely loud at the beginning. They are clear. Clarity is the whole strategy.
Five principles
The rules I do not negotiate — the ones that decide everything downstream.
Speed without direction is expensive noise. We move when the thesis is sharp — not when the calendar demands theatre.
Ask why before how fast.
Elegance in execution is not vanity. It reduces risk, attracts exceptional people, and tells investors you mean what you say.
Quality is a cost structure.
Hard problems deserve hard thinking. Performative difficulty does not. The goal is a system a smart team can still explain at midnight.
Simple is the hard version.
Reputation is not a landing page. It is what you do when nobody is applauding: how you treat partners, how you handle setbacks, how you report reality.
Character compounds too.
Investors do not fund confusion — they fund narratives they can underwrite. Engineers do not stay for chaos — they stay for missions they can believe in.
One honest paragraph beats ten slides.
If this resonates, we should talk. If it does not, you will know quickly — and that is a kindness too.
Three places where a second set of hands and an honest second opinion tend to change the outcome.
Turning a vague ambition into a system with a spine: what the first version must prove, what it is allowed to ignore, and where the seams go so the second version does not require a rewrite.
Shipping is a discipline, not a mood. Sequencing the work so progress is visible weekly, risk is retired early, and the team spends its energy on the parts that actually decide the outcome.
Reading a technical story the way an operator reads it. What is genuinely defensible, what is a rebuildable weekend, and which claims in the deck the team could not survive being asked about twice.
No discovery theatre. Four steps, each one designed to make the next one cheaper.
The first conversation is not a pitch in either direction. I want the constraint you have stopped mentioning because you assume it is permanent.
Most briefs describe a symptom. Written back in one paragraph, the actual decision usually turns out to be different — and smaller — than it looked.
Something real, in front of real users or real numbers, early enough that being wrong is still cheap. Opinions are expensive; evidence is not.
Documented, legible, owned by your team — not by me. The measure of the work is how well it runs after I stop touching it.
Different seats at the table. The same bar for honesty, depth, and follow-through.
If you are tired of rewriting the same mistakes, we speak the same language.
If you allocate to substance over story, we should compare notes.
I take a small number of conversations seriously: founders with a real wedge, engineers with a real problem, investors with a real thesis.
A few sentences on who you are and what you are building is enough. Noise is optional.
Usually a reply within a few days