DARYL ERP Foundations

# The DARYL contract DARYL is Silver Owl's AI-native ERP: org shell, workflows, audit, and the operating core for mid-market teams. Ledger (finance/MRP) and Kiln (regulated commerce) sit on the same org, auth, and audit backbone. Status is **beta**. Do not present DARYL as a finished NetSuite replacement with full parity. Open https://daryl.silverowl.dev (or the current DARYL login) and start from the shared org shell. The demo org is **Silverline Manufacturing Group**.

# Readiness check 1. Open DARYL and confirm login or dashboard. 2. Sign in with the demo account if prompted. 3. Confirm the shared org shell renders for Silverline Manufacturing Group. 4. Note which modules are actually reachable today: core, Ledger, Kiln. 5. If a module 404s or is waitlisted, record it as beta status, not as a failed company. A waitlist CTA is honest. A fake GL is not.

# Ledger Open Ledger and show GL, invoices, inventory, or manufacturing cost if those surfaces load. The seeded shape is about 48 invoices, 12 purchase orders, and 4 open work orders. Invoice OCR, cash-flow forecast, and "ask your books" are AI features. Demo them only when the panel responds. If the model is offline, walk the seeded invoices and say inference needs the runtime. Do not import a real customer's books into a demo tenant.

# Kiln Open Kiln and show restricted catalog and compliance-gated order flow if available. The seeded shape is about 86 SKUs, 9 compliance holds, and 14 orders pending review. Kiln is a regulated-commerce module, not a general storefront. Do not promise cannabis, alcohol, or other license coverage the demo does not show. If Kiln is unreachable, stay on DARYL core and name the module as part of the operating suite map.

# Ten-minute sequence - Minute 0-2: mid-market operating problem and beta status. - Minute 2-5: org shell and one core workflow. - Minute 5-8: Ledger invoices or work orders. - Minute 8-10: Kiln hold or, if offline, the suite map and a scoped next step. Ask which close, inventory, or compliance step currently lives in spreadsheets.

# Boundaries The demo can prove org navigation, seeded operating data, and the Ledger/Kiln map. It does not prove NetSuite parity, multi-entity tax, shop-floor MES, or a completed data migration. The next step is a scoped evaluation on one process (close, inventory, or compliance), not a rip-and-replace date.