Your objects, your fields
Model CRM data around your business instead of adapting your process to a fixed template. OSTRATA supports custom objects and rich field types, then lets Pilot operate directly against that schema in Operations and related workflows.
∞
Custom objects
Beyond Contacts, Companies, Deals
1
Source of truth
Schema and ops share one workspace
0
Migration tax
Extend in place as process matures
Model the business, not the vendor
Objects and fields in Setup; Operations executes on what you define.
Schema in OSTRATA gives teams control over data structure. You can start with default objects like Contacts, Companies, and Deals, then extend with custom objects and fields that match how your organization actually sells and supports customers.
This model is practical because Pilot reads it continuously. Teams do not maintain separate assistant mappings or brittle aliases. Requests in Operations resolve against workspace-defined objects and fields, so conversational actions stay accurate as the model evolves.
Custom objects for real processes
Define entities beyond defaults so CRM structure reflects operational reality, not vendor assumptions.
Rich field toolkit
Use lookups, currency, number, select, and attachment fields to capture meaningful context per record.
Pilot reads current schema
Operations actions resolve against your configured objects and fields, including later model changes.
Foundation
Build model around business language
Define objects in your own business language, not vendor defaults.
- Start with baseline CRM objects, then extend
- Model delivery, onboarding, or partner entities directly
- Keep critical context in structured records
Defaults
Field definitions that capture operational truth
Use rich field types to preserve measurable context and relationships.
- Connect records with lookup fields
- Capture finance values with currency and numbers
- Store evidence and files through attachments
Relationships
Pilot alignment without extra integration work
Pilot reads current schema so requests stay accurate after model changes.
- Avoid stale assistant mappings and aliases
- Reflect new objects without prompt rewrites
- Keep create and update flows stable over time
Evolution
Designed for evolution over one-time design
Evolve schema iteratively as workflows change without resetting team habits.
- Add objects when process maturity requires
- Refine fields based on actual usage patterns
- Validate updates quickly in Operations and Views
Governance
Foundation for views, permissions, and integrations
One schema powers reporting, access control, and external automation behavior.
- Anchor Live Views to defined objects and fields
- Drive permission rules from same model
- Keep API behavior predictable across integrations
Questions
Short answers before you request access.
- Can teams add objects beyond Contacts and Deals?
- Yes. OSTRATA supports custom objects in Setup, so teams can model entities specific to their workflow. Defaults provide a baseline, but schema is intentionally flexible so organizations can represent real operations without forcing everything into generic record types.
- Which field types are supported for custom schema?
- Teams can define practical field types such as lookups, currency, number, select lists, and attachments. These options help preserve structure and relationships needed for search, reporting, and updates, rather than relying on loosely formatted text across critical records.
- Does Pilot work with custom schema changes?
- Yes. Pilot resolves actions against the current workspace schema, including custom objects and fields. As teams evolve definitions in Setup, conversational operations remain aligned without creating separate assistant mappings or rebuilding core workflow conventions.
- Why is schema central to other features?
- Live Views, permission profiles, and operational actions all depend on shared object and field definitions. Keeping schema explicit gives these features a consistent foundation, which improves reliability, access control clarity, and reporting alignment across the entire workspace.