Who is involved?
Client, provider, users, memberships, roles, and workspace boundaries.
SYSTEM DESIGN
Orbit connects the request, the scope, the decision, the agreement, and the work that follows — while keeping the boundaries between them explicit.
Someone describes what they need in plain language, asks questions, adds context, and reviews the emerging proposal.
The application gathers requirements, composes scope, applies pricing rules, routes review, and records decisions.
Structured records keep the proposal understandable beyond any single chat, document, or model.
Once approved, the commitment can become a contract, an invoice schedule, and a project handoff without retyping the promise.
THE OBJECT MODEL
These are the core business objects that let a proposal carry its context forward.
Client, provider, users, memberships, roles, and workspace boundaries.
Brief, requirements, sources, options, scope baseline, pricing model, and versions.
Approval steps, comments, flags, review events, meetings, and decision reasons.
Terms, signature status, billing triggers, payment terms, credits, and retainage rules.
Milestones, tasks, time entries, change orders, escalations, and delivery ownership.
Who changed what, which version was approved, and where an exception entered the system.
THE BOUNDARY
The assistant can call a tool, but a tool is not permission. Access scopes, workspace roles, server-side authorization, pricing policies, and review requirements remain application responsibilities.
That is why Orbit can be useful to an AI-first buyer without becoming an AI-only system. The same proposal can be inspected by a client, a salesperson, an architect, finance, and delivery.
GO DEEPER