You bought a Cobot Welder. Production is up, your welders are happier, the math made sense.

Now you're thinking about cobot #2.

The instinct is to buy another welder – more of what worked. Stack capacity in the place you already proved automation can win.

Is it the right move?

The bottleneck moves

Here's what happens when you automate one process: the constraint shifts.

Before cobot #1, welding was your slowest step. That's why you automated it. Now welding is fast — sometimes dramatically faster. Which means welding is no longer the bottleneck. Whatever was the next slowest process is now the one limiting your output.

If you add another Cobot Welder, you're stacking capacity in a place that's no longer the constraint. The new welder will run, but the line as a whole won't go much faster, because the slow step is somewhere else now.

This is the part most shops don't model when they plan for cobot #2. They look at the success of cobot #1 and assume more of the same equals more of the result. The math doesn't work that way once the bottleneck has moved.

Read more on finding your real bottleneck: Welding Automation Planning Guide for 2026 →

The Tank Technology case

Tank Technology, an employee-owned manufacturer of custom porcelain-lined water heaters, was running into this exact problem.

A quarter of their product line was built-to-order — custom diameters, shapes, fittings. Manual plasma cutting was producing inconsistent results, and 25% of parts came back for rework. Even with a skilled team, variability was baked into the upstream process.

That variability didn't just slow down cutting. It rippled forward. Inconsistent cuts meant inconsistent fit-up at welding. Welders spent extra time compensating for parts that didn't quite match the fixture. The whole downstream line moved at the speed of the slowest input.

When Tank brought in a Cobot Cutter, the cutting problem solved itself. Cycle times dropped from 3 minutes to 11 seconds. Rework went from 25% to nearly zero.

But the real story isn't what happened to cutting. It's what happened to everything downstream of cutting.

"With the Beacon Cobot Cutter, we're seeing perfectly sized holes in perfect locations — every time," said Eric Parmenter, ASME Production Lead at Tank Technology. Once cuts were consistent, fixtures fit better. Welders ran cleaner. The shop started plasma-cutting parts they didn't think were possible — beveled heads and bases with compound curves — which opened up new product capabilities entirely.

Cobot #1 didn't have to change. The thing feeding cobot #1 changed. And cobot #1 got better as a result.

Read the full Tank Technology case study: Tank Technology Inc. →

The multiplier effect

This is the math the spreadsheet usually misses.

When you add cobot #2 in a different process — especially upstream of cobot #1 — you don't just add cobot #2's capacity. You unlock capacity that was already in cobot #1 but constrained by the process feeding it. More wire goes to actual welding instead of compensation. More gas goes to good welds instead of rework. More operator attention goes to programming instead of fit-up firefighting.

The same logic runs the other direction. Add a Cobot Painter downstream of welding, and paint can finally keep up with the welder. The whole line runs at the rate of automation, not the rate of the slowest manual step.

Two cobots in different processes may be worth more than two cobots in the same process – not because the math doubles, but because the bottleneck stops moving against you.

How to find your real bottleneck

Before you spec cobot #2, walk the line. Three questions tell you most of what you need to know.

1. Where do parts wait? The station with the longest queue in front of it is your real constraint. If parts are piling up before cutting, cutting is the bottleneck. If they're piling up before paint, paint is. The location of the pile-up doesn't lie.

2. Where does rework start? Rework usually has a single origin point — a process whose inconsistency cascades downstream. If your welders are constantly compensating for bad fit-up, the welder isn't the problem. The cuts are. Adding another welder makes the rework problem twice as expensive.

3. Where do operators spend time fixing inputs instead of running their station? If your most skilled people are bridging gaps between manual processes, automating one of those processes frees their time across the whole line, not just at one station.

The answers won't always point to your most obvious problem. Sometimes the slowest-looking station is fast and the fastest-looking station is creating drag everywhere downstream. Walk the line with fresh eyes.

The platform makes this honest

There's one more reason this matters, and it's specific to how Beacon works.

Cobot Welder, Cobot Cutter, and Cobot Painter all run on the same platform. Same app. Same operator interface. Same support model. Same data visibility. That means when you decide cobot #2 belongs in cutting instead of welding, you're not learning a new system. Your team already knows how to run it. The fixturing logic transfers. The programming logic transfers. The support relationship transfers.

That's not a coincidence — it's the point. A platform that only runs welders forces you to keep buying welders. A platform that runs all three lets you put cobot #2 wherever the bottleneck actually is.

We can give you that answer honestly because we sell all three. The right cobot for cobot #2 is the one that moves the bottleneck for your shop. Sometimes that's another welder. Often it's not.

The decision worth making

The shops that scale automation well don't think in terms of more cobots. They think in terms of where does the bottleneck go next.

Cobot #1 proves automation works in your shop. Cobot #2 proves you understand your own line. The hardware will run either way. The question is whether the second purchase moves your output forward or just adds a faster step to a process that's already not the constraint.

Walk the line. Find the wait. That's where cobot #2 belongs.

Where to go from here:

• See the Cobot Cutter in action → Cobot Cutter
• Read the full argument for platform-first thinking → Read the blog
• Talk to someone about your specific bottleneck → Contact