The Hardware Project Planning Software
Engineers Actually Use.
Most hardware builds stall in planning: wrong parts, unwritten constraints, decisions buried in email. SpecZero is hardware project planning software that replaces the mess with a structured workflow — from first requirement to a verified, BOM-backed build.
Free for your first project. No credit card required.
Define
Explore
Decide
Build
The problem
Bad planning has a price.
You've paid it.
It's not a talent problem. It's a system problem: wrong parts, unwritten constraints, decisions that were never documented.
Wrong part ordered. The constraint was never written down.
Five BOM versions exist. Nobody knows which one is correct.
Can't explain why you chose this component. It just seemed right.
Decision history is spread across six Slack threads and a sticky note.
Three weeks into design, you missed a constraint. Starting over.
Progress report due. Nothing was documented. You're guessing.
The system
One workflow. Everything in its place.
Four phases, each building on the last. By the time you order the first part, every constraint is documented and every decision is justified.
01 Define
Start with requirements, not parts
Write down what the build must achieve before opening a browser tab. Requirements live in two lanes (essential and nice-to-have) with target specs per item.
- Essential vs. nice-to-have requirement lanes
- Target value per requirement (e.g. "< 500g", "5V tolerant")
- Constraints documented before design begins
02 — Explore
Compare before you commit
Every requirement gets a concept comparison. Explore multiple approaches with pros, cons, and difficulty ratings. Choose deliberately, not by default.
- Multiple concepts per requirement with pros and cons
- Difficulty ratings and tradeoff notes
- Per-concept BOM items and file attachments
03 — Decide
Lock your reasoning, not just your choice
The Decision Log structures every key call: objective, approaches, analysis, decision. AI scaffolds the entry. You fill in the reasoning. Confirm to lock.
- Structured entries: objective → approaches → analysis → decision
- AI-assisted scaffolding and drafting per field
- Confirm to lock, reopen at any time
04 — Build
Execute with a single source of truth
Select a concept — it goes to the Master BOM. Track each part from Planned to Ordered to Received. Build sections keep tasks, notes, and files in one place.
- Master BOM auto-generated from selected concepts
- Build sections with tasks, notes, and file attachments
- Part status: Planned → Ordered → Received
What you get
Every tool purpose-built for hardware.
Not Notion. Not ClickUp. Not a spreadsheet with extra columns. Built specifically for the engineering planning workflow, from first spec to final BOM.
Requirements
Capture constraints and target specs in Essential and Nice-to-have lanes. The guardrails that prevent expensive mistakes before design begins.
Concept Planner
Compare approaches per requirement with pros, cons, and difficulty. Each concept carries its own BOM items. Select when ready.
Decision Log
Objective → Approaches → Analysis → Decision. AI scaffolds the structure; you fill in the reasoning. Lock when confirmed.
Master BOM
Auto-generated from your selected concepts. One source of truth for every part. Status tracking from Planned to Ordered to Received.
Execution Tasks
Per-section checklists linked directly to BOM items. No Kanban overhead — just what needs to happen, in the right order.
Auto Timeline
Every decision, upload, and status change creates a permanent record. No manual logging. Progress reports write themselves.
Built for engineers who build things
Engineering Students
Capstone and senior design projects
Makers & Hobbyists
Serious builds deserve serious planning
Indie Engineers
Solo hardware and product development
FAQ