Make the decision.
Compare your options, surface assumptions, and see what evidence would change the answer.
Should we hire, outsource, or redesign the work?Compare options
ChiefOS · Business thinking, put to work
Work you
can use.
You bring the context.
ChiefOS brings a useful way forward.
Pressure-test a plan, shape a proposal, or turn a pile of notes into a clear brief. Put a growing library of business skills to work in your AI assistant—or from your inbox.
Sign-in is currently available to the Conversint team.
Library and assistant access available · Email workflows in validationA few places to start
From leadership and sales to operations and finance, find a method that fits the work—not another blank page.
Compare your options, surface assumptions, and see what evidence would change the answer.
Should we hire, outsource, or redesign the work?Compare options
Turn scattered notes into a proposal, an actionable plan, or a brief your team can use.
Turn these meeting notes into a clear plan.Plan work
Review the numbers, question a strategy, or understand what customers are really telling you.
What are we missing in this business case?Review financial assumptions
Use the same growing collection of skills in a conversation with your assistant or a request sent by email.
Connect ChiefOS to an MCP-compatible assistant. Ask it to find and apply the right skills to the context you provide.
Connect your assistant →Email your request and source material for a reply or a finished document. The shared team connection is the default being validated; a personal subscription is an optional override.
See the email workflow →Threaded collaboration, source reading, and document delivery are being checked together from request to reply.
Ask a follow-up, add a constraint, or request a revision in the same thread. Earlier visible messages and source material help carry the work forward.
“Use the same assumptions, but make this a one-page brief.”
Include ChiefOS in To or CC. Track who said what, keep people and company context distinct, and respect the current audience. Sharing a company domain does not make private conversations shared.
“Alex owns the forecast. Jordan needs the final recommendation.”
Attach documents, tables, images, or scanned PDF pages. ChiefOS can work through written and visual context, while identifying unreadable material instead of guessing.
“Compare these proposals and the notes in this scanned page.”
Receive a text reply with Word or PDF attachments when needed. Continue refining it in the thread, with the result shaped for the person who will use it.
“Send the recommendation as a Word document and a PDF.”
Find and apply skills, follow their relationships, and contribute to the library. Contribution actions require the appropriate access.
Search by the work you need to do, from a pricing decision to a customer brief.
search_skillsLoad complete instructions, examples, and quality checks into your conversation.
get_skillExplore related methods and see when combining them would help.
get_skill_graphContributors can draft a missing capability with examples and evaluation cases.
create_skillContributors can propose better instructions or new relationships between skills.
update_skillRecord useful feedback against the exact skill version you used.
record_skill_feedbackNew skills and updates are saved as drafts. Recording feedback does not publish a change.
Connect your assistant →Start with business methods across decisions, strategy, sales, marketing, finance, operations, writing, leadership, people, learning, and customer work. Related skills help a decision flow into a plan or a brief.
Automatic growth · In validationWhen a request reveals a missing skill or relationship, ChiefOS can prepare a proposed addition. The automatic path evaluates it before publication, then makes accepted improvements available to future work.
Published versions keep a reviewable history of changes. Assumptions and missing evidence stay visible in the work itself.
One possible path through the work
Some methods need an earlier result; others are optional ways to strengthen the work. Use the context you already have and follow only the steps that help.
Manage who connects, how requests run, and which updates are used from your ChiefOS workspace.
Create a key for each assistant, choose its permissions and expiry, and revoke it when access should end. Read access and contribution rights stay separate.
Manage access →The shared team connection is being validated as the default for email work. Use a personal Codex subscription as an optional override.
Your execution settings →ChiefOS uses Terra for managed work. New Codex versions are tested before selection, and the current validated Terra runtime remains in place while those checks run.
View update settings →Ask ChiefOS to research approved websites, work inside accounts you authorize, and retrieve files for the work at hand. Terra plans each step with ChiefOS skills while an isolated browser performs the approved action.
Passwords remain outside the model. Sign-in verification and consequential actions pause for you.