Small Windows tools. Bench-tested.
Each BenchWorkSoftware tool does one job on your own PC and costs one price. It ships with the report of the tests it passed and the ones it failed.
Fig. 2, live
This page, on the bench
Take nothing here on trust, starting with this page. Your browser has just measured it against the rules a BenchWorkSoftware tool has to meet. The numbers below are its own.
The check runs in your browser once the page has loaded. It reads the browser's own records, sends nothing and stores nothing.
Tools
Nothing released yet
The first tool will be listed here when its test report is fit to publish. Every tool's page will carry the same five things.
General notes
Every tool meets these
A drawing states its tolerances once, in the title block, and every dimension obeys them unless it says otherwise. These are ours. If a tool ever needs an exception, its own page and its Store listing say so before you install it.
Method
How a tool gets released
Four gates, in order. Each one can stop a tool. So far the first has turned away 7 ideas, and nothing has reached the bench.
- 1
Proof before work
We build a tool only when people already pay for that job: at least two sellers showing a price, with recent reviews.
No proof: it is not built.
- 2
A written offer
The price, the scope and a list of what the tool will not do are fixed before any code is written.
No clear offer: it is not built.
- 3
The bench test
A fixed set of real files and a pass mark set in advance.
Below the mark: it does not ship.
- 4
Release with the report
The report that cleared the tool is the one you read on its page, failures included.
A fault found later joins the bench. The next release has to pass it.
Company
Who makes these
BenchWorkSoftware LLC is a small software company in Michigan, USA. Much of the building and testing is automated, and the test bench decides what ships.
Write to hello@benchworksoftware.com.