psi*
Log in Book a meeting
Menu
Products
Ontology Org Intelligence psi* Coworkers Agent-Use App Builder
Research and Technology Pricing Docs
Log in Book a meeting

Product | Agent-Use App Builder

Build real GTM apps around the way your company works.

Describe the workflow to psi*. The builder creates structured application source—pages, components, queries, events, data models, and flows—then compiles it into a working app you can inspect, edit, preview, and publish.

Every app shown here was built with psi*. It can connect to production data and systems directly, while the same published capabilities remain available to your team, flows, and AI coworkers.

Book a build session See the builder

One app lifecycle

Define the operation. Compile the app. Release it with control.

Application lifecycle

Define -> compile -> release

01 Define snapshot
Define the operation business logic first

Model the job—not a collection of screens.

Start with a concrete motion such as lead intake, campaign planning, account research, routing, review, or outbound. Define what people need to see, what data the app may read or write, and which decisions should become reusable flows.

purpose-built pagesproduction datadurable flows
  • A complete operating job lives in one application
  • Business rules stay visible instead of hiding in glue code
  • People and AI coworkers use the same bounded capabilities
Application blueprint campaign routing
SURFACE / review queue + routing consoleSTATE / campaign + lead + capacity modelsDECISION / ownership + eligibility + fallbackFLOW / preview -> assign -> confirm -> refreshUSERS / operators + flows + AI coworkers
Compile the system prove the whole application

Validate the interface, data, and automation together.

The compiler resolves every page, query, event, model, policy, and flow as one dependency graph. It catches broken references and unsafe capability bindings before producing a preview that behaves like the application you intend to release.

connected graphpolicy checksexecutable preview
  • Failures surface before anything reaches production
  • The preview includes real behavior—not a screenshot
  • Human and automated paths share one build contract
Validated build selected revision / preview
READ / structured source + resource graphRESOLVE / page -> event -> query -> flowCHECK / schema + policy + permission bindingsBUILD / preview with server actions and flowsPROVE / operator + automated execution paths
Release with control exact revision, explicit authority

Change quickly without losing control of production.

Every edit creates reviewable source history. Teams compare revisions, inspect the compiled preview, and deliberately point production at the approved version. The live app never has to follow an unfinished draft.

revision historyreviewrollback
  • Production never follows an unreviewed draft
  • Every release remains attributable and reversible
  • Built-in RBAC controls who can edit, approve, and publish
Controlled release source history / production authority
BRANCH / isolate the proposed changeDIFF / compare source + behavior + permissionsPREVIEW / compile the selected revisionAPPROVE / record reviewer + release decisionPUBLISH / move production to the exact revision

Apps built with psi*

These are applications made in the Agent-Use App Builder.

Each app begins as structured source, compiles into a preview, and publishes as a real operating application connected to the rest of the psi* platform.

Built with psi*

Lead Intake

Capture raw opportunity signal, normalize it, and finalize the winning campaign before anything downstream opens.

Intake QueueProcessing ReviewCampaign Routing

Queued submissions

runtime state
AccountModeNext step
Asteron AI source-led normalize
Northfield Capital company-led expand people
Kepler Treasury founder-led route review
capturenormalizeexpandroute

Lead Intake

Turn forms, referrals, and opportunity notes into clean company and campaign state.

Replaces
Intake spreadsheets, routing handoffs, and disconnected enrichment steps.
Outcome
A reviewable front door that people, flows, and AI coworkers can operate.

Built with psi*

Campaign Manager

Run research, enrichment, scoring, and pipeline state from the same campaign record instead of splitting work across enrichment sidecars.

SetupResearchEnrichmentScoringPipeline

Campaign-scoped leads

runtime state
AccountStageReady
Meridian Funds research complete A
Beacon Treasury contact verified A
Hudson Markets scoring review B
researchenrichmentscoringpipeline

Campaign Manager

Keep campaign definition, research, enrichment, scoring, and pipeline state together.

Replaces
Point enrichment tools, research sidecars, and campaign-specific spreadsheets.
Outcome
One campaign application with shared context from setup through pipeline.

Built with psi*

Outbound

Generate drafts in batch, review them company by company, and keep approval plus delivery state visible in the same queue.

GenerateReview & SendQueue Audit

Review queue

runtime state
CompanyChannelState
Northline Robotics email draft ready
Atlas Treasury linkedin needs edit
Vanta Capital email approved
generatereviewapprovedeliver

Outbound

Generate drafts, review them in context, approve the right channel, and preserve delivery state.

Replaces
Batch generators, review documents, and separate approval queues.
Outcome
Governed outbound work with the team kept inside the operating loop.

Organizational operating leverage

Adapt / iterate / govern

Your software can change at the speed of the organization.

Business needs do not wait for another implementation cycle. psi* keeps application source, compilation, publication, runtime, identity, and policy in one system so teams can respond without rebuilding their operating stack.

Organizational advantage A shorter path from a new business need to a governed production application.
01 Source-controlled change Adapt

Adapt

Change the application when the business changes.

New processes, data requirements, approval paths, and operating rules become revisioned application changes—not another procurement exercise or brittle sidecar workflow.

Branch with purpose

Change pages, queries, data models, and flows together against the current application source.

Compile before release

Validate references, policies, and runtime behavior in a working preview before production changes.

Publish an exact revision

Release only the reviewed source revision, with provenance and rollback posture intact.

02 One build-and-run loop Iterate

Iterate

Build and operate applications in the same system.

The people improving the application can inspect the same data, actions, flows, and operating context used in production. Feedback becomes a source change and a new preview without crossing product boundaries.

Observe real work

See where operators stall, where data is missing, and where the workflow needs a stronger decision edge.

Change the whole system

Update the interface, business logic, production bindings, and automation as one connected application.

Shorten the cycle

Compile, review, publish, and learn again without handing the workflow between disconnected tools and teams.

03 Published access control Govern

Govern

Authentication and RBAC ship with every published app.

Published applications inherit the platform's identity, workspace, role, policy, and audit boundaries. Teams do not have to rebuild access control each time they create a new operating surface.

Authenticated entry

Users enter through the platform's managed identity and workspace session instead of app-specific auth glue.

Role-based scope

Roles and policies determine which applications, data, actions, and approval paths each user can access.

Governed execution

Sensitive actions stay policy-gated and attributable across the UI, flows, and agent-operated capabilities.

Get started

Bring us the GTM workflow your team has outgrown. We’ll turn it into a working app.

Book a build sessionSee the builder