About JSBS
Built around the work. Designed to connect the system.
JSBS is a founder-led product and services company that combines manufacturing experience, mechanical design, process development, software, and automation to help engineering and manufacturing teams operate with more consistency and shared context.
See how the company works- Founder-led, direct project delivery
- Product and custom-system capability
- Manufacturing and engineering context
- Customer-controlled systems and information
From real work to a usable system
One accountable path from current-state understanding through implementation and handoff.
Operating inputs
- Understand
- Standardize
- Build
- Implement
Connected results
Less translation between sales, scoping, design, implementation, and handoff.
The system is designed around the records, decisions, files, and output that matter.
Ready-made capability where it fits and custom work where the operation needs it.
Useful at any scale and especially practical for small-to-mid-size manufacturers.
Why JSBS Exists
The hardest problems usually live between the tools, departments, and handoffs.
A company may know what the result should be while still relying on disconnected files, manual repetition, individual memory, and systems that were never designed around the people doing the work.
JSBS works across that gap. The company can review the current process, define a usable standard, build or configure the supporting software, connect the technical records, and document the system for the people who will operate it.
The objective is not to replace every tool. It is to create a clearer operating method around the work that already has to happen.
Built for organizations of any size. The model is especially practical for small-to-mid-size manufacturers because it adds structure and connected capability without requiring a large internal development department or a heavyweight system that is difficult to administer.
Disconnected work
- Records live in separate files and tools.
- Repeated tasks depend on memory.
- Standards are applied inconsistently.
- Handoffs lose context between departments.
Connected system
- Related records remain visible together.
- Rules and guided steps reinforce the process.
- Ownership and status are easier to follow.
- Output is organized for the next person.
Founder-Led Company
Direct, practical, and grounded in the work.
JSBS Co. is founder-led by Josh Smith, who remains directly involved in scoping, system design, implementation, and handoff.
The experience behind the work includes mechanical design, plastic-injection-mold-related work, sheet-metal parts and enclosures, wiring-related assemblies, technical documentation, supplier-facing manufacturing work, Autodesk tools, file systems, process automation, databases, and software development.
That combination helps reduce the distance between the business problem, the technical detail, the software decision, and the person who ultimately has to use the result.
Mechanical Design
- Plastic-injection-mold-related work
- Sheet-metal parts and enclosures
- Assemblies, wiring context, and production drawings
- Autodesk Inventor and technical documentation
Manufacturing Operations
- Supplier-facing manufacturing work
- Release packages and technical handoffs
- File systems, part information, and recurring output
- Practical production and DFM context
Software & Automation
- Desktop tools and technical utilities
- Workflow automation and data validation
- Databases, reporting, and guided processes
- CAD, file, folder, and document automation
Product Development
- JSBS Core product architecture and delivery
- Connected engineering, MRP, and commercial records
- Individual and multi-user deployment models
- Ongoing support, iteration, and product growth
The Product Behind the Model
JSBS Core turns the approach into a connected operations platform.
JSBS Core links engineering, manufacturing, materials, and supply records so projects, CAD, ECOs, notes, tasks, BOMs, inventory, vendors, customers, reports, documents, and backups remain connected and easier to find.
- Open a record and see the work related to it.
- Support an individual workspace or a shared multi-user deployment.
- Keep the database under customer control.
- Print clean records or save them as digital PDFs.
Current product direction: engineering, MRP purchasing, receiving, pricing history, and commercial-document workflows are connected today. Deeper production planning, CAD file-structure automation, Autodesk Inventor and SolidWorks manufacturing packages, and communication automation remain areas for continued growth.
One Connected Capability Model
Software, process, and mechanical design belong together when the work crosses all three.
The value comes from understanding the operating context, building the right system around it, and carrying that system through implementation rather than stopping at a recommendation.
01 · Understand
Start with the actual work.
Review the users, decisions, CAD, files, materials, handoffs, current tools, and required output before defining the solution.
- Current-state workflow
- Failure points and repeated effort
- Users, ownership, and constraints
02 · Build
Define and create the system.
Combine standards, data structure, JSBS Core, focused software, automation, documentation, or mechanical-design support as the work requires.
- Rules, templates, and connected records
- Software and automation
- Technical and production-ready output
03 · Implement
Make the result usable and maintainable.
Test the system with real work, document the operating method, support deployment, train users where needed, and define the next owner and next step.
- Testing and feedback
- Documentation and training
- Deployment, support, and iteration
Working Principles
The system should improve the work without becoming another burden.
Good implementation is practical, understandable, maintainable, and clear about who controls the information and what happens next.
Start with reality
Design around the actual process, files, users, exceptions, and downstream output—not a generic framework.
Use what already works
Connect and improve existing tools where replacement is unnecessary, then add new capability only where it creates value.
Keep it maintainable
Choose a right-sized structure the customer can operate, support, and grow without unnecessary complexity.
Keep ownership clear
Define data control, deliverables, responsibilities, documentation, qualified-party needs, and future ownership explicitly.
Built to Grow
Start focused. Expand when the operation is ready.
JSBS can support one recurring task, a department workflow, a JSBS Core deployment, or a broader connected operating system. The starting point should match the current need—not an artificial minimum company size.
Any size, right-sized implementation. The approach can support larger organizations while remaining especially practical for small-to-mid-size manufacturers that want stronger control without a difficult-to-maintain enterprise rollout.
Clear Scope & Accountability
Honest boundaries are part of a professional handoff.
JSBS is a focused, founder-led company. The value is direct involvement, clear responsibilities, practical implementation, and an accurate description of what the company does—and does not—provide.
Work that legally requires a licensed professional, sealed design, regulated approval, certified testing, or specialist responsibility remains with the appropriate qualified party. Outside resources can be coordinated when that responsibility is included in the project.
Founder-led means direct—not artificially large.
JSBS does not present a fabricated national staff, enterprise development department, production-manufacturing operation, or office footprint that does not exist.
Qualified responsibilities stay with qualified parties.
Licensed, sealed, regulated, certified, or specialist work is identified clearly and remains with the appropriate professional or provider.
Based in Pittsburgh, available nationwide.
JSBS is based in the Pittsburgh region and supports remote project work across the United States. No additional office location is implied.
The deliverable includes clarity.
Scope, files, code, documentation, training needs, system ownership, support boundaries, and the next step are defined as part of the project.
Bring the work. JSBS will help define the right system.
Share the process, product, recurring problem, or operating objective. The next step may be JSBS Core, a focused project, or a connected combination of product and custom capability.