The Distance Between Maker and Client
- Contributor - Bhavana Ramesh
- 6 min read
Share:
Design reviews used to be a mess. An engineer would finish a revision, export the file, attach it to an email, and wait. The client might not open it for hours, sometimes from a different time zone entirely, then they’d try to guess what the engineer meant from a flat image with no context. Questions would pile up. Half the time, by the time anyone actually got on a call, the conversation was less about the design and more about figuring out which file everyone was even looking at.
Most firms just accept this as normal because it’s what everyone’s always done. It’s really just a side effect of using tools built for one person working alone, not a firm and a client trying to work through something together.
When our product engineering team moved its design work onto Onshape, we talked about it internally as an operational upgrade, mostly concurrent editing and not having to hunt down the right file version. Those benefits turned out to be real. What surprised us was something else. We ended up a lot closer to the clients we work with, and that mattered more than the speed did.
Built for Fighter Jets, Not for Conversations
CATIA is the software Dassault used to design the Rafale fighter jet. It handles serious aerospace-level complexity, but it’s expensive and takes years to learn well, since it was built for one expert working alone, not a design firm walking a client through a decision.
Our clients aren’t designing fighter jets. Most of them don’t want to learn a piece of enterprise software just to understand their own product. What they need is a way in that doesn’t require training, and that’s what Onshape gives them. It costs less and runs in a browser, so instead of the old file-based system where every version lives somewhere different, everything just lives in one place people can actually get to.
From Delivery to Joint Ownership
Most client relationships keep the actual design work out of view. The client sees whatever gets sent over, not the version that got scrapped or the reason a certain constraint shaped the final call. That gap creates a weird kind of friction. The client has to trust the process without seeing it, and the firm has to explain decisions without actually showing the work behind them. Neither side has the full picture, and it tends to show up in small ways, like a tense budget call or a deadline conversation that goes sideways for no clear reason.
Cloud platforms change that. When a client can open a browser and watch the model change in real time, the calls start feeling different. Instead of a status update, they’re watching us work through a problem as it happens.
That’s usually when they start asking questions instead of waiting for the next update. We’re giving them a real say in how the design comes together while it’s still being figured out. They ask questions and push back when something doesn’t sit right. By the time a project wraps, they’ve usually had a hand in most of the decisions along the way.
The Single Source of Truth
The old workflow left behind a mess of half-finished files: renamed exports and screenshots marked up in a hurry. The client had to piece together what was current from whatever landed in their inbox last.
Onshape fixes that by keeping one model in one place. When the client opens it, they’re looking at exactly what we’re looking at. There’s no guessing which version is current and nothing to reconcile between two people’s copies. It’s just the model, and everyone sees the same one at the same time.
That sounds like a small thing, but trust really does run on this kind of alignment. Small mismatches between what a client sees and what we see are usually where doubt creeps in. Once there’s only one version to look at, that problem mostly goes away, and everyone gets to spend their time on the actual design instead of chasing down which file is right.
The Routine Remains Sacred
A lot of firms assume better collaboration means asking clients to change how they work: new software to install, a new interface to learn. We went the other way. Good collaboration should slot into whatever a client’s already doing, not ask them to rearrange their schedule around it.
Onshape runs in a browser, so there’s nothing to install and no license to manage. A client can pull the model up on a laptop at their desk or check it from a phone between meetings. They don’t need to become engineers, they just need a link and a few minutes.
That low barrier isn’t just convenient. It’s a way of showing respect. We’re asking for their attention and their judgment, not asking them to learn a new system first.
Why Seeing the Work Changes the Work
This matters more than any efficiency number shows. Fewer emails, shorter revision cycles, sure, but the bigger shift is how people think about the work. When a client watches a decision get made instead of hearing about it after the fact, they start to understand the tradeoffs on their own. Why one angle got picked over another. Why a material got dropped. For a few minutes, they’re thinking about the problem the same way we are.
One of our senior engineers ran into this on a project with a medical device client. The client wanted a housing change that would’ve broken sterilization compatibility. Normally that’s a long email and a few days of back and forth. This time, the client joined a live session and watched us test the change against thermal constraints. They saw the interference problem show up on screen before we’d even finished explaining what we were testing for. Nobody got defensive about it. The client ended up suggesting a fix we hadn’t thought of, one that solved the sterilization issue without giving up the design change they actually wanted.
The Paradox of Openness
Some people assume this kind of access wears down professional boundaries, like a client is going to start second-guessing every decision that took years to learn how to make. That hasn’t matched what we’ve seen.
One of our design directors put it this way: clients seeing more of the process doesn’t make us look less skilled, if anything they get why some things take as long as they do. When it’s real access and not some curated version of it, people tend to respect the work more. Once someone’s actually watched how complicated the process is, they stop asking for things that aren’t realistic, because they’ve seen where the limits actually are.
It's Also Good for Business
There’s a business angle here too. When a lot of firms can offer similar technical chops, a finished design is only part of what a client is paying for. What the process felt like along the way matters too, sometimes more than people expect.
A process that feels closed off says something about how a firm operates. An open one usually says something better, that the firm has enough confidence in its own work to let a client watch it happen in real time, without spending time polishing it before anyone sees it.
Cloud tools get credit for keeping distributed teams running and covering for people out sick, which is true, but that’s really just describing the plumbing. The bigger change is what happens between a firm and its client. A shared time zone or a shared room used to matter more than it does today. What actually helps is looking at the same problem at the same time, wherever everyone happens to be sitting.
What We Are Still Learning
We’re still figuring out what this changes about how we work day to day. Some clients want updates constantly. Others check in occasionally and only step in when something actually needs a decision. Both work fine, because the platform doesn’t force anyone into a specific rhythm. We don’t expect every client to watch every small change we make. What matters is that the wall between us and the client isn’t as solid as it used to be, and that changes how trust gets built over time.
Cutting friction really just means getting rid of whatever gets in the way of two people trying to solve a problem together. Good client relationships have always worked something like a partnership. What’s different now is that the tools can actually keep up with that idea, at the pace modern product development moves.
The work is out in the open now, and something worth paying attention to is happening on both sides of the screen.
See what a transparent design process looks like
If your current design partner still works behind a curtain, it doesn’t have to stay that way. Explore our work to see how real-time collaboration has changed outcomes for clients like ours, or start a project and get your first working session on the model itself, not just a proposal. Prefer to talk it through first? Book a 30-minute call with our team.