The Shop Test

Last week I got invited to a potential client's office. They led me past the boardroom and into the shop. On one of the benches, they had a prototype, half-assembled. Wires everywhere and a whiteboard covered in diagrams.  You can taste it in the air.

That's when I knew we'd work well together.

At ROK, we take the workshop over the boardroom and projector and here's why that matters for software.

When you're building software for hardware with clients, context is everything. You can't architect a system for an underwater robot without understanding it needs to "swim back to the boat" before it can upload data. You can't scope a project for marine sensors without asking about bandwidth constraints offshore.

These aren't details you pick up on a video call. You learn them by standing next to the thing. By asking dumb questions. By seeing what's actually on the bench.
Years ago, we secured a $600K contract by jumping on the ferry the next day to visit a client. One afternoon in their facility clarified scope and established mutual respect for capability that would have taken weeks of back-and-forth emails. And started a relationship.

But it goes beyond the technical.

When we show up, we ask questions most software vendors never ask. What's your five-year vision? How are you monetizing this? What does commercialization look like?  Deployment?  Support and Service model?

Your business strategy shapes the software architecture.

So here's the educational takeaway for 2026.

If you're evaluating a software partner and they're not asking to visit you in person, ask yourself why. If they're not curious about your shop, your product, your business model, your bench test setup, something's off.
The best partners in the software for hardware space don't just write code. They show up. They get their hands dirty. They ask the questions that change everything.

Is your potential partner asking to come see what's on your bench?