Skip to main content
Launchpad mark
Launchpad by Tessera
Onboarding Wizard (Interview site), development instance
New product
Net-new intake (Step 1b). There is no Application Product to ingest, so the run skips the APO-ingest step and enters the Conversational Planner directly. The seed parsing (reading the BRD and the mockup into prefilled answers) is represented in this development instance; the deep BRD-led elicitation is a follow-up.

New product document type (no APO)

Use this front door when the document type is net-new: there is no legacy application output to learn from, so there is nothing to ingest. Instead you seed the Conversational Planner with a business requirements document and, or, a design mockup, and optionally a driver-file schema definition. ACaaS detects the working sub-mode from what you supply and confirms it by exception. From there the run enters the same wizard, confirm, simulate, and promote flow as an ingested product.

Development instance. SSO is a stand-in field, not a real identity provider. Synthetic and demo inputs only, never a real inbox file or PII.
Sign in (single sign-on stand-in)
In production this is the enterprise single sign-on identity. Access is deny-by-default: the enterprise authorizes who answers each kind of question, and ACaaS routes by question kind.
Declare the net-new document type
The kind of document being created, for example a welcome kit cover letter, a new disclosure notice, or a marketing insert.
Seed the Conversational Planner

There is no Application Product for a net-new type, so the planner is seeded from requirements and design rather than learned from history. Provide a BRD and, or, a design mockup. You may also provide a driver-file schema definition, that is, the field definitions the runtime feed will carry, not any recipient data.

The requirements that describe the document. Its presence sets a BRD-led sub-mode.
A visual of the intended layout. With a BRD present this sets a mixed sub-mode.
A definition of the runtime feed, that is, the field names and types the driver stream will carry. This is a schema, not data. It stands in for the driver stream during elicitation.
Sub-mode (auto-detected, confirm by exception)
Left on auto-detect, ACaaS infers the sub-mode: a BRD present is BRD-led, a BRD with a design mockup is mixed, and nothing supplied is wizard-led. Override it here only if the detected mode is wrong.
Cancel