SYSTEM DESIGN

The proposal is the center of a larger commitment.

Orbit connects the request, the scope, the decision, the agreement, and the work that follows — while keeping the boundaries between them explicit.

01 / CLIENT EDGE

Client or AI assistant

Someone describes what they need in plain language, asks questions, adds context, and reviews the emerging proposal.

ChatFormShared linkConnected AI
↓
02 / CONTROL PLANE

Proposal Manager

The application gathers requirements, composes scope, applies pricing rules, routes review, and records decisions.

IntakeScopePriceReview
↓
03 / SYSTEM OF RECORD

API + database

Structured records keep the proposal understandable beyond any single chat, document, or model.

OrganizationsProposalsVersionsAudit events
↓
04 / COMMITMENT GRAPH

Contract → billing → project

Once approved, the commitment can become a contract, an invoice schedule, and a project handoff without retyping the promise.

ContractInvoiceMilestoneTask

THE OBJECT MODEL

Connected records,
not a document pile.

These are the core business objects that let a proposal carry its context forward.

ORGANIZATION

Who is involved?

Client, provider, users, memberships, roles, and workspace boundaries.

PROPOSAL

What is being offered?

Brief, requirements, sources, options, scope baseline, pricing model, and versions.

REVIEW

Who decided?

Approval steps, comments, flags, review events, meetings, and decision reasons.

CONTRACT

What became binding?

Terms, signature status, billing triggers, payment terms, credits, and retainage rules.

PROJECT

What gets delivered?

Milestones, tasks, time entries, change orders, escalations, and delivery ownership.

AUDIT

What can we explain?

Who changed what, which version was approved, and where an exception entered the system.

THE BOUNDARY

Tools can suggest.
Rules decide.

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

See what the architecture makes possible.

Explore the tools →