Name the client and Juma builds a complete Notion client portal in one run, populated from the brand's website and ready to use the same day.
Share the client name and website, and Juma researches the brand, then builds the full Notion portal: a hub landing page, a brand info page filled in with the client's colors, typography, and tone, a project tracker database, a deliverables and asset library, and a meeting notes log with a kickoff entry. Every page and database is nested under the hub and ready for the team to assign work the same day.
Once the portal is live, the most common extension is a reporting page or KPI database that tracks campaign performance, deliverable status, and monthly outcomes. Point Juma at the existing portal and name the reporting cadence (weekly, monthly, quarterly) and the metrics that matter (impressions, conversions, MQLs, content velocity), and Juma creates a Reports database nested under the hub with rows for each reporting period and the right columns for the named metrics. The output extends the portal without disrupting the existing structure or content, so the team adds new capabilities to a client portal as the engagement matures.
Add a monthly reporting database to the IKEA client portal. Track impressions, conversions, content velocity, and deliverable status per month. Nest it under the existing portal hub.
Brand info pages tend to start as empty scaffolds and stay that way for weeks. This step takes the client's URL and pulls colors, typography, tone-of-voice cues, visual style, and any publicly stated brand guidelines into the brand info page in one pass. The output is a real reference document the team can use on the first deliverable, not a placeholder. For brands with public style guides (PDFs, brand sites, design systems), the Flow links to the source so the team can verify and dig deeper when the brief calls for it.
Populate the brand info page in LEGO's client portal (https://www.lego.com) with their colors, typography, tone of voice, photography style, and a link to their public brand guidelines if one exists.
For agencies onboarding a full roster onto Notion (after a switch from another tool, or after a merger), running the Flow one client at a time is slow. This step takes a list of client names and URLs and builds a parallel portal for each one under a shared Clients parent page, keeping the structure identical across the roster. The output is a fully populated Notion workspace organized by client, with each portal carrying the standard 4-item structure plus the client-specific brand research. Account directors inherit the same starting point on every client, which makes cross-account audits and team rotations far cleaner.
Build Notion client portals for all of these new clients in parallel: IKEA (https://www.ikea.com), Glossier (https://www.glossier.com), and LEGO (https://www.lego.com). Place them under a shared Clients parent page with identical structure.
The portal becomes more valuable once other Juma Flows read from it. Save the portal in the client's Juma Project knowledge once, and the project tracker, brand info, and asset library all become reference material for downstream flows: creator vetting reads the brand voice to keep outreach on-brand, voice of customer analysis stores quotes against the right client, win/loss analysis uses the deal context, performance reports pull deliverable history from the asset library. This step is the handoff that turns the portal from a static workspace into a connected hub the rest of the agency's work runs through.
Save the IKEA client portal as project knowledge in our IKEA Juma Project. Every future flow we run for IKEA (creator vetting, VoC analysis, win/loss, performance reports) should be able to read the brand voice, project tracker, and deliverable history from it.
Teams build one Juma Project per client and add context over time. The client portal flow benefits from four agency-side knowledge items that shape how every new portal gets built. Add them once and the structure stays consistent across the whole client roster, which is the actual point of standardizing portal setup in the first place.
Agency Brand Voice Standards
How the agency writes about its own work: tone, vocabulary, what to avoid. Used when populating portal pages so the language stays in the agency's voice, not the client's. Especially important on hub landing pages and meeting notes templates.
Client Onboarding Checklist
The agency's own day-1 process: which pages get created when, which databases the team uses internally, what gets shared with the client and what stays internal. With this added, Juma builds the portal to match the agency's onboarding sequence rather than a generic default.
Past Client Portals
Example outputs from prior client setups, saved as reference. Juma matches the structure across the roster so the next portal looks like the last one. This is what locks consistency for agencies running 20+ active clients.
Reporting Cadence Defaults
Standard reporting rhythm for the agency: weekly status, monthly performance, quarterly review. Used to pre-fill date defaults in the project tracker and seed the reporting database if a reporting dashboard is added later.
Add a short description to each knowledge item in the project's info field so Juma picks the right files for the right task. For example:
Cloning a template gives the team an empty scaffold; this Flow delivers a populated portal. Juma researches the client's website and fills in the brand info page with their actual colors, typography, and tone of voice, seeds the project tracker with relevant starter projects, adds initial deliverables to the asset library, and creates a kickoff meeting entry in the meeting notes log. Strategy, taste, and the call on which client to prioritize stay human; the Flow handles the scaffolding and the research.
The other practical difference is consistency across the roster. When five account directors each clone the same template manually, they all start adjusting it within five minutes, and within six months the agency has five subtly different portal layouts that nobody can audit. Running the Flow with the same agency project knowledge produces structurally identical portals across the roster, which makes cross-client reporting, team rotations, and onboarding new account directors significantly easier.
Standalone Notion templates also charge per-seat or per-template. Juma's credit-based pricing with unlimited seats means the whole agency can spin up portals without per-user budget conversations.
The default portal contains five components: a hub landing page with navigation and engagement context, a brand info page with the client's colors, typography, tone of voice, and links to public brand guidelines if any exist, a project tracker database with status, priority, owner, dates, and budget columns, a deliverables and asset library tracking type, format, version, and file links, and a meeting notes log with a kickoff entry and a Weekly Sync template ready to duplicate.
Every component is nested under the hub, which becomes the single page the team shares with the client or uses as their daily landing point for that account. The schema for each database is sensible by default and can be extended on subsequent runs without rebuilding the portal. Custom components like reporting dashboards or KPI databases are added through secondary prompts on top of the standard structure.
Both. If the project knowledge points to an existing client portal in Notion, the Flow extends it: adding missing components, populating empty pages, or appending new starter content without overwriting prior work. If no portal exists, the Flow searches the connected Notion workspace for one matching the client name; if nothing is found, it creates fresh under the configured parent page.
For agencies running an existing client roster on Notion, this means the Flow can be used to standardize what already exists rather than rebuilding from scratch. Pointing Juma at an active client portal and naming the missing pieces ("the project tracker is there but we never built a meeting notes log") gets the structure aligned without disrupting the team's current work in the existing pages.
Yes. Save the portal in the client's Juma Project knowledge and every other Flow run for that client can read from it. Creator vetting picks up the brand voice; voice of customer analysis stores quotes against the right client context; win/loss analysis uses the deal information; performance reports pull deliverable history from the asset library.
The portal becomes the source of truth for everything the agency does for that client. Every subsequent flow inherits the context for free, which is the point of standardizing the structure in the first place. Teams running the full agency stack on Juma describe this as the moment the workspace stops feeling like a tool and starts feeling like a system, because the work compounds instead of restarting from scratch every time a new flow opens.
The Flow requires a connected Notion workspace to deploy the portal as a live, editable structure. Agencies that don't yet use Notion can still run the Flow to get the portal blueprint as an in-chat outline they can paste into their current tool, but the bulk capability (deploy → populate → seed starter content) requires the Notion integration.
For agencies considering Notion as a client workspace tool, this Flow is often the trigger that makes the switch worth the effort. The setup cost on Notion drops to minutes per client instead of the hour-plus it takes manually, which is what tips the math for agencies running 10+ active accounts.
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
Start typing a task and Juma will figure out the rest.
