Contact JSBS

Start with the work. We’ll find the right path.

Ask about JSBS Core, share a manufacturing or engineering workflow problem, or send a general message. You do not need a complete scope—the first conversation is for understanding the need and identifying a practical next step.

Start a Project Ask About JSBS Core

Send a general message

Product or custom-project inquiries
Software, process, design, and manufacturing systems
Confidentiality can be discussed before files are shared
Pittsburgh-based with remote project support nationwide

JSBSInquiry RoutingOne contact point for product and project needs

Choose a path

What would you like to discuss?

Selecting a route opens the right form and prepares the relevant starting point.

Switch forms at any timeIncomplete scopes are welcomeNo sensitive files required

Contact Forms

Choose the amount of detail that fits the conversation.

Use the general form for a quick message. Use the project form to share the current process, systems, service areas, and desired outcome.

Direct contact

Use the form or contact JSBS directly through the channel that fits the conversation.

Emailcontact@jsbsco.com

Phone(814) 488-3875

Service areaBased in the Pittsburgh region with remote project work available nationwide.

ConfidentialityDiscuss NDA or information-sharing requirements before sending sensitive project material.

Helpful starting material

A rough description is enough. Representative examples can make the first review more efficient.

Screenshots or sample forms
Current software, CAD, spreadsheets, or file systems
Representative drawings, reports, or output examples
The result that should become easier or more consistent

Do not send confidential files yet. First identify any NDA, ownership, access, or information-handling requirements.

Send a general message

For introductions, collaboration, general questions, or anything that does not need a project brief.

Name *

Email *

Company

Subject *

Message *

Your information will be used only to review and respond to this message. Do not send confidential files or sensitive project information until any required NDA or information-sharing expectations have been discussed.

What Happens Next

A straightforward starting process.

The first goal is to understand the work well enough to identify a practical scope, delivery path, and next decision.

Step 01

Review the inquiry

JSBS reviews the process, product question, systems, files, users, current friction, and desired outcome you provide.

Step 02

Clarify what matters

A short call, representative files, screenshots, drawings, examples, or deployment details may be used to define the real requirement.

Step 03

Recommend a path

Once the need is understood, JSBS can outline the proposed product, service, deliverables, responsibilities, timing, and pricing approach.

Product purchase or deploymentFocused custom projectConnected product + service engagement

JSBS Core

Questions about the connected operations platform?

Use the product inquiry route for licensing, Solo or Team deployment, database ownership, product fit, purchasing, demonstrations, or questions about the current engineering, MRP, purchasing, and commercial-document workflows.

Licensing and seat questions
Solo or multi-user deployment
Customer-controlled data
Current capabilities and roadmap

Ask About JSBS Core View the Product

JSBS CoreProduct inquiry workspace

Ready to discuss

Choose the product topic

Start with one question or combine several areas in a single inquiry.

LicensingSeats, annual licensing, purchasing, and product access.

DeploymentSolo, Team, multi-user databases, backups, and data control.

Product fitModules, linked records, print and PDF output, and operating use.

RoadmapDeeper planning, CAD-package, and communication automation.

Native Windows productCustomer-controlled databaseIndividual or shared use

Before You Reach Out

Helpful details for the first conversation.

You can begin with incomplete information. The purpose of the first exchange is to make the next step clearer.

What should I send first?

Start with a short description and representative examples such as screenshots, sample spreadsheets, folder structures, forms, CAD files, drawings, photos, reports, or documents. Do not send sensitive information until confidentiality requirements are clear.

Do I need a complete scope?

No. The conversation can begin with a recurring problem, a desired output, a JSBS Core question, or a workflow employees find difficult to perform consistently.

Can I use this page for JSBS Core questions?

Yes. Select “JSBS Core / Product Question” in the project or product form for licensing, deployment, purchasing, product-fit, demonstration, or roadmap questions.

Can JSBS work with our existing systems?

Yes. The starting assumption is to understand and improve the environment you already use. Replacement is recommended only when it is genuinely necessary.

Can software, process, and mechanical design work be combined?

Yes. A project can begin with one focused capability or connect software, process development, mechanical design, technical documentation, and JSBS Core around a shared operational goal.

Not sure which route fits? Start with a general message.

Describe what you are trying to improve. JSBS can help determine whether the next step is a product conversation, a focused project, or a connected combination of both.

Send a General Message Start a Project

Start with the work. We’ll find the right path.

What would you like to discuss?

Choose the amount of detail that fits the conversation.

Send a general message

Thanks—your message has been sent.

Tell JSBS about the work

Thanks—your inquiry has been sent.

A straightforward starting process.

Review the inquiry

Clarify what matters

Recommend a path

Questions about the connected operations platform?

Choose the product topic

Helpful details for the first conversation.

Not sure which route fits? Start with a general message.