Measure before touching
so there is a number to argue with later, and a before to compare against.
Consulting
You already know which step it is
A process that works fine at ten orders a month is quietly costing a day a week at forty — and everyone in the room can name the step. Foresight measures that step, automates the part that is genuinely repeatable, and leaves the judgment with the engineer.
One consultant with a system, not an agency with a deck: SolidWorks add-ins in C# and xCAD, PDM workflows, DriveWorks implementation, VBA and macros, web tooling, cloud data, reporting through Power Query. The tool follows the problem, not a preferred stack.
The method, given away
01
02
03
04
Measure first. Version everything. Ship with receipts.
Version every artifact
nothing already handed over is ever overwritten. Ever.
Assert, then change
every change declares what it should touch first; a failed assertion is information, not an obstacle to push through.
Read the file back
a build log records intent; the file on disk records fact. Claims get checked against the file.
The method is not a secret, and this is it in full. Take it and use it without us — plenty do. The ones who call are the ones who want it applied at speed by the hand that sharpened it.
The Bezalel Framework
Principles are the rock. Practices are the attempts.
Behind the method sits a written operating model for custom manufacturing — the Bezalel Framework. It separates the principles that do not change from the practices that should: every process is the current best attempt, reviewed against two tests — does the context still fit, and does it still benefit everyone it touches, not just its administrators.
It names the three ways work goes wrong — waste, unevenness, overburden — and pairs each with its own countermeasure. It keeps shared resources loaded below the threshold where queues blow up. And it treats bad news early as good behavior, because bad news late is the only failure.
Tools change. Software changes. The principles are load-bearing.
What that discipline is worth to you
Work arrives with its evidence attached: counts, versions, and a short account of what was checked. If something is half-built, the status says half-built. Handover is a document and a working artifact, not a walkthrough you have to record.
The same discipline built Keystone — 155+ shipped builds, about 1,600 automated assertions per surface on every one, 15+ release gates that can stop a build. That is not a quality process bolted on for clients. It is the method on this page, applied long enough to leave evidence.
You are not hiring hours. You are hiring a system that happens to bill by them.
The artifacts
What an engagement leaves behind
Not a slide deck. Recent engagements have left behind artifacts a shop runs on — the kind of documents that get printed, argued with, and kept.
An operating system for the shop
One document that unifies how people treat each other and how the work gets done — a twelve-phase, nine-gate delivery process where every phase carries a named owner, a definition of done, and one yes-or-no test. Payment milestones ride the gates, so commercial terms track technical progress.
Engineering standards that hold
Five numbering schemes that cover every part a manufacturer makes or buys. Identity fixed at first use — reuse does not create a new number. Vendor swaps become procurement actions that never touch the BOM, and a six-state workflow moves designs to release without retyping.
A culture activation plan
Change sequenced the only way it holds: safety, then connection, then ownership. A protected pilot, leadership changing its own behavior first, and a cascade that advances on evidence, not on schedule.
The part-number walk
A live floor exercise that makes the cost of meaningless numbers countable — three rounds, every lookup tallied, the decoder learned once in two minutes. The contrast is the lesson.
Process without honor hardens into bureaucracy. Honor without process dissolves into chaos. The work is keeping both.
Client names stay off this page and always will. The patterns are the portfolio.
The install is the start of the relationship, not the end of the project.
The no you can bank on
Foresight says no to work it cannot do well, and says it early rather than three invoices in. If your problem is better solved by a setting in software you already own, that is the advice you will get. Nothing here is priced to keep a consultant on site longer than the problem needs.
The tools are held to the same standard: when Keystone cannot do something safely it says so in a sentence rather than guessing. The person who built it answers questions the same way.
A refusal you can rely on is worth more than a yes you have to verify.
The tools Foresight sells started as consulting work that outgrew a single client, and the consulting is still where the next ones come from. Keystone and the DriveWorks practice are the same hand at a different scale.