About
Keypiece exists because most problems don’t need more advice.
They need someone experienced enough to see the whole picture, honest enough to say what’s actually missing, and willing to stay until it works.
Founder
Oran Zak
BuilderOwnerOperatorProblem Solver
Oran came up through the technical and mechanical side of work and studied mechanical engineering. Most of his career since has been in construction: excavation and groundwork, equipment operation, foundations and concrete, estimating, project management and custom-home construction.
He went on to own and run a construction company with nearly twenty employees — hiring, managing people, coordinating subcontractors, managing suppliers, dealing with customers, and carrying complex projects from quote to completion.
That meant being the one responsible when employees needed answers, when payroll was due, when a customer changed the requirements mid-project, when a supplier created a problem, when the schedule slipped, when an estimate was wrong, and when a decision had real financial consequences.
He isn’t a management consultant, and Keypiece isn’t built to look like one. He’s a practical operator and problem solver who has carried the responsibility himself.
“What does the textbook say?” has never been the useful question. “What will actually work here?” is.
Placeholder photography — to be replaced with real project images.
How Keypiece works
Judgment is the product. Everything else supports it.
Technical and business, together
Understanding how the work is physically performed and what it costs to perform it. Scope, estimate, labour, materials, subcontractors, schedule, execution, change, invoice, margin — and how a decision in one moves all the others.
Systems thinking
The obvious problem is often a symptom. Keypiece looks for what’s actually causing it and how the pieces connect before recommending anything.
Owner mentality
Every recommendation gets tested the same way: what will it cost, who will actually do it, will people use it, is the benefit worth the effort, and what happens when something goes wrong.
Resourcefulness
Comfortable in messy situations where the information isn’t complete and a decision is still needed.
Directness
Plain language. Understand the situation, decide what needs to change, help make the change happen.
Foresight
Thinking past the decision in front of you to the second-order consequences it creates.
Technology
Process first. Tools second.
Technology, automation and AI are useful when they remove real work, improve the information behind a decision, or make something consistent that used to depend on memory. They are not useful as an answer to a problem nobody has defined yet.
So the order matters: understand the problem, understand how the process actually runs today, then decide whether a better tool genuinely helps — and whether the people who have to use it will.
Bring Keypiece the situation.
We’ll start by understanding what’s actually happening.