Machinable

• The description states that Machinable is a desktop web app built with Next.js, React, TypeScript, Python, and FastAPI.
• It takes digitally generated PDF drawings and identifies material, stock shape, finished part size, units, part number, and any existing stock callouts.
• It adds machining allowance and looks for standard stock sizes that will work.
• It can calculate cut length, drop length, saw kerf, end trim, and yield when sufficient data is present.
• The app shows the PDF alongside results so a machinist can review findings, correct fields, and recalculate without re-running models.
• The tool uses two GPT-5.6 models (Sol High and Terra High) to read drawings separately, comparing their outputs field-by-field.
• If models disagree on a dimension but agree on material/shape, it still displays the agreed-upon fields.
• Python handles all mathematical calculations including allowance, unit conversion, stock size selection, and yield.

Inference The product is described as a proof-of-concept or pilot tool, not yet integrated into any commercial workflow or vendor system.

• The description states that Machinable aims to help CNC machinists get to a material decision faster.
• It is positioned as an AI-powered solution for pre-production processes in machining.
• The author claims it addresses a common pain point identified through scraping forums like Practical Machinist and Reddit.
• It is described as not meant to make final decisions without human review.
• The tool is framed as solving inefficiencies in the "pre-production" phase of manufacturing, particularly around material selection.
• The author notes that this was submitted for a hackathon, suggesting it's an early-stage prototype.

Inference The positioning is narrow and focused on a specific use case within CNC machining. It does not claim to be a general-purpose CAD or CAM tool.

• The description states that Machinable is designed for CNC machinists.
• It targets users who process part drawings and need to determine raw material stock sizes quickly.
• The author identifies a specific pain point in machining shops: time lost to pre-production tasks like processing drawings and ordering materials.
• It is intended for use by individuals working in machine shops, particularly those using 2D PDF drawings.

Inference The target customer segment appears to be small-scale or mid-sized machine shop operators who rely on manual processes for material planning. No evidence of segmentation beyond this.

• Not evidenced.
• There is no mention of pricing, licensing, subscription models, or monetization strategy in the description.
• The project is described as a hackathon submission and pilot, not a commercial product.
• No indication of whether it will be sold to end-users or integrated into larger platforms.

• Built with Next.js, React, TypeScript, Python, and FastAPI.
• Uses two GPT-5.6 models (Sol High and Terra High) for reading PDF drawings.
• Models are run independently and results compared field-by-field.
• If models disagree on dimensions but agree on material/shape, those fields are shown.
• Python handles all mathematical computations including machining allowance, unit conversion, stock size selection, and yield calculation.
• The interface keeps the PDF next to results for review and correction.
• The app allows users to correct a field and recalculate without re-running models.
• Challenges noted include confusion with dimension/extension lines and chained dimensions.
• The author mentions using Codex to build earlier versions and add features.

Inference The technical stack suggests a modern, full-stack web application. The reliance on two AI models for reading drawings implies an attempt at robustness through cross-validation.

• Not evidenced.
• No revenue data, customer base, or adoption metrics are provided.
• The project is described as a pilot and hackathon submission.
• There is no indication of any live users, feedback loops, or iterative improvements beyond the initial version.
• The author states that the tool is not yet connected to vendors like McMaster-Carr.

• Not evidenced.
• No mention of existing tools in the marketplace for parsing CNC drawings or automating material selection.
• No competitive analysis or differentiation from other AI-based CAD/CAM tools.
• The description does not reference any competitors or market positioning relative to them.

• Unverified claims: All statements are self-reported and unverified. No third-party validation of performance, accuracy, or utility.
• No traction or revenue: There is no evidence of customers, users, or monetization.
• Limited scope: The tool is described as a pilot with future plans to connect with vendors — it's not yet integrated into real workflows.
• AI limitations acknowledged: The author admits that vision models struggle with complex drawings (e.g., chained dimensions), which could limit its practical value.
• Single-person team: Only one developer is listed, raising questions about scalability and long-term maintenance.
• Unclear path to market: No evidence of go-to-market strategy or business development plans.

1. What specific feedback have you received from machinists who tested the tool?
2. How does the tool handle ambiguous or incomplete drawings? Is there a mechanism for flagging unclear elements?
3. Are there any pilot customers or partners currently testing the system?
4. What are the current limitations of the AI models in real-world usage?
5. How do you plan to monetize this tool, and what is your go-to-market strategy?
6. Have you considered integrating with existing ERP or procurement systems used by machine shops?
7. What is the timeline for connecting with vendors like McMaster-Carr?