How to use ManyRequests: first setup of services, intake forms and client invites

The short version of a first ManyRequests setup

To use ManyRequests, you set up your portal, create at least one service with a request form, connect Stripe, and invite clients, who then submit requests that your team works through. The official getting started guide, dated March 2026, gives that order in eight steps. This page follows it and adds the menu paths from the linked help articles.

This is documentation-based research. This site has not set up a ManyRequests portal itself.

What you need before you start

• A ManyRequests account. The trial lasts 14 days and needs no card. After that, Core is $59 per month on monthly billing or $39 on annual billing, as read on 3 October 2026.
• A Stripe account if clients will pay through the portal. Trials on recurring services cannot be created until Stripe is connected.
• Your logo and brand colors, and access to your DNS if you want a custom domain. Custom domains are included on every plan.
• A written list of the services you sell, with price and what you need from the client to start each one.
• A seat for each team member. One seat is included. Extra seats on Core cost $20 per month on monthly billing.

Not sure what to package? See what a productized service is first.

The eight setup steps from the official guide

1. Customize the client portal. Add your logo, colors and domain. This is what clients see, so the guide puts it first.
2. Create your first service. Go to Services, then All Services, then Create Service. Choose recurring or one-off, fill in the service details, then the pricing. On a recurring service you can cap active requests at one time and requests per month.
3. Build the request form. It is the third screen of the service editor. A Title field is there by default. Add fields such as short answer, paragraph, file upload, single or multiple selection and date. Conditional rules can show or hide a field based on an answer.
4. Connect payments. Open Modules and Extensions, choose Billing, and switch on Connect to Stripe. You are sent to Stripe to approve the connection.
5. Add your team. Invite team members and set their permissions before real work arrives.
6. Add or invite clients. Click Users, then Clients, then Create Client. Enter the name, email and organization. The client gets an email with login instructions.
7. Start receiving requests. Clients submit through the form. Your team manages them in list or kanban view. The plan table also lists a queue view, but the help center's article on it, dated June 2024, says that for now only clients see it.
8. Set notifications. Decide which emails and alerts go to the team and to clients.

Worked example: a design subscription with one active request

Say you sell unlimited graphic design for a flat monthly fee, with one request in progress at a time.

Save the form as a template from the three-dot menu beside Preview, so your next service can import it instead of starting again. For the reasoning behind request limits, see credits versus hours.

The mistake to avoid: inviting clients before you test as one

Creating a client sends that person a login email straight away. If the form is half built or Stripe is not connected, that is the first thing they see. The help center gives two ways to check first.

• Create a test client. Open your portal link, choose Create new account and register with a spare email address. Or add one under Users, then Clients, then log out and sign in as that client.
• Impersonate a client. Under Users, then Clients, click the three dots next to a client and select Impersonate.

Submit one test request from start to finish, including payment. The official guide says most good setups come from small adjustments after real use, not from one perfect first configuration.

After the first request

Once requests flow, the next jobs are a repeatable welcome sequence and moving existing clients across. The client onboarding guide covers the first, and the staged migration plan covers the second. The vendor's pricing page FAQ says it offers free migration help on all plans for importing clients and active subscriptions, but the plan table on the same page ticks migration help for Pro only, so confirm it before you rely on it on Core.