FAQ

Ultraform is a workspace for designing and reusing reasoning workflows. You decide the steps, rules, and outputs. Ultraform runs them and saves the full history for review. You can also find and run ready-made workflows from the directory, or subscribe to run them on a schedule.

Auditability by default (for workflow owners): every run gets a unique ID and a complete reasoning trace - prompts, bound variables, step outputs, evaluator results, model references, token usage, timestamps, and delivery events.

Chats are one-offs. A workflow is a versioned artifact you can rerun, inspect step-by-step, branch, diff, and roll back. Steps can reuse previous outputs to refine, red-team, and reconcile before the final report. Results stay consistent, not conversational.

Every workflow starts with a form you design. It defines typed inputs (text, number, multiselect, file, URL) with validation and optional prefills. Each form submission becomes a run with its own metadata and trace. The form fields flow into the prompts throughout the workflow.

Initialization: run ID, timestamp, selected version, configuration.

Execution: steps run with dependencies; parallel where possible.

Checks: evaluator gates can pass/score or trigger revision loops.

Output: a report in your chosen format.

Trace access: workflow owners can open the full reasoning trace. Runners typically see the report page (and PDF download) the owner chose to share. Owners can also schedule the same report to run automatically.

Yes. Use conditionals for branches, merge logic for consensus, and review loops that retry until rubric thresholds (or loop limits) are met. You can chain “analyze -> critique -> improve -> rerun” as many times as you need.

Anyone making frequent, important calls where consistency matters:

Growth marketing: daily budget shifts from changing ROAS/CPA.

Sales ops: lead scoring and outreach ranking from CRM data.

Research and publishing: briefs with live sources and citations.

Trading/allocations: rules-based signals and proposals before market.

Healthcare/ops and supply chain: staffing, replenishment, and routing.

Common patterns: analyzer -> critic -> synthesizer for briefs, lead-scoring with rules, and allocation checks against fixed policies.

Yes. Published workflows respect private / team / public visibility. Shared items can pin a verified version so everyone runs the same trusted logic.

No. Use the visual Builder to design steps, checks, and outputs. Developers can also use the REST API, webhooks, or email triggers, and register extensions for custom steps and connectors. (Enterprise Consulting access today; broader self-serve access is planned.)

Each form field becomes a typed variable. Steps reference variables directly in prompts. Required fields validate before execution to prevent incomplete runs.

Every step persists its inputs, parameters, and outputs as addressable variables. Downstream steps bind to any upstream artifact explicitly. Example:

Step 1: “Find big sales today.”

Step 2: “Analyze Step 1 and pick the top three opportunities.”

Add evaluators for coverage, formatting, citations, bias flags, or domain rules. Gates can pass/fail or score. Failed checks can auto-revise and retry. All outcomes are recorded in the trace.

Open the trace. It pinpoints the failing step and shows its inputs and parameters. Adjust the form or the step prompt, then replay to generate a new, fully recorded run.

Yes. Replay the same version with fresh inputs for apples-to-apples comparison. Ultraform records parameters, evaluators, and outputs across runs.

Builder: defines steps, evaluators, versions, and visibility.

Runner: fills the form and executes the selected version.

Trace visibility: by default, only the owner can see the full trace. Owners may opt to share it.

Branch, diff, and roll back. Shared or public workflows can mark a verified version as the default.

Yes. Fix settings (and seeds) for reproducible outputs, or loosen them for controlled variation. Ultraform records the parameters used in each run.

A clean report in Markdown, HTML, JSON, CSV, and PDF. Reports can include images when the workflow produces them. Owners can link the report to the reasoning trace when appropriate.

Yes. Reuse steps, prompts, evaluators, and report templates across workflows. Clone entire workflows and modify from there.

Available today via Enterprise Consulting. Self-serve multi-output routing is on the roadmap.

Yes - via schedule, API, or webhooks. Inbound email triggers are in private preview for consulting clients and planned for self-serve.

Upload draft -> clarity check -> jargon flags -> targeted revisions -> final polish.

Run it on every new draft. Same logic, new input.

Pull yesterday’s metrics -> compare to targets -> propose budget shifts and tests -> email a morning brief.

Schedule daily before stand-up.

