One context across voice, SMS, web, email, and internal threads
OBTUSE WORK / BUSINESS CORE
The whole business. One operating graph.
CRM, field service, projects, time, communications, workspace, people, compliance, invoicing, payments, and accounting are being unified around the records you own—not stitched together as ten disconnected subscriptions.
01 / 04 · RevenueCommunications Time People Portability
Demand becomes a durable customer journey.
Accounts, contacts, source evidence, activities, leads, opportunities, forecasting, sequences, quotes, and client decisions share one identity.
Approved work flows into margin, invoices, and payroll preparation
Named identity and authority are part of every consequential move
JSON, CSV, SQLite, PDF, attachments, schemas, and mapping profiles
01CRM + pipeline+
Account/contact history, opportunities, ownership, stages, forecasting, relationship memory, and explainable priority.
02Prospecting+
Permitted public sources, citations, verification confidence, deduplication, signals, suppression, and consent-aware sequences.
03Commercial documents+
Reusable line items, quotes, client review, invoices, receipts, exact versions, and direct journal provenance.
SYSTEM DESIGN
Broad without becoming a junk drawer.
The breadth comes from a shared architecture. Every module uses the same identity, event, authority, export, evidence, and human-review rules.
One record, many views
Customer, opportunity, job, task, schedule, time, conversation, document, invoice, and journal records stay linked instead of being rebuilt across apps.
Native where it creates ownership
Core data, accounting, policy, workflow, communications context, reporting, and portability belong to Work. Open components extend infrastructure without owning the operation.
Rails remain replaceable
Banks, carriers, tax authorities, payroll deposit, benefits, public email delivery, and legal filing connect through qualified adapters with reconciliation.
Autonomy inherits authority
Agents observe, research, draft, simulate, and recommend. Money movement, commitments, permissions, filings, sensitive disclosure, and external sends keep explicit gates.
FOUNDATION IN THE CURRENT BUILD
Ownership is being implemented at the foundation.
These are concrete paths in the current source—not borrowed screenshots or an integration wish list.
Inspect data ownership- Business identity and commercial defaults
- Exact-cent chart of accounts and immutable balanced journal
- Quotes, invoices, PDFs, client review, receipts, and test checkout
- Scheduling, public requests, reminders, and calendar receipts
- Encrypted inbound communications and an original open gateway contract
- JSON, CSV, SQLite, PDF, and password-encrypted recovery
- Local integration signals and named shared-device authority
Run one operation—not a pile of software.
Explore the consequence-free browser demo, then bring the workflow creating the most drag.