Every company has a system of record. No company has a system of judgment.
What your estimator knows about a drawing, a set-up and a changeover is not in your ERP. Blake is the first application built on that model. It makes the calculation and its assumptions reviewable, so the estimator can confirm or correct them.
One shared representation of geometry, requirements and factory. A model per process. Each line shows its basis, for review.
How Blake works
01
Upload
Start from an upload. Additional intake channels are part of the rollout.
02
Understand
Blake proposes requirements and their links to the model for review. Where the evidence is incomplete or conflicting, the estimator decides.
03
Confirm
Your engineer confirms or corrects each item in one click. Where Blake is unsure, it asks.
04
Decide
Blake is being built to support manufacturability, machine choice, cycle time and manufacturing cost, with the estimator reviewing the assumptions behind each one.
How work gets in
Now
You start from an upload: the 2D drawing and the 3D model.
Four steps, reviewable at every stage.
Direction
Additional intake channels, including a customer portal and email, are part of the rollout.
A universal layer
Blake is agnostic: it does not matter which ERP, CAD or CAM you run. Blake sits on top of what you already use, reads what it needs, and organizes the work around your existing process. Nothing is replaced.
Designed to fit alongside the ERP, CAD and CAM systems a shop already uses.
The first product loop we are building
Hover or focus a block, tab and arrow keys work too, to see what it does today.
The first release focuses on an editable manufacturing-cost calculation for milling and turning.
One model, four things it learns
Blake is the first application of our world model for precision manufacturing. The model learns how geometry, requirements, machines and process decisions come together in a physical part, and Blake uses that to answer the questions an engineer asks before production starts.
Geometry
What the part is: shapes, features and how they relate.
Requirements
What the part must meet: tolerances, finishes, materials, standards.
Machines
What your floor can do: machines, tooling, fixtures and their limits.
Decisions
How process choices turn a drawing into a finished part, and what they cost.
What Blake gives you
Understands the part, not just the file
Blake proposes links between requirements and the geometry they apply to, for the estimator to review.
Designed around your factory
Blake is being built to reflect the machines, tooling and manufacturing history of the shop it works in, not a generic factory.
Each answer shows its basis
Every output points to what it rests on, so your team can check it in seconds instead of redoing it.
Runs where your data is
Designed to run on your premises or in an EU tenant. Customer data stays in the environment you choose.
What the first release actually carries
The ambition is large. What is live today is smaller, on purpose: this is the honest line between the two.
Now
Geometry parsing (2D drawing / 3D model) and an interactive 3D viewer
Stable face identity and first hole/bore recognition on a test part
Requirement and conflict objects
Deterministic calculation rules with a traceable source
Repeat-order comparison
In development
Blake is learning to connect requirements to geometry
Blake proposes features, operations and cost inputs for review
The calculation is designed to become specific to a shop's machines, tooling and history
Direction
A full, sendable quote object
Execution outcomes and machine feedback
A calibration loop built from measured outcomes
A learned model
Broad portal and email intake
CAM integration or physics-based simulation
Request early access
Want to see how Blake reviews a drawing? Choose your own time: we show you Blake with your own drawing, or one of ours, with its basis shown alongside.
