Approval Queue
LiveEvery automated message, email, and file action lands here as a draft. One person approves each send: Tim. Full audit trail, write-ahead intents, multi-user accounts.
Obelisk drafts the routine work behind every client launch. Nothing sends without Tim's sign-off.
Most onboarding delay is not missing information. It is information waiting to be relayed. Obelisk closes that gap: when the answer already exists in our systems, the draft is ready before anyone has to ask. Less context switching. Less burnout. Launches that move at the speed of what the team already knows.
Seven modules, one rule: automation reads and drafts, a human decides. Live status and metrics are inside the control panel.
Every automated message, email, and file action lands here as a draft. One person approves each send: Tim. Full audit trail, write-ahead intents, multi-user accounts.
Instant answers from Guru, team Slack, case notes, and the inbox. A privacy filter scrubs credentials and personal content at ingestion, so the answer is safe before it is stored.
Onboarding KPIs and the client forecast, refreshed hourly. Aggregates only, never client rows.
Email attachments filed to the right Drive folder, client folders created in the team trees. Every action approved first.
Task completions parsed into a clean event log; webhook capture is in place for real-time updates.
The panel ranks what matters most each morning: overdue go-lives first, weighted by revenue and urgency.
Will generate US onboarding and tax documents from templates and route them for signature once live.
Automation does the reading, matching, and drafting. One person decides what actually goes out: Tim.
Source events are read and matched to the right client, company, and project.
Each event is appended to a plain-text log on the server. Nothing is silent.
Slack messages, emails, and file actions are written as drafts into the approval queue. Never sent directly.
Pending drafts wait in the control panel with their full text and target visible. Tim approves or rejects each one individually.
There is no bulk-approve and no auto-send. A rejected draft is logged and goes nowhere.
Only after approval does the message go out, from Tim's own account, exactly as reviewed.
Every send is traceable back to the draft, the approval, and the source event.
Sensitive client data (EINs, bank details) is processed only inside the company Google Workspace account. It is never stored on this server.
The event log records task names, timestamps, and company references so progress is auditable. Client documents and credentials are not written to it.
The codebase has been through two adversarial security audit passes. Credentials are scrubbed at ingestion, every panel route is auth-gated, and the privacy filter fails closed.