A commission is two purchases, not one
When someone commissions a bespoke bicycle, a tailored suit, or a piece of handmade furniture, they're buying two things. The first is the object itself — the craftsmanship, the materials, the fit. The second is the experience of having it made: the conversations, the progress photos, and the feeling that someone skilled is giving their full attention to something made only for them.
The instinct to share is already there — the progress updates clients love, the workshop photos of a half-welded frame or a hand-cut dovetail, the decisions explained as they go. The client's involvement is part of what makes bespoke work what it is.
The problem isn't intent — it's infrastructure. An update sent as an email with a photo attachment gets buried, a progress shot sent on WhatsApp disappears into a scroll, and a spec decision spread across three threads and a phone call cannot be found by anybody later. The experience the maker wants to deliver — considered, beautiful, personal — gets diluted by the tools they're forced to use.
One portal, your brand
In Vidual, every client gets a branded portal. Not Vidual-branded — yours. Your logo, your brand colour, your studio name. It looks and feels like an extension of your workshop, not a software product your client has been asked to sign up for.
The client creates no account, sets no password and downloads no app — we do have one, and it's rather nice, but your client doesn't need it. You send them a message from the project, they receive a branded email, they tap a button, and they're in. From that moment, every update, every photo, every file, every payment request lives in one place — their project portal. Organised by build stage, in chronological order, with your brand wrapped around the whole thing.
If they want to reply, they can do it in the portal or simply hit reply on the email. Either way, the message lands back in your project timeline. The client doesn't need to change their habits. But you get the benefit of everything in one place.
Photos and files, in context
When you share a progress photo or a technical drawing from a Vidual project, it doesn't arrive as a loose attachment in someone's inbox. It's embedded in the message, tied to a build stage, with a timestamp and the context of the conversation around it.
For the client, this means they can scroll back through their portal six months later and see every photo from every stage — the raw materials, the first cuts, the test fitting, the final finish — in the order they happened. It reads like a visual journal of the build. For the maker, it means you never have to dig through email threads to find the photo the client liked or the drawing everyone finally agreed on. It's all there, in the timeline, exactly where it was posted.
A client who can revisit the story of their build — who can show a friend the progress photos, who can look back at the moment the colour was chosen — has a deeper connection to the finished piece. That connection is your brand, working long after the handover.
The private layer
Not everything in a build is meant for the client's eyes. The conversation with your paint supplier about lead times, the note to your colleague about a tricky mitre, the cost breakdown on the BOM and the internal debate about whether to change the dropout spec all belong on your side of the wall.
Vidual keeps these streams completely separate. Internal notes live in the same project timeline but are invisible to the client. Partners and suppliers can be invited with controlled access — they post internal notes, see only what they need to, and can never accidentally message the client or see your pricing.
This separation is what makes Vidual feel safe. You can have a frank conversation with a supplier about a delayed shipment in the same project where your client is happily following along with progress updates. The two streams coexist without colliding. There are no "reply all" disasters, no BCCing the wrong person, and no sanitising emails before forwarding them.
From private to shared, in one move
The work that happens privately — the photos taken during fabrication, the files uploaded by a partner, the decisions made in internal notes — can be selectively shared with the client at exactly the right moment. You see a great progress shot in the internal thread? Write a client message, attach the photo, and it's in their portal. A partner uploads a technical drawing? Review it internally, then share a version with the client when you're ready.
The flow is always private first and shared when ready, so the maker stays in control of the narrative and the client sees a considered account of their build rather than the raw chaos of production. And the maker doesn't have to do any extra work to achieve this, because the photos, files, and context are already in the project. It's not about creating content for the client — it's about choosing which moments to let them see.
The industry partner
Not every stakeholder is an end client. Sometimes the person commissioning the build is another brand — a retailer, a distributor, a trade partner who sells your work to their own customers. The relationship is professional, the visibility requirements are different, and the communication needs to stay tighter.
Vidual's Industry Client feature is designed for exactly this. You invite another Vidual account holder to view your project. They see a restricted view — client-facing messages, files, and progress — but no BOM, no financials, no internal notes, no settings. They access it through their own Vidual account, switching between their workspace and yours with the workspace switcher. No separate login, no extra app, no permissions confusion.
And the forward mechanic means an industry partner can take a message from your project — a progress update, a photo, a milestone — and forward it directly into one of their own Vidual projects, where it reaches their end client. Your update, their brand, one unbroken chain.
What this looks like in practice
These are not abstract features but daily rhythms. Three shapes come up again and again:
A first commission is a nervous one — the client is spending more than they ever have on a bicycle, and the bespoke process is new to them. From the first branded email, their portal lays the build stages out in front of them: Design, Order, Frame Build, Paint, Assembly, Delivery.
Updates are posted as the work happens. A photo of the geometry drawing carries a note explaining the stack height choice, a shot of the tubing laid out on the bench follows it, then a close-up of the first mitre. Each one lands in the portal under the right build stage, with the builder's explanation alongside it — and the client can reply in place, and share the progress with whoever they like.
Meanwhile, the internal notes track the real production detail — the message to the painter about the RAL code, the swap of the brake bridge spec, the conversation with the wheel builder about spoke tension. None of it reaches the client; they see the curated story. The result: a client who feels looked after, and a builder who hasn't spent a single extra minute on "client communication" — the updates are the natural workflow, shared selectively.
A bespoke three-piece suit involves more people than the client ever sees: a cloth merchant sourcing a specific bunch, a trouser maker handling the alterations, and the head cutter coordinating the whole thing.
The cloth merchant is invited as a partner with minimal access — they can see internal notes about the fabric order and upload a swatch photo, but they can't see the client's messages, the pricing, or the fitting notes. The trouser maker has full partner access so they can see the client's measurements and fitting feedback.
Fitting photos go up as a client message. The client sees them in their portal — their suit taking shape, pinned and chalked, with a note about the next steps. The trouser maker sees the same photos in the internal thread and knows what adjustments to prepare for. Three people collaborating, one client experience, zero email chaos.
A commission that comes through a high-end retailer has two brands in it — the builder's and the retailer's, each with their own relationship to protect. The builder invites the retailer as an Industry Client on the project.
As the build progresses, the builder posts updates — progress photos, milestone markers, shipping ETAs — and the retailer sees them from their own Vidual account, alongside their own projects. A particularly good progress photo can be forwarded straight into the retailer's own project with the end customer, carrying the retailer's note rather than the builder's.
The end customer sees the update in the retailer's branded portal — not the builder's. The provenance chain stays intact, with the builder controlling what the retailer sees and the retailer controlling what their customer sees. Two brands, one build, complete narrative control at every level.
The Owner's Card — the final chapter
When the build is complete, the story doesn't end. Vidual lets you create an Owner's Card — a beautiful handover document with the product photo, serial number, aftercare notes, and your brand's provenance. It's sent to the client as a branded email, and it becomes a permanent entry in their personal collection page on Vidual.
That collection page is cross-brand. If your client also commissioned a piece from another maker on Vidual — a bespoke bag, a piece of jewellery, a set of shelves — all of their Owner's Cards appear together. A growing archive of everything they've ever had made by hand. Your brand sits alongside others in their collection, a permanent record of the relationship and the craft.
For the client, it's a beautiful thing to have. For the maker, it's the ultimate expression of the idea that the experience doesn't end at delivery. The story of the build, from the first message to the Owner's Card, is preserved for good.
This is the third dispatch from The Workbench. If you missed the earlier posts: why we built Vidual and how the BOM, calendar, and payments work together. More coming soon.