Business data, governed end to end
TBOC2 connects customer-owned records to a secure operating workspace, validates every publication, preserves source authority, and turns authorized questions into evidence-backed answers.
Which active contracts have timecard exceptions this week?
Illustrative workspace state
A trustworthy operating model
TBOC2 does not blur ownership. It keeps the authority of each source explicit while making the information useful together.
From source to decision
Use scoped credentials for approved sources.
Check schemas, types, identities, dates, and references.
Create a new immutable data generation atomically.
Expose the approved generation through a private, read-only query layer.
Power authorized workspaces, reports, exports, and Ask TBOC.
The GA 2.0 business workspace
The current Home experience is a role-aware card dashboard. Each card explains its destination and opens the corresponding workspace directly.
Choose a section to get started.
Month-to-date financial and labor metrics, rolling trends, and PO utilization.
Contacts, records, timecards, allocations, charge usage, and labor insights.
Managed customer records and purchase-order lifecycle information.
Contract, monthly labor, performance, attention, and planning views.
Business records, contract labor records, and direct Source Sheets access.
Evidence-backed answers through authorized, read-only tools.
Hours, labor cost, billed revenue, and margin include three-month visual history.
Compare hours used with hours available through a governed utilization heat map.
Operate employee, customer, purchase-order, timecard, and contract data.
Manage connectors, licensing, local AI, updates, recovery, and audit history.
Ask TBOC
A local language model helps interpret the question and choose from approved, read-only tools. TBOC2—not the model—enforces identity, role, data scope, and evidence.
Security is part of the data model
Authority is explicit. An administrator manages the platform; that alone does not grant access to confidential HR data.
Invited users authenticate through Google. In Google mode, TBOC2 stores no user passwords.
Observer, operator, HR, and administrator permissions remain distinct and server-enforced.
Sensitive HR fields stay protected across views, search, sorting, exports, evidence, and Ask TBOC.
Interactive sign-in and unattended source collection use different Google credentials and scopes.
Database, query, and model services can remain inside the customer-controlled environment.
Immutable generations make data publication observable, recoverable, and easier to audit.
Available now
Purpose-built solutions
When the mission does not fit an off-the-shelf workflow, TBOC2 can be configured or custom-built around your operating model, data authority, roles, and reporting needs.
Discuss your use caseCommon questions
It is designed for customer-controlled deployment. Core data, query, and local model services can operate inside the customer environment.
The customer does. TBOC2 preserves explicit source authority, uses scoped access, and does not require a third-party hosted data platform.
Current capabilities include Google Sheets and Drive-connected workflows, PostgreSQL, qualified Excel ingestion, CSV snapshots, and CSV patterns configured for live customer-system data.
The current implementation uses a local model with cloud inference disabled. The model selects approved tools; it does not receive credentials, arbitrary database access, or authority to write.
No. Administrative authority and HR data authority are separate. Access to confidential fields requires the explicit HR role.
The failed generation is not published. TBOC2 preserves the previous usable generation so operational access does not depend on accepting partial data.
Request access
Tell us what your teams need to see, protect, and act on. We’ll map the sources, authority, roles, and operating workflow.