Start here · Practical guideHow to create a client portal: three routes, five steps and what each costs
Read the guide →To create a client portal, pick a portal product or a free plan, add your branding and domain, set up one service with a request form and payment, test it as a client, then invite clients a few at a time.
Practical guideWhat is a client portal? A private login for requests, files, messages and invoices
Read the guide →A client portal is a private, branded login where a client submits requests, reviews files, messages your team and pays invoices, replacing scattered email threads with one record per client.
Practical guideWhat should a client portal include? Seven requirements for a small agency
Read the guide →A client portal for a small agency should include request forms, a status or queue view, feedback on files, billing with checkout, your own branding and domain, role permissions and notifications.
Practical guideIs a client portal worth it? When one pays for itself and when email is enough
Read the guide →A client portal is worth it once requests, feedback and invoices are spread across email threads and nobody can see what is queued.
Practical guideHow to start a productized service business: five decisions from scope to checkout
Read the guide →To start a productized service business, define one service with a fixed scope, choose a flat fee with a queue, hours or credits, publish the price, take payment at checkout and cap active requests.
Practical guideWhat is a productized service? A fixed scope, a published price and one process
Read the guide →A productized service is a service sold like a product: fixed scope, a published price and a standard process, bought at checkout with no custom proposal. Design subscriptions are the best-known kind.
Practical guideProductized service examples: nine companies, how each fixes its scope and what it charges
Read the guide →Productized service examples you can check today include ManyPixels at $699 a month, Penji at $995, Design Buffs at $1,500 for 40 hours and WP Buffs at $89.
Practical guideManyRequests how to use guide: branding, services, intake forms and client invites in eight steps
Read the guide →Brand the portal, create a service, build its request form, connect Stripe, add your team, test as a client, then invite real clients. The official guide lists eight steps and the 14-day trial covers all of them.
Integration guideManyRequests integrations: Stripe, Zapier, Slack, webhooks and portal embeds by plan
Read the guide →ManyRequests has a short native list (Stripe, Zapier, webhooks, Slack, Loom, chat widgets, Meta Pixel) and a longer list of portal embeds. Stripe is the only payment gateway. Webhooks, Slack and the API need Pro.
Practical guideManyRequests API: the plan it needs, how tokens work and the webhook events
Read the guide →Yes. ManyRequests has a REST API with public documentation. The help center says it needs the Pro plan ($99 monthly, $79 per month annually). Webhooks are also Pro. Core has Zapier only.