Loading OneFoundry
Loading OneFoundry
Teammate gallery
Each teammate has a role, a visible queue, approved tools, saved work, and approval boundaries. Use a proven role when the job is common. Create a custom teammate when the work is specific to your company.

Work you can inspect
Visible queue
Waiting on approval
Active automation
Next run Thu 9:00
Proactive monitor
Checked 18 minutes ago
Dashboard preview
Needs review
Finished work examples
Every role should create saved work before scope expands. These examples show the output and the boundary that stays in place.
Fundraising
Fit score, deadline, eligibility notes, and source URLs.
No submission, spend, or funder outreach before approval.
Outbound
Account rationale, contact notes, source confidence, and draft copy.
No external sends or CRM writes before approval.
GitHub Portfolio
Failing checks, stale PRs, open risks, and linked GitHub evidence.
No branch, PR, merge, or secret access before approval.
Finance Watch
Vendor deltas, invoice flags, budget impact, and ledger references.
Read-only analysis; no money movement or billing changes.
Research Watch
Comparison matrix, confidence notes, changed-source log, and citations.
No publication or external contact before review.
Customer Care
Ticket links, risky accounts, severity labels, and escalation reasons.
No replies, refunds, or plan changes before approval.
Common roles
These are not generic personas. They map to repeatable work with visible outputs and reviewable evidence. If the role is not here, describe it and OneFoundry will build the setup.
First hire
Finds the right investors or grants, prepares the story, and shows why each next step matters.
A short list, drafts, source notes, and the fundraising decision to make next.
View teammateSales work
Finds accounts, learns the context, drafts messages, and triages replies before anything is sent.
A researched account list, message drafts, reply summaries, and the next sales decision.
View teammateTechnical proof
Turns repositories, commits, and technical work into a clear proof package.
Project briefs, code evidence, contribution summaries, and a crisp portfolio narrative.
View teammateClear answers
Answers business questions with cited sources, clear assumptions, and a recommended next step.
A concise brief, source links, assumptions, and the open decision.
View teammateCompany rhythm
Keeps priorities, follow-ups, blockers, and decisions in one place.
A daily brief, priority queue, and clean handoffs between teammates.
View teammateApproval first
Keeps sensitive work inside policy and makes exceptions visible before action.
Clear boundaries, audit-ready proof, and high-risk exceptions surfaced before execution.
View teammateYour role
Describe the job your team needs done. OneFoundry builds the teammate setup around that role, not around a fixed catalog.
A scoped role, first work product, suggested sources, blocked actions, and approval rules.
View teammateVisible work queue
The teammate queue shows what is waiting, running, scheduled, blocked, or complete so follow-up work does not disappear after the first answer. Every item carries the owner, source context, proof, and decision boundary needed for the next action.
Backlog
Visible in the teammate work queue with owner, source receipts, and next action
Running now
Queue state shows the accepted cost estimate and approved source list
Waiting on user
Decision packet shows draft/send boundary and account context
Blocked
Connector status requires certification or policy review