Pilot Kit

This kit helps a customer evaluate EntryLayer with a concrete Snowflake-backed workflow instead of a broad platform trial.

Pilot goal

Prove that a team can turn Snowflake-backed exception records into a structured form, work queue, review process, audit history, and customer-controlled extraction path without moving the process into a separate SaaS data layer.

Best first use case

Choose a workflow with these traits:

Trait	Why it matters
Records already live in Snowflake	The pilot starts from an existing table or view.
Humans already review exceptions	The value is visible because a manual workflow exists today.
The workflow has a small reviewer group	Fewer roles make setup faster.
Approved records have a clear downstream meaning	The team can define what success looks like.
Data can be synthetic or non-sensitive for the pilot	The team can move quickly without waiting on every production approval.

Common examples include order exceptions, reference data corrections, provider/vendor review, finance adjustment review, quality issue remediation, and operational intake triage.

Snowflake admin checklist

Before the pilot session, confirm:

EntryLayer is installed from Snowflake Marketplace.
Required Native App privileges are granted during install.
SNOWFLAKE.CORTEX_USER is granted if Cortex-assisted generation will be used.
At least one Snowflake role can open EntryLayer through ENTRYLAYER_USER.
A small admin/operator role can administer setup through ENTRYLAYER_ADMIN.
Caller rights grants are applied to the pilot database, schema, and table or view.
The source has a stable primary key or equivalent unique row identity.
The team has agreed whether the pilot uses synthetic, redacted, or production-safe data.

Two-week pilot timeline

Day	Activity	Success signal
1	Confirm source object, roles, and pilot workflow.	EntryLayer can see the pilot source metadata.
2	Create the project and generate the starting form.	Builder can review fields and publish a first version.
3-4	Configure review states, field groups, validation, and permissions.	Operator and reviewer experiences are distinct and understandable.
5	Run the first end-to-end review with 5-10 records.	Records can move from draft or not started to approved or rejected.
6-8	Tune labels, required fields, queue views, and reviewer notes.	Users can work without spreadsheet fallback.
9	Validate audit history and access behavior.	Stakeholders can answer who changed what and when.
10	Review extraction and pilot decision.	Approved records can be pulled into a customer-controlled Snowflake workflow.

Sample exception-review dataset

Use this synthetic table when a real customer source is not ready yet.

CREATE DATABASE IF NOT EXISTS ENTRYLAYER_PILOT;
CREATE SCHEMA IF NOT EXISTS ENTRYLAYER_PILOT.DEMO;

CREATE OR REPLACE TABLE ENTRYLAYER_PILOT.DEMO.ORDER_EXCEPTIONS (
  EXCEPTION_ID STRING,
  ORDER_ID STRING,
  CUSTOMER_SEGMENT STRING,
  EXCEPTION_TYPE STRING,
  SEVERITY STRING,
  DETECTED_AT TIMESTAMP_NTZ,
  SOURCE_SYSTEM STRING,
  ORDER_AMOUNT NUMBER(12, 2),
  PROPOSED_CORRECTION STRING,
  REVIEW_OWNER STRING,
  REVIEW_NOTE STRING,
  PRIMARY KEY (EXCEPTION_ID)
);

INSERT INTO ENTRYLAYER_PILOT.DEMO.ORDER_EXCEPTIONS
  (EXCEPTION_ID, ORDER_ID, CUSTOMER_SEGMENT, EXCEPTION_TYPE, SEVERITY, DETECTED_AT, SOURCE_SYSTEM, ORDER_AMOUNT, PROPOSED_CORRECTION, REVIEW_OWNER, REVIEW_NOTE)
VALUES
  ('EX-1001', 'ORD-24001', 'Enterprise', 'Missing approval code', 'High', '2026-06-01 09:15:00', 'ERP', 12450.00, 'Add approval code from contract amendment.', 'Operations', NULL),
  ('EX-1002', 'ORD-24018', 'Mid-market', 'Amount mismatch', 'Medium', '2026-06-01 10:40:00', 'Billing', 875.25, 'Confirm invoice amount before posting.', 'Finance', NULL),
  ('EX-1003', 'ORD-24027', 'Enterprise', 'Unknown product mapping', 'High', '2026-06-02 08:05:00', 'CRM', 4610.90, 'Map SKU to active product catalog.', 'Data Steward', NULL),
  ('EX-1004', 'ORD-24031', 'SMB', 'Missing region', 'Low', '2026-06-02 11:30:00', 'Web', 240.00, 'Assign region from customer account.', 'Operations', NULL),
  ('EX-1005', 'ORD-24044', 'Enterprise', 'Duplicate order candidate', 'High', '2026-06-03 14:20:00', 'ERP', 19100.00, 'Review against ORD-24043 before approval.', 'Finance', NULL);

Then grant caller rights to the installed app name used in the customer account:

GRANT CALLER USAGE ON DATABASE ENTRYLAYER_PILOT TO APPLICATION ENTRYLAYER;
GRANT INHERITED CALLER USAGE ON ALL SCHEMAS IN DATABASE ENTRYLAYER_PILOT TO APPLICATION ENTRYLAYER;
GRANT INHERITED CALLER REFERENCES, SELECT ON ALL TABLES IN DATABASE ENTRYLAYER_PILOT TO APPLICATION ENTRYLAYER;

Replace ENTRYLAYER with the installed application name if it differs.

Success criteria

Use these criteria to decide whether the pilot is successful:

Criterion	Evidence
Builder can create and publish the project	Project exists with a reviewed form and workflow state model.
Operators can work records	Users can open rows, edit permitted fields, add notes, and submit.
Reviewers can approve or reject	Workflow actions are visible only when valid for the user and state.
History is inspectable	Field changes, workflow transitions, and access activity are visible.
Source access is understandable	Snowflake grants and project permissions produce explainable access behavior.
Extraction path is credible	Approved records can be pulled into customer-owned Snowflake workflows.

Handoff checklist

At the end of the pilot, capture:

Source object and source owner.
Builder, operator, reviewer, and admin roles used.
Final workflow states and transition rules.
Fields that were edited, hidden, required, or read-only.
Any permissions that confused users.
Any reviewer notes or audit reports the team expects.
Extraction target and downstream owner.
Decision: expand, revise, pause, or stop.