Implementation guide

How to Build a Client Portal App with AI

Plan the member journey, choose Web or Android, connect existing Client Portal capabilities and protect CRM and Custom Object visibility before publishing.

Explore Client Portal & App Builder

Start with the customer job—not the app screens

Define what a signed-in customer should accomplish: continue a course, join a community, book an appointment, access a file, view permitted data, pay an eligible invoice or request service.

Treat Client Portal as the member foundation and Client App Builder as the AI creation layer.
Choose Web or Mobile carefully; the project type cannot currently be switched later.
Map member roles and record visibility before adding CRM-driven screens.
Start with one complete customer journey rather than many unfinished pages.
Test every action as the intended member, not only as an administrator.

Client Portal app setup, step by step

1. Confirm prerequisites

Enable the documented Client App Builder access for the sub-account and review existing courses, communities, calendars, files, member accounts, CRM data and Custom Objects.

2. Choose Web or Mobile

Use Web for browser access, shareable URLs and supported custom domains. Choose Mobile when the planned deliverable is a signed Android APK. iOS generation is not currently documented.

3. Choose a starting point

Describe It Instead creates a custom experience from a natural-language brief. ClientPortal Standard starts from the familiar portal structure and connected features.

4. Write a focused brief

Describe the audience, main tasks, required pages, brand direction, data sources and success condition. Ask the builder for a clear plan before generating.

5. Connect member capabilities

Add the appropriate courses, communities, appointments, shared files, accounts and supported invoice actions already configured in the sub-account.

6. Configure CRM data safely

Use supported CRM information and Custom Objects only after defining whether members can see their own, company or other permitted records. Test with realistic member accounts.

7. Review design and navigation

Check mobile and desktop layouts, labels, empty states, errors, sign-in, menus and calls to action. Keep the most important member task easy to find.

8. Test the complete journey

Test invitations or sign-in, permissions, content access, bookings, files, records and supported payments. Verify that one member cannot see another member’s data.

9. Publish the web experience

Publish to the supported hosted address or an eligible custom domain. The active Client Portal domain cannot be reused for the app.

10. Prepare Android delivery

For Mobile projects, prepare the documented app name, icon, splash screen and optional configuration file, then generate and test the signed APK. Direct store publishing is not currently included.

Example customer experiences

Gym or coach

Programs, course progress, class bookings, community, files and member check-ins.

Clinic or service business

Appointments, approved preparation resources, forms, files, invoice actions and service requests.

Agency or B2B provider

Onboarding, shared resources, permitted project or account records, bookings and support access.

Common planning and publishing mistakes

Choosing the wrong project type

Web and Mobile are selected at creation and cannot currently be switched later.

Building before permissions

Design member and company record visibility before exposing CRM or Custom Object data.

Treating it as unlimited custom software

The builder works within supported Client Portal and CRM capabilities—not arbitrary backends, databases or npm packages.

Assuming every payment flow is supported

Documented payment support is invoice-based; a fully custom checkout is not currently supported.

Skipping real-member testing

Administrator access can hide permission, empty-state and navigation problems that members will encounter.

Current product scope

The documented builder supports branded web portals and Android APK projects connected to Client Portal capabilities. Current limits include no iOS generation, no direct app-store publishing, no arbitrary server backend, no third-party npm packages and no custom checkout. Availability and limits can change, so confirm them before committing to a delivery plan.

Client Portal app setup questions

Is Client App Builder part of Client Portal?

Yes. Client Portal is the member foundation; Client App Builder is the AI creation and customization layer.

Can I switch a project from Web to Mobile?

No. The project type is selected at creation and cannot currently be switched.

Can it build an iOS app?

Not currently. The documented mobile output is a signed Android APK.

What is the most important test?

Test permissions with realistic member accounts and confirm each member sees only the appropriate records and actions.

Build one valuable customer journey first

Prototype, test permissions with real member roles and publish only after the full experience works from sign-in to the intended result.

See plans and pricing