Who this is for
Designers, developers, marketers, coaches and analysts who work alone or with one or two subcontractors. You have a handful of active clients, a longer list of past ones, and most of your project talk already happens in Telegram or email.
The material around your work is scattered: proposals in Drive, call recordings in Zoom, decks in email threads, and the handover doc the client needs is a link from three months ago.
The handover nobody can find
A brand designer ships the logo, the colors and a 20-page usage guide. Six months later the client's new marketer asks for "the brand file" and nobody knows which email it was in.
The "how do we deploy this" message
A developer finished the site in spring. In autumn the client writes in the chat asking how to add a page. The answer exists in a doc the developer wrote, on a drive the client never bookmarked.
The consultant's weekly calls
A marketing consultant runs a call every Thursday. Decisions get made out loud, the client's team forgets half of them, and the same question comes back two weeks later.
Why Embedify fits as a client portal for freelancers
Embedify is a private knowledge base: content lives in spaces, and only signed-in members of your workspace can read it. Access groups decide which member sees which space. For a freelancer, that covers two jobs: keeping each client's material in one place, and giving every client the same answers about how you work.
- An open space every client sees. The default space is readable by every member of your workspace, which means every client you've let in. Put there how you work, your services, an FAQ, and case studies you're happy for all your clients to read. The Free plan covers open content with unlimited members reading it.
- A private space per client. Each client gets a space with their brief, notes, decks and handover docs. Access groups keep client A out of client B's work. See spaces and access groups.
- Access that follows the project chat. If you already run a Telegram group with each client, connect it. Embedify's bot checks who is in that group, gives them access to their space, and takes it away when they leave. Details on automatic access for group members.
- Write in Google Docs, publish as pages. Import your docs and keep them in sync. Fix a step in the handover doc, and the client's page updates without a new link. See Google Docs sync.
- Recorded calls people can skim. Put a YouTube or Vimeo recording of a call on a page, and it gets a transcript and an AI summary. The client's team reads the decisions in two minutes. The guide to sharing Zoom and Meet recordings covers getting the file there.
- Decks on the page. Proposals and strategy decks in Google Slides, PPTX or PDF open right on the page, on a phone. See presentations.
- Know if the handover was read. Reading progress shows who opened and who finished each page, so you can see whether the client's team went through the guide before the support questions start.

On Basic and up, the portal opens from your own Telegram bot with your name and avatar. Search covers every page, deck and call transcript a client can open, so "what did we decide about pricing" finds the call where it came up.
Rules for running a client portal
- One space per client, never a shared one. Mixing clients in one space is how an NDA gets broken by accident.
- Treat the open space as read by all clients. Anything there is seen by every client you invite. Ask before you add a case study, and leave out names a client didn't clear.
- The brief sits at the top of every client space. Scope, deadlines and who decides. When scope creeps, you both point at the same page.
- Every call gets a page the same day. Recording, summary, and three lines of decisions you wrote yourself.
- Handover docs are written for the next person. Assume the client's contact will change, and write so a stranger can follow it.
- Keep the source in Google Docs. The doc is the master, the page is what the client reads. Edit in one place only.
- Archive when the project ends. Tell the client how long their space stays open, and keep that promise.
Example structure for a freelance client portal
How we work (open: every client in the workspace)
About me and how I work
Services and what each one includes
Case study: brand refresh for a coffee roaster
Case study: onboarding emails for a SaaS team
FAQ: timelines, revisions, how we start
Client: Acme Studio (Acme project group or email invites)
Brief and scope
Timeline and milestones
Calls
Kickoff call: recording, summary, decisions
Review call 1: recording, summary, decisions
Decks
Strategy deck
Final presentation
Handover
Brand guidelines
File list and where things live
How to request changes
Client: Northwind (Northwind project group or email invites)
Brief and scope
Calls
Handover
Templates (only me)
Proposal outline
Case study outline
Handover checklistThe open space is the shared part of the portal: every client reads the same services, FAQ and case studies there. Each client space has its own access group, tied to that client's Telegram project group or filled with the people you invited by email. The "only me" space holds the outlines you copy for each new project; owners and admins don't use private member seats, so it costs nothing extra.
A worked example: one designer, three clients
Picture a freelance brand designer with three active clients. Two talk in Telegram project groups, the third by email.
Before, every project ended with a zip file, a long email and a steady drip of messages asking for things already sent. With a client portal, the setup takes an afternoon. The designer writes a "how we work" page and an FAQ in the open space and adds two case studies their past clients agreed to share. For each client, they create a private space and add the brief, the timeline and the decks. The two Telegram project groups are connected to their own access groups, and the third client's team is invited by email.
Review calls are recorded in Zoom, uploaded as unlisted videos and added to a call page, where the transcript and summary appear under the video. When a client asks "did we agree on the darker green?", the designer replies with a link to the call page instead of rewatching an hour of video.
At handover, the guidelines go in as a synced Google Doc. When the client's marketer joins the project group later, they get access, open the same space and see the full history. Reading progress shows they finished the guidelines page, so the designer knows the questions that follow are new ones.
A client who can find your work without asking you is a client who remembers you were easy to work with.
Best practices that keep it useful
Use one outline for every case study
Problem, approach, result, what the client said if they agreed to share it. Clients read them faster when every page has the same shape.
Pin the portal in each project chat
Put the button in a pinned message, so the client opens their space from the chat they already use with you. Email clients get the link in your welcome email.
Write decisions in plain words
The AI summary helps people skim, but your three-line list of decisions under each call is what clients act on.
Keep handover docs short and linked
One page per topic: files, logins the client owns, how to change things. Long pages get an automatic table of contents, but short pages get read.
Review the open space every quarter
Keep the services page and FAQ current, and check that every case study there is still one all your clients may see.
How this page differs from others
If you've grown into a studio with staff to onboard, read the small business page; it covers staff handbooks and customer FAQs. If you sell what you know to an audience rather than doing client work, the content creators page fits better. Teams in Telegram have the teams page, and the full list is on who uses Embedify.
When another tool fits better
Embedify is not a website builder, and nothing in it is public. Every page needs a signed-in member of your workspace, and search engines don't index it. There are also no custom domains, no custom page designs or themes, no invoicing, no contracts to sign and no payments.
So a public portfolio for prospects belongs on your own website, Behance or Dribbble. They show galleries and rank in search. Many freelancers keep both: the public portfolio wins the first look, and Embedify takes over once the client signs. You can link to your portfolio from the open space, so clients have it in one place too.
Clients who don't use Telegram can still get in: invite them by email straight into their access group, and they sign in on the web or in the apps with their Google or Apple account. What Embedify doesn't do is the rest of a full client portal: there are no invoices, file uploads from the client side or approval flows.
Choose a website builder or portfolio site
if you need a public portfolio prospects can find, your own domain, a custom design, image-heavy galleries, or invoicing and contracts in one place.
Choose Embedify
if you talk to clients in Telegram or email, write in Google Docs, record calls, and want each client's material in one private space they can find.
A common setup: a public portfolio on your own site or Behance for prospects, and once a client signs, an Embedify invite to their private space and your open "how we work" space.
What it costs
The Free plan is $0 and covers the open space with unlimited members reading it, with Embedify branding. That works if every client may see everything. Private client spaces, your own bot, Google Docs sync and text translation for clients in another language start on Basic from $29/month, with up to 300 private members. Meeting summaries are on Pro. See pricing for the details, or start for free.

