Skip to main content

Experience layer Available

Client, vendor, resident and employee portals, built with AI

Kinetic's experience layer is where you build the screens people use when they need something from your organization: portals, forms and apps. AI drafts them through MCP and your team approves them. Every screen reads from and writes to your existing systems, so people ask once instead of learning five.

Book a working session

Real screens An employee portal built on Kinetic: open tasks, tickets and an AI assistant on one page.

An employee portal built on Kinetic. The page asks 'What do you want to do?' and shows a My Work panel with open task cards for finance and compliance requests, plus sections for the person's tickets, surveys and assets.
Finance and compliance tasks on one page, though different systems do the work.
The same employee portal with an AI assistant panel open. The assistant lists the company's observed holidays and points the employee to the annual leave request form to ask for time off.
Asked about holidays, the assistant lists them and links the leave request form.

Bought systems give every audience someone else's screens

An ERP is designed for the finance team, and a case system for caseworkers. The supplier, the resident and the new hire get whatever screens are left over. So suppliers email PDFs, residents fill in a different form for each department, and employees guess which of five systems handles a laptop request.

Teams patch it with a form tool and a spreadsheet. The experience layer replaces those patches with one front door per audience.

A portal for each audience, one set of workflows underneath

Underneath, every portal shares the same workflows and connections, so the fourth one starts with most of the work done.

  • Client portals

    Clients open and track requests in one place. Staff work them from the CRM they already use.

    Client Management

  • Vendor and supplier portals

    Suppliers upload certificates and check invoice status against the ERP, instead of emailing accounts payable.

    Vendor onboarding

  • Resident portals

    A resident applies for a building permit once, and licensing, payments and inspections each pick up that same request in their own systems, so nobody asks the resident for the same details three times.

    State and local government

  • Employee portals

    Every HR and IT service on one page, with ServiceNow and Workday doing the work behind it.

    Service Management

Built with AI through MCP

AI drafts the portal, and your team decides what goes live

Because the assistant builds inside Kinetic, its first draft already uses your connections and access rules. It is a working portal your team can click through and test, with real lookups against your systems.

Follow a full build, step by step
  1. 01 Describe it In an MCP-capable assistant such as Claude: “Suppliers upload a new insurance certificate each year. Check the supplier number against the ERP before accepting it.”
  2. 02 AI builds it in Kinetic Through the MCP server, the assistant creates the form and portal page in a development space, using connections your team already set up.
  3. 03 Your team reviews it Someone checks the wording and who can see what, in the form builder they already use.
  4. 04 A person promotes it The approved version moves to production. The next portal starts from these forms and connections.

Forms that know what your systems know

Each form pulls live data through the integration layer and, on submit, starts a workflow in the workflow layer. Nobody retypes a submission into another system.

The Kinetic form builder. On the left, a form's page and sections with fields such as name and file attachment. On the right, form settings including a bridged resource named User that pulls user records from a connected system.
The form builder, with a resource that pulls user records from a connected directory.

  • Forms that already know the answer

    A supplier enters a tax ID and the form fills in the company name and remit-to address from the ERP.

  • Only the questions that apply

    An overseas supplier sees the W-8 upload. A domestic one never does.

  • One status, however many systems

    Requesters check progress in one place while the work moves through three back-end systems.

Requests from Teams, Slack or an AI assistant

Kinetic is headless: every form and request is available through its API, so the portal is one front door among several.

There is no ready-made Teams or Slack app. Customers who want one build a small plugin against the Kinetic API, and requests raised in chat run through the same workflow. An MCP-capable assistant can also find, submit and track a request for whoever is signed in.

What AI does on a portal, and what it leaves to your team

AI does

  • Generate forms and portal pages through the MCP server.
  • Submit and track requests for a signed-in user, through an MCP-capable assistant.
  • Point people to the right request, when you add an assistant to the portal.

AI does not

  • Decide who can see a portal. Your access rules do.
  • Make up a request's status. Status comes from the workflow and your systems.
  • Move a draft to production. A person promotes the approved version.

A resident portal built on this layer

Every search result and tile on this page opens a Kinetic form. The city changes the catalog in the console; residents see the change the next time they visit.

City of Cedar Harbor resident portal home page with a service search box, quick links for missed garbage pickup, pothole, streetlight out and bulk trash pickup, and panels to create an account or look up who serves your street.
A resident portal built in the experience layer. Every tile and search result opens a Kinetic form. City of Cedar Harbor · fictional organization, sample data

What you can build next

Your first portal's sign-in and connections carry over. Any of these would make a good second build.

Frequently asked questions

Answered by Kinetic Data. Last updated .

  • What is the Kinetic experience layer?

    The part of Kinetic people see: portals, forms, service catalogs and apps. Screens read and write your existing systems, so there is no data migration, and every submission starts a workflow.

  • How does AI help build a portal?

    You describe the portal to an MCP-capable assistant, and it creates the forms, fields and pages inside Kinetic through the MCP server, which is generally available. Your team edits the result in the form builder before a person promotes it.

  • Is there a Microsoft Teams or Slack app?

    There is no ready-made one. Because Kinetic is headless, customers who want requests in Teams or Slack build a small plugin against the Kinetic API. MCP-capable assistants can also submit and track requests for a signed-in user.

  • How do people sign in to a Kinetic portal?

    Employees sign in through your SAML or OIDC identity provider, such as Entra ID or Okta, and government users can sign in with CAC or PIV cards. External portals can have their own sign-in.

Bring one process. Leave with a plan to build it.

Two hours with our team, at no cost. Bring the portal your clients, suppliers or staff keep asking for. We sketch it against your real systems and send you a written plan afterward.

Book a working session