Public Portal and Intake Funnel

Generally available
Supplier
From free

A per-org branded public front door for inbound opportunities. An applicant submits by chat or dynamic form without an account and gets a reference number plus a self-serve status page.

Catalogue id
public-portal

Description

What it is

The firm's public, unauthenticated front door for inbound opportunities. Each firm gets a branded portal at {firm_slug}.klarum.com (Next.js middleware rewrites the subdomain to /portal/{firm_slug}). An applicant lands on the branded page, submits a project by chatting with an AI intake assistant or filling a dynamic form (the firm picks which), optionally attaches documents (RFP/EOI/business plan/financial model), and receives a reference number plus a public status page. On the firm side, an admin configures what the portal collects via a no-code inbound form builder. The portal layout is deliberately isolated: no sidebar, no auth guard, no subscription check.

What it helps users do

  • For the firm: turn a shareable URL into a structured inbound channel; every submission becomes a normalised projects row plus a substrate opportunities row, ready for triage. The firm controls branding and field set without engineering.
  • For the applicant: submit in under a minute, conversationally or by form, attach the source RFP, get an immediate reference and confirmation email, and self-serve a status check, all without an account.
  • For the platform: unify inbound/outbound onto one substrate (source_type=inbound) so submissions flow through the same matching/workspace/decision machinery as discovered tenders.

Capabilities

  • Conversational intake assistant

    Generally available

    A stateless slot-filling LLM conversation that collects the submission fields, never re-asks a known field, never invents a value and emits strict JSON at temperature 0.4.

  • One schema, two consumers

    Generally available

    A single builder schema drives both the portal render and the server-side validation, so the form a user sees and the rules the server enforces cannot drift.

  • Reference and status check

    Generally available

    A URL-safe INB-XXXXXXXX reference plus the applicant email acts as a bearer pair for the public status page; a mismatch 404s rather than confirming the reference exists.

  • Rate limiting on an unauthenticated surface

    Generally available

    60 reads, 10 applies and 30 chat turns per minute, with a stateless chat so a bounced visit costs nothing.

Keywords

portal, intake, applicant-chat, form-builder, unauthenticated, branding

Provenance

This page renders a published artifact. Read the same records as JSON if you would rather check the source than the page.