Software feature map
Browse records, dependencies, boundaries and operating procedures.
Capability delivery and evidence ledger
Delivery model and evidence state are separate axes. Source verified does not mean runtime verified. No runtime verification is claimed unless that exact badge appears.
Leads & pipeline
- Records you work with
- Leads, statuses, substatuses, representatives, follow-up notes
- Before this can work
- Configured source/status lists and role-based lead access.
Delivery noteLead records and follow-up controls are part of the shared foundation; assignment and permissions are configured per installation.
How to do it
Configuration boundaryStatuses and communication permissions follow the installation’s configuration.
Contacts & relationship history
- Records you work with
- LeadContacts, LeadNotes, tags, source and campaign links
- Before this can work
- An existing LeadID and agreed attribution/tag conventions.
Delivery noteContact attribution is standard; call ingestion and analysis depend on configured external services.
How to do it
Configuration boundaryCampaign assignment can originate in acquisition/import integrations; the basic lead form does not expose every relationship.
Commerce accounts
- Records you work with
- Accounts, account types, lead/account association
- Before this can work
- A lead and enabled account type; customer identity checked first.
Delivery noteLead-to-account setup and first-sale records are standard; account ownership and commerce settings are installation configuration.
How to do it
Configuration boundaryPayment profiles are initialized by gateway operations, not entered as account-creation fields.
Products & catalog
- Records you work with
- Products, product types, categories, images and product-category links
- Before this can work
- Product identity, type, primary price and publishing rules.
Delivery noteProduct, category and price records are standard; each installation supplies its own catalog and commercial rules.
How to do it
Configuration boundaryShipping, digital delivery and license sections identify configuration work; they are not universal setup wizards.
Prices & promotions
- Records you work with
- ProductPrices, PriceTypes, Discounts and PromoCodes
- Before this can work
- Agreed price selection, eligibility, schedule and caps.
Delivery notePrices, discounts and quotes use shared records; customer-specific policy such as a minimum-order rule may require configuration or scoped bespoke work.
How to do it
Configuration boundaryAdditional price records do not automatically establish tier-price selection in the stock quote UI.
Quotes & orders
- Records you work with
- Baskets, BasketItems, account and product references
- Before this can work
- Enabled account/products; an open quote for edits.
Delivery noteQuote conversion and BasketID continuity are standard; downstream order exchange is an installation-owned integration.
How to do it
Configuration boundaryConversion finalizes the same BasketID; it does not charge or create a new invoice identity.
Payments & fulfillment
- Records you work with
- Basket payment context, processor/method references and fulfillment result
- Before this can work
- Finalized basket, ready processor/manual method and configured fulfillment.
Delivery noteThe checkout contract is source-verified. Processor credentials, live payment execution and fulfillment runtime evidence are not claimed here.
How to do it
Configuration boundaryPayment and fulfillment are separate states; a retry must target the unresolved operation.
Subscriptions & renewals
- Records you work with
- SubscriptionPlans, ProductRenewals, SubscriptionPayments and operation history
- Before this can work
- Matching enabled product schedule, account and gateway configuration.
Delivery notePlans and local lifecycle controls are standard; provider billing behavior requires configured integration and separate verification.
How to do it
Configuration boundarySuspend Management is local only; Pause Billing cancels remotely and Resume creates a successor.
Inventory & suppliers
- Records you work with
- Inventories, Vendors and ProductVendors
- Before this can work
- Inventory-tracked products and an agreed stock source of truth.
Delivery noteInventory and vendor associations are standard records; procurement and fulfillment handoffs are separate integrations.
How to do it
Configuration boundarySupplier association is not purchase-order dispatch; warehouse/carrier workflows are configured integrations.
Calls & AI-assisted work
- Records you work with
- Calls, transcriptions, extracted analysis and lead activity
- Before this can work
- Available recordings/transcripts and configured analysis services.
Delivery noteCall-analysis seams are source-verified; provider setup, prompts and customer-specific automation require scoped delivery and runtime validation.
How to do it
Configuration boundaryExtracted commitments must become verified notes, contacts and scheduled work through the appropriate workflow.
Imports & integrations
- Records you work with
- Datasets, mappings, ImportKey/external keys and operation results
- Before this can work
- Authoritative data ownership, test environment and explicit contracts.
Delivery notePreview/import and shared data contracts are source-verified; production data movement and external ownership remain installation responsibilities.
How to do it
Configuration boundaryReview import defaults and saved mappings for the current batch. External handoffs need their own acceptance checks.
Administration & managed changes
- Records you work with
- Users, roles, representative relationships and release evidence
- Before this can work
- Authorized owner, clear change scope and testable examples.
Delivery noteThe documented change workflow is source-grounded. A managed-service or bespoke change exists only when separately scoped and accepted.
How to do it
Configuration boundaryThis documents the operating process, not a fictional universal rule editor.