How to Start Using OpenBOM (Day 22 of 30)

Today, we want to introduce the next group of 30 days articles series – a simple first step toward organized, connected product data

For the last five days, we talked about the architecture behind OpenBOM—composable PLM, multi-tenant SaaS, extended enterprise collaboration, ERP-near-PLM, and what engineering work looks like when intelligent agents operate on shared product memory. Those articles painted the big picture of where PLM is heading and why OpenBOM was built the way it was.

Today, we turn the page.

This is the beginning of the “how do I actually start?” part of the journey.

If you’re an engineer, a buyer, a manufacturing lead, or someone working in a small or mid-sized hardware company, PLM can feel intimidating. Heavy systems, long implementations, big planning sessions, and complex onboarding—none of that is appealing. Most people simply want to start organizing their data, collaborating better, and getting rid of messy spreadsheets… without committing to a giant IT project.

That’s exactly why OpenBOM was created—to make starting simple.

You don’t need a long plan. You don’t need a consultant. You don’t need perfect data. You don’t even need part numbers to be final. You just need one small dataset and a few minutes.

And that’s where Day 22 blog begins.

Starting Should Be Easy

I talk to a lot of teams who assume they need to “get ready” before trying OpenBOM. They want to clean their Excel files, finalize naming conventions, or map the perfect workflow. I always tell them the same thing:

You don’t need any of that to start.

OpenBOM is intentionally designed so you can begin with what you already have, try a few things, and grow naturally. The first steps are lightweight, familiar, and forgiving. The whole experience should feel more like opening a shared Google Sheet than deploying a PLM system.

And the reason it works this way is because of everything we discussed in Days 17–21. Multi-tenancy, composability, and the graph data model are not abstract architecture—they are what make the product simple enough for anyone to try in minutes.

Today we shift from the “why” to the “how.”

The Instant Start

If you’ve never used OpenBOM, the experience is deliberately frictionless.

You open your browser, go to openbom.com, and create a free 30-day trial. There’s no installation, no server configuration, no onboarding call required. You log in, and you’re in.

From that moment, you can begin exploring:

• upload an existing Excel BOM
• import a CAD assembly from SolidWorks, Autodesk Fusion, or PTC Onshape
• create your first catalog of parts
• open a sample BOM and click around
• invite a colleague to collaborate with you

The entire process is quiet and simple. Nothing about it feels like a “software implementation.”

Most users tell me their first impression is: “It works exactly how I expected a modern tool to work.”

And that’s the goal.

Why OpenBOM Is So Easy to Begin With

Ease of use is not an accident. It comes from a few principles baked into the design.

First, OpenBOM is a pure multi-tenant SaaS platform. You don’t manage servers, versions, or upgrades. You don’t install anything except optional CAD plugins. The platform is always up-to-date, automatically.

Second, CAD integrations “just work.” Once the plugin is installed, you log in and generate a BOM directly from your CAD assembly. There’s no manual mapping or scripting. Everything is preconfigured for common workflows.

Third, the interface feels familiar. A BOM in OpenBOM looks and behaves like a spreadsheet—rows, columns, quick edits, immediate updates, automatic saving, and real-time collaboration. If you’ve ever edited a Google Sheet with someone else at the same time, you already understand the model.

And finally, you’re supported at every step. Tutorials, videos, live chat, documentation, and a large community help you move forward without friction. Most people never need formal training—they simply follow short guides or experiment on their own.

The end result is a platform you can start using the very first day.

A First Glimpse of What’s Coming Next

Day 23 is the front door to a series of practical articles designed to guide new users through the essential early steps. Over the next several days, we’ll walk through a path that mirrors the journey many of our customers take.

Tomorrow’s article will explore how to import CAD and legacy data quickly—often the first moment where teams see “real value” instantly appear. After that, we’ll dive into smart part numbering, catalogs, linking objects, building a simple digital thread, and even connecting your BOM to procurement and ordering workflows.

Each of these steps is lightweight and concrete.
None of them require a full PLM project.
They simply build on each other, one small win at a time.

What You Actually Need to Start

Many readers come to the start with a sense of hesitation—worrying whether their data is clean enough or whether their team is ready to adopt something new. Let me reassure you:

You don’t need perfect data to begin.
You don’t need every part number defined.
You don’t even need to set up a catalog on day one.

All you need is something real:

• a small spreadsheet
• a simple CAD assembly
• a list of purchased items
• a quick test catalog

Take that object, import it, and explore.
That one step will show you more than any documentation ever could.

The rest can come later—better structure, better naming, better workflows. OpenBOM will support you as your process matures.

The Best Way to Begin? Start With Something Small

If you’re wondering what the “best” first step is, here are a few that consistently produce good momentum:

Open a CAD assembly and generate a BOM. You’ll instantly see a structured, connected view of your product.

Upload an Excel BOM and compare it with the structured format OpenBOM creates automatically. It’s often an eye-opening experience for teams who’ve been emailing spreadsheets for years.

Create a catalog of purchased parts. Even 15–20 items is enough to feel the power of item reuse and consistent properties.

Invite a colleague to join you. Real-time editing is one of OpenBOM’s strongest features, and seeing it live for the first time is a moment every user remembers.

Start with what’s easiest. Expand with what’s meaningful. Structure will grow naturally.

The Journey Forward

Day 22 marks a shift in this series. We’ve spent five days laying out the architecture and vision behind OpenBOM—why composability matters, why multi-tenant SaaS is crucial, why PLM must extend across companies, and how intelligent workflows emerge from a connected product memory.

Now we move from ideas to action.

Each of the upcoming articles will give you a practical step you can take immediately:

• importing CAD and legacy data
• organizing catalogs and part numbers
• linking objects into real digital threads
• generating RFQs and purchase orders
• sharing BOMs with suppliers

If you haven’t started yet, this is a perfect time.
Sign up, import something small, invite someone you trust, and begin experimenting.

OpenBOM is built to meet you where you are and grow with you as your process evolves.

I’ll guide you through the next steps in the coming days.

Meantime, REGISTER FOR FREE to check OpenBOM by yourself. 

Best, Oleg