Launched this week
Modulat
Turn client handoffs into branded client portals you own
23 followers
Turn client handoffs into branded client portals you own
23 followers
Handing work to clients always felt broken: you copy a mile-long URL, paste it in Slack, and hope they find it, then iterate and leave them juggling three links. Modulat gives each client one branded page on your own domain that gathers your links, notes, videos and files in one place. Swap the destination anytime and the link stays the same, so they always see the latest. Branded, password-protected, with a Figma plugin and Slack updates for clients. Free links to start; portals from $24/mo
Hey Meta
Hey everyone! I'm Igor, the maker of Modulat ✌️
I built this because handing work off to clients always felt broken. You finish something, copy a mile-long URL, paste it into Slack or email, and hope they figure out what they're looking at. Then you iterate, the tool gives you a new link, and suddenly the client has three URLs and no idea which one is current.
Modulat gives each client one branded page on your own domain instead: a portal holding everything you send them (prototypes, links, notes, videos, images, file downloads), grouped into sections they can always come back to. No accounts for the client, ever. They just open a link.
The three parts I'm happiest with:
It lives in Figma. Turn a frame into a shareable link and drop it into a client's portal without leaving the canvas. No other client-portal tool does this, because none of them are built for designers.
The link never changes. Swap what sits behind it (a new prototype, an updated Drive folder, a revised Miro board,...) and the client always lands on the current version.
Slack knows when you ship. Publish an update and the client's channel gets a message naming exactly what changed, item by item. Fix a typo and it stays quiet.
Beyond that: password protection and expiry for confidential work, three ways a link can behave (instant redirect, inline embed, or a branded page), portals branded to your studio or to the client, team seats so a whole studio works from one account, and a quiet view count so you're not left guessing whether it landed.
You can poke around a real (example) portal without signing up: https://figu.modulat.co
On pricing, so nobody's surprised: the free plan covers branded short links, and you can build a portal and see exactly how it looks. Client portals start at $24/mo (annual saves two months).
I'd genuinely love your feedback. What does your client handoff look like right now, and would this fix it?
🙏
Congrats on the launch! The stable-link-swappable-destination thing is the part that would actually change my behavior. Half the reason handoff feels broken is that v3-final-FINAL lives at a different URL than v2, so clients bookmark the wrong thing and you spend a week re-sending links. Curious what you’re seeing on the client side: do they actually keep coming back to the portal, or is it mostly a one-time open? Feels like the retention answer decides whether this is a delivery tool or a client hub. Anyway, excited to test it out!!
Hey Meta
@nemodesol yes, that's what actually bugged me a lot. Especially since clients either forget what you've sent, and I can't blame them if it's a long email or slack thread, or bookmark a link that might not be the last version or even worse it expired (Figma does that a lot if the product you're working on is ideating a lot).
But to answer your question regarding the retention, from what I can see and hear from clients is that having one place/portal/link as a source of truth means a lot. This is the thing they'll bookmark and go to if they need anything regarding the project, so it's not a one-time open but visited almost daily. For some that link also stayed after the project has finished as a final asset deliverable, so they could reference it for some time too, which was quite a nice use of the product.
Thanks for the support, let me know if you'll have any feedback 🙏
Would love to see a built-in read receipts or view notification for each section so I can tell if a client actually opened the latest files without needing to ping them in Slack.
Hey Meta
@omera29139 this is a request I go back and forth most to be honest. Right now the analytics stay deliberately aggregate. You can see a portal was opened, roughly where from and on what device, but never who, and never which item they clicked. Partly that's a principle: I didn't want this to quietly become a surveillance tool. Partly it's structural, since your clients never create an account, so there's no identity to attach a receipt to. Real per-person read receipts would mean making them sign in, and that's the trade I most want to avoid.
That said, the need behind your question is completely fair, and it's a different question from the creepy one. "Has anyone opened this since I published the update?" is not the same as "who looked at what, and for how long." I think the first is answerable without the second, something like a per-portal signal showing whether it's been opened since your last publish. I also didn't want to give the wrong information in case some of your own team viewed the portal and the system would think it's the actual client.
Worth mentioning the other half of it: when you publish an update, the client's Slack channel gets a message naming exactly what changed. So the default is that they get told, rather than you having to check whether they noticed.
I hope I answered your question 😊
One thing that would really seal it for me: let clients leave feedback or sign off directly on the portal. Right now updates still seem like theyd bounce back to email or Slack, and having a little comment thread or approval button right on the page would keep everything in one spot. Would make handing off work feel way more complete.
Hey Meta
@lhanmarangfclk I've heard this a few times, interesting.
Comments and feedback on design usually wants to sit on the artwork itself, which Figma already does well, and I didn't want to build a second inbox that's worse than the one you have. For now the update lands in the client's Slack and they reply there. At least from my experience, there's a lot of back and forth and replicating something like multi threaded chat would be overkill. At least for V1 😊
Sign-off is the more interesting half, and I think you're right that it's what makes a handoff feel finished. The catch is that an approval only means something if you know who gave it, and clients never make an account here, which is the part I don't want to lose. So it'd have to stay light, a name and a timestamp on the page rather than a login. Which then also means that since it's anonymous the value could be lost...still thinking about this to be honest.
If you test it, I'd like to know whether sign-off alone would be enough, or whether you'd really want the thread too.
Thanks for the support 🙏
finally something that fixes the whole copy-paste-a-giant-link-into-slack mess. swapped out a doc behind a portal link and the client side just kept working, which honestly felt kind of magical.
Hey Meta