In development · Early access open for manufacturers
Know what a part demands before you commit to making it.
SpecForge reads engineering specifications, technical drawings and equipment manuals, extracts every dimension, tolerance, material and process requirement, and checks each one against your shop’s declared capabilities. Engineers review linked evidence instead of hundreds of pages.
Built for precision manufacturers, industrial suppliers, fabricators and engineering contractors.
RFQ-2417 · KFS-MB-220 Rev C · sheet 1 of 3
Sample dataExtracted requirements
- D-04Main bore Ø12H7Matched
- M-01Block material6061-T6 / 6082-T6Conflict
- S-02Sealing facesRa 0.2 µmOut of capability
- T-07M8 × 1.25 threadsdepth ?Missing info
- F-02Hard anodizeType IIIOutsource
4 items need an engineer’s decision
Reads the whole package
Specs, drawings, manuals and RFQ letters, native or scanned PDF.
Finds conflicts and gaps
Contradictions between documents and details nobody specified.
Checks against your shop
Each requirement compared with the capabilities you declare.
Every finding has a source
Page and region links so engineers verify in seconds.
The problem
One missed line on page 37 can cost the whole job.
Manufacturers decide whether they can make a component by reading hundreds of technical details by hand. Most of the time it works. When it doesn’t, the cost shows up as rejected parts, rework and delayed production.
Illustrative example
RFQ package arrives
Drawing, 12-page material spec, 41-page supplier quality manual.
Manual review under deadline
An engineer skims for dimensions and materials to price the job.
One note is missed
Quality manual §9.2 requires Type III hard anodize. The quote assumes Type II.
Parts rejected
Coating fails incoming inspection. Parts are stripped, re-coated and re-inspected.
Margin and schedule lost
Rework cost, a late delivery and an uncomfortable customer call.
Requirements are scattered
A single part can be governed by the drawing, a material spec, referenced standards and the customer’s quality manual, and they don’t always agree.
Review depends on who has time
Thoroughness varies with workload. The experienced engineer who would catch the conflict is often busy on the shop floor.
It doesn’t scale with quote volume
Every new RFQ adds hours of reading. Shops either slow down responses or accept more risk in each quote.
The SpecForge approach
Read every document in the package, structure every requirement, cross-check them against each other and against the shop, and hand the engineer a short list of decisions, each linked to its source.
Core features
From RFQ package to reviewed requirements.
Seven capabilities that cover the review an engineer does today, with the engineer still making every call. SpecForge assists professional judgment; it does not certify designs.
F-01
Document ingestion
Upload the full RFQ package: drawings, specifications, equipment manuals and customer requirement letters, as native or scanned PDFs.
Nothing is reviewed in isolation. Every document that governs the part is read together.
F-02
Requirement extraction
Dimensions, tolerances, materials, surface finishes, threads, coatings, heat treatments and inspection criteria become structured, typed records.
A complete requirement list in minutes instead of a highlighted printout.
F-03
Conflict and gap detection
Cross-checks requirements across documents and flags contradictions, ambiguous callouts and information that is simply missing.
Catch the problem while it is still a question, not after parts are made.
KFS-MB-220 Rev C · Note 2
MATERIAL: ALUMINIUM ALLOY 6061-T6 PER EN 573-3.
MS-14 Material Spec · §3.1
Block bodies shall be machined from 6082-T6 bar to EN 755-2.
F-04
Capability matching
Compares each requirement with your declared machines, processes, tolerances and partner capabilities.
See immediately what you can make in-house, what needs a partner and what is out of reach.
F-05
Readiness assessment
Rolls everything into a manufacturing readiness score with the blocking items listed first.
Decide to quote, clarify or decline with a clear picture of risk.
- Conflict Material
- Out of capability Ra 0.2
- Missing info 2 items
F-06
Clarification requests
Drafts precise questions for the customer for every conflict or gap, citing the exact document and section.
Fewer back-and-forth emails and faster, firmer quotes.
To: Kestrel Fluid Systems · re T-07
Thread depth for M8 mounting holes
The four M8 × 1.25 threads on sheet 1 have no depth callout. Please confirm the required full-thread depth.
F-07
Evidence-linked summaries
Technical summaries where every statement links to the page and region it came from.
Engineers verify instead of re-reading. Decisions are recorded with their evidence.
How it works
Five steps, one reviewable record.
The same workflow an experienced engineer follows, made systematic and traceable.
- 01
Upload the package
Drop in the drawings, specs, manuals and RFQ letter for a part. SpecForge groups them into one project.
4 documents · 58 pages
- 02
Extract and structure
Text, tables and drawing notes are read with their page positions and turned into typed requirements.
14 requirements
- 03
Cross-check documents
Requirements are compared across documents and against referenced standards to surface conflicts and gaps.
1 conflict · 2 gaps
- 04
Match your capabilities
Each requirement is checked against the capability profile you maintain for your shop or site.
1 out of capability · 1 partner
- 05
Engineer decides
Review the short list, accept with notes or send drafted clarification requests. Every decision is logged.
Readiness 71% → 93%
Example outputs use the sample manifold-block project from the demo below.
Interactive demo
Walk through a real-feeling RFQ review.
Switch projects, filter requirements, open the evidence behind a finding, resolve the review queue and watch readiness update. Everything here runs in your browser with fictional sample data.
Readiness
71%
Requirements
14
from 58 pages
Need review
4
blocking a firm quote
Documents
4
Kestrel Fluid Systems
Requirement status
Select a segment to filterAI assessment
Two items block a firm quote: the material conflict (M-01) and the Ra 0.2 µm sealing-face finish (S-02). Resolving M-01 with the customer and quoting lapping as an outsourced step would raise readiness to about 93%.
Activity
- SpecForge Flagged a material conflict between drawing note 2 and MS-14 §3.1 · 09:42
- SpecForge Extracted 14 requirements from 4 documents (58 pages) · 09:41
- A. Mensah Uploaded RFQ package from Kestrel Fluid Systems · 09:38
SpecForge is building its initial product. The workspace shown on this site is an interactive demonstration that uses sample data.
Who it’s for
Built for the teams that say yes or no to a part.
Precision manufacturers
- Problem
- Tight-tolerance machined parts where one misread GD&T callout or finish spec turns into scrap.
- How they use SpecForge
- Quoting engineers run each RFQ through SpecForge and price from the requirement list and readiness assessment.
- Benefit
- Faster, firmer quotes with tolerance and finish risk visible up front.
Fabrication companies
- Problem
- Weldments and sheet-metal assemblies governed by weld procedures, material certs and finishing specs spread across documents.
- How they use SpecForge
- Estimators check weld qualifications, material grades and outsourced finishing against their capability profile.
- Benefit
- Fewer surprises at weld qualification and finishing.
Industrial suppliers
- Problem
- Suppliers responding to customer specifications and supplier quality manuals that change between programs.
- How they use SpecForge
- Teams compare each new package against the customer’s quality requirements and their own certifications.
- Benefit
- Consistent compliance checks, whoever handles the RFQ.
Engineering contractors
- Problem
- Contractors interpreting equipment manuals and owner specifications before procurement or fabrication.
- How they use SpecForge
- Engineers extract requirements from manuals and specs, then send drafted clarifications to the owner.
- Benefit
- Requirements clarified before work packages go out.
Technology
How We Use Amazon Web Services
SpecForge’s proposed architecture is designed on AWS so that every requirement it reports can be traced back to the page and region it came from. Documents move through a serverless pipeline, from upload through extraction and AI analysis to the engineer’s review, with each AWS service owning one clear responsibility.
- 1
Document intake
Authenticated upload of RFQ packages directly to object storage.
- Amazon API Gateway
- Amazon S3
- 2
Secure storage
Source files and page images in S3; projects and records in DynamoDB.
- Amazon S3
- Amazon DynamoDB
- 3
Processing
Orchestrated extraction of text, tables and positions from every page.
- AWS Step Functions
- AWS Lambda
- Amazon Textract
- 4
AI intelligence
Requirement interpretation, conflict detection, capability matching, RFI drafts.
- Amazon Bedrock
- 5
Engineer workspace
Results, evidence links and recorded engineer decisions in the web app.
- Amazon API Gateway
- AWS Lambda
- Amazon DynamoDB
Amazon S3: Stores uploaded specifications, drawings and manuals, plus the rendered page images used as evidence for each extracted requirement.
Amazon Textract: Extracts text, tables and form fields from native and scanned PDFs while keeping page coordinates, so every requirement links back to its source region.
Amazon Bedrock: Runs the foundation models that turn extracted content into structured requirements, detect conflicts and gaps, compare requirements with capability profiles and draft clarification requests.
AWS Step Functions: Orchestrates the multi-step review pipeline (ingest, extract, interpret, match, assess) with retries and per-step status for each document package.
AWS Lambda: Executes each pipeline step and the application’s business logic on demand, without servers to manage.
Amazon DynamoDB: Holds projects, extracted requirements, capability profiles, engineer review decisions and the audit history of each assessment.
Amazon API Gateway: Exposes the secured API the web application uses to upload document packages, retrieve results and record engineer decisions.
Progress & early access
Where SpecForge is today.
SpecForge is building its initial product. We’re looking for manufacturers who want to shape it with their own RFQ packages.
SpecForge founded
2026
Product workflow and AWS architecture defined
Requirement model, review workflow and serverless pipeline design.
Interactive product demonstration published
The workspace on this page, built with sample data.
Building the initial platform
Document pipeline, extraction and capability matching.
Early access with manufacturers
Applications open now for shops that want to test with real RFQ packages.
Request early access
Tell us about your shop. We’ll follow up by email about the early access program.
Pricing
Simple per-seat pricing.
Pricing that applies when SpecForge becomes generally available. Early access participants are contacted directly.
Starter
For individual engineers reviewing occasional RFQs.
$5per user / month
- Document upload (PDF specs, drawings, manuals)
- Requirement extraction
- Evidence-linked summaries
- Export requirement lists
Growth
Most teamsFor quoting and engineering teams.
$10per user / month
- Everything in Starter
- Conflict and gap detection
- Capability profile matching
- Readiness assessments
- Drafted clarification requests
- Shared review queue
Scale
For multi-site manufacturers and contractors.
$15per user / month
- Everything in Growth
- Multiple capability profiles per site
- Role-based access
- Decision audit history
- Priority support
Prices in USD. Need volume or custom terms? Contact the team.
Team
The Team Behind SpecForge
SpecForge was founded in 2026 by two co-founders building software for the engineers who review what manufacturers make.
Emmanuel Kayode
Founder, SpecForge
Emmanuel founded SpecForge to give manufacturing engineers a faster, evidence-backed way to review incoming specifications and drawings. He leads product direction, company operations and the early access program.
emmanuel@specforge.siteJude Oloyede
Co-Founder, SpecForge
Jude co-founded SpecForge and works with Emmanuel on building the platform, from the document-processing workflow to the engineer review experience.
Contact
Talk to the team.
Questions about SpecForge, a walkthrough of the demo, or a partnership? Send a message or email us directly.