Ingest leads (CSV or CRM) -> score fit and timing -> rank top 20 -> generate first-touch openers -> push to CRM and Slack.

Provide topics and source links -> extract facts with citations -> cluster themes -> produce an executive brief with links.

Keep the trace for review.

Load inventory and orders -> detect risks and delays -> recommend replenishment and reassignments -> draft purchase orders or shift notes.

Run on a schedule or on data updates.

They preserve your best-day reasoning as a reusable system. You run the same standard every time and improve it through versioned updates.

You agree on “what good looks like,” encode it once, and run it everywhere - across roles, regions, and days. Teams can still get custom reports by changing inputs while the logic stays constant.

Yes. You get a concise report and, for owners, a complete reasoning history. Add double-checks, rubric gates, and red-team steps to reduce hallucinations or misreads.

Short/long text, numbers, multiselects, files, URLs, and images. You can validate and prefill fields for reliable runs. (Conditional form logic is coming soon.)

Yes. You can prefill with saved defaults or recent values to speed repeat runs.

Coming soon. Today, branching happens inside the workflow steps.

Markdown, HTML, JSON, CSV, and PDF. Workflows can also output images for reports when designed to do so.

Email, Slack, webhooks, or API. Owners can include a link back to the full trace. Runners usually receive a report page and optional PDF.

Yes. Enable web search within selected steps. Store sources in the trace and add citation-coverage checks if needed.

Private preview for consulting clients now; self-serve planned. The inbox parses emails (and attachments) from authorized senders, maps fields, and starts a run.

Free - explore structured reasoning at no cost.

Pro - automate, schedule, and publish workflows.

Enterprise - private or on-prem deployment with deep integrations.

• $5 starter credits
• Full Builder access
• Access to directory workflows
• Manual runs only
• Saved reports and stored traces for later review
• Most directory agents require credits; a few are free.

You can still view your workflows and past runs. New executions require upgrading.

• Everything in Free
• $20 in credits each month
• 60-day credit rollover
• Scheduling and automation (time or event)
• Publish to the public directory
• Priority support

• Private cloud or on-prem with identical core functionality
• Custom connectors (CRMs/ERPs/analytics)
• White-labeling and custom domains
• High-volume operations and SLAs
• Engineering help through Enterprise Consulting

Click Upgrade to Pro in-app.

For private or on-prem deployments, Contact Dave (Enterprise Sales). Your workflows and run history carry forward.

Credits pay for the AI reasoning steps inside runs. Ultraform records tokens and model usage, but you see clear dollar amounts per step and per run.

Data is isolated by workspace and encrypted in transit and at rest. Every run and delivery requires authentication.

Visibility can be private, team, or public. Roles (creator, editor, viewer, runner) control who can build, execute, and inspect traces.

Yes. The same workflow model and APIs run in hosted cloud or on-prem. Logic and artifacts are portable between environments. (Enterprise Consulting recommended.)

Integrations are off by default. Email triggers accept only authorized subscribers. External calls require explicit configuration. You control schedules.

Yes. Audit logs record edits, runs, deliveries, validations, user identity, model choice, token usage, and per-run cost. Retention rules apply; data is permanently purged after the retention window.

Use the REST API to create runs and fetch outputs. Subscribe to webhooks for completion or step events. Deliver results by email or Slack. (Enterprise Consulting access today; broader self-serve access is planned.)

Yes. Register step types, evaluators, or connectors that declare inputs, outputs, parameters, and side effects. Ultraform validates each component’s contract for predictable behavior.

Yes. Theme workspaces, use custom domains, and publish to a private directory. (Available via Enterprise Consulting.)

Yes. Export or clone with templates, evaluators, report definitions, version metadata, and ownership preserved.

Yes. Each run records model choice, token usage, elapsed time, and cost. Billing shows currency totals per step and per run.

Free: community resources.

Pro: priority support.

Enterprise: dedicated assistance and runbooks via Enterprise Sales.

Yes. We help with reasoning design, systems integration (CRMs/ERPs/analytics/messaging), delivery optimization, and private deployments - using the same model and APIs.

Yes. Invite teammates with roles. Control who builds, who runs, and who reviews traces.