$675M
raised by California-based Figure in one 2024 round
Axios on FigureAbout Blueprint
Blueprint exists to help robotics capital turn into real deployments.
The industry has raised enormous amounts of money and produced real progress, but deployment still breaks on the same things: unknown sites, late context, messy handoffs, and too much fieldwork before the team has even seen the actual environment.
Founded by
Nijel Hunt — background in robotics simulation, 3D capture, and deployment operations. Based in Durham, NC.
LinkedInThe gap
In the U.S., capital is not the bottleneck anymore. Deployment is.
$350M
raised by Texas-based Apptronik in 2025
Axios on Apptronik37,587
industrial robots installed in U.S. factories in 2023
IFR on the U.S. marketIn the U.S., robotics is clearly not short on capital. The funding headlines are real. What is still harder is turning that capital into repeatable deployments on real sites.
There is no single public database for 'successful robot deployments per year' across every U.S. robotics category. The cleanest public proxy is actual installation data. That misses plenty of service-robot activity, but it is still better than pretending the deployment number is easy to measure.
Blueprint exists to push that deployment number up year after year by getting the real site in front of the team earlier, packaging it clearly, and making evaluation less blind before the fieldwork starts.
What Blueprint sells
Blueprint sells site-specific world models, site packages, and hosted evaluation built from real indoor capture.
Who it is for
Robot teams preparing for a pilot, field visit, or deployment question that depends on one exact facility.
What it does not claim
Blueprint does not claim that one package or one hosted session replaces final on-site validation, safety review, or deployment signoff.
Our goal is to make real robot deployments increase year after year by cutting the cost, delay, and guesswork between interest and real-site validation.
That starts with a simple rule: get the actual site in front of the team earlier. Then make the package, the hosted runtime, and the trust boundaries clear enough that the team can move from curiosity to real deployment work without flying blind.