SUPERMEGA.dev
AI worker user guide

Use the worker like a real teammate.

Start with one approved source pack, get a first proof, then decide whether the worker should become a maintained workflow. The same operating rules work on desktop, tablet, and mobile.

Choose a workerBack to AI agents
Quick start

Use any worker in four steps.

1Pick the jobUse the matcher or setup kits to choose the worker that matches your source and first proof.
2Send one source packShare a small approved sample: screenshot, export, folder link, email thread, sheet, PDF, or chat sample.
3Review first proofCheck the output, source trace, missing fields, and approval boundary before connecting more tools.
4Accept or refineApprove, request changes, or stop. Production runs and recurring support begin only after owner acceptance.
Role-aware onboarding

Choose the mode that matches the user.

Owner, operator, and technical admin users need different proof and approval steps. The public site saves only the selected role in this browser and passes it into setup forms as a routing hint.

Owner modeApprove the goal, first proof, price, payment route, and first production run before any recurring claim.
Operator modeCollect source samples, check missing fields, report edge cases, and confirm whether the proof matches daily work.
Technical admin modeConfirm connector scope, permissions, logs, vaulting, and rollback before account access or browser/mobile actions.
Daily use

Mobile, tablet, and desktop.

Device-aware onboarding detects the current screen size and routes first steps toward phone, tablet, or desktop work without storing private source text.

Phone modeReview first proofs, approve quick items, capture photos or screenshots, and check owner status.
Tablet modeUse review queues, floor checks, approval lists, checklist work, and manager handoff during live operations.
Desktop modeUse source review, setup forms, control console, ledgers, proof packets, and larger dashboards.
Adaptive setup plan

The next step changes with the user.

The public flow combines selected worker, role mode, and device mode into a first-proof plan before the request is sent. It passes only routing hints into forms: worker ID, plan summary, next step, and page path.

Worker signalSelected setup kit or remembered worker decides which first-proof checklist should open.
Role signalOwner, work reviewer, or technical admin mode changes approval, source, and connector tasks.
Device signalPhone, tablet, and desktop users get different next actions without tracking private business text.
Source pack checklist

Send the smallest approved source pack.

Each worker shows the minimum inputs and sample sources needed for the first proof. The checklist is generated from the worker template and passes only source-pack requirements into the setup request.

Minimum inputsStart with the smallest source set that can prove the promised output.
No secrets firstDo not send credentials, payment secrets, or live system access for the first proof.
Proof before scaleExpand to connectors, schedules, and production workflows only after the first output is accepted.
Connectors

Connector setup rules.

Export firstStart with files, screenshots, or exports before granting account access. Prove value before credentials.
API before browserUse official APIs, webhooks, and scheduled jobs before computer-use or mobile-app action workers.
Approval ledgerEvery send, write, payment, browser action, mobile action, or live record edit needs owner approval and evidence.

Computer-use and mobile workers are available only as gated workcells after reliability, consent, vaulting, legal review, and audit logs are proven.

Template guide

What to send for each worker.

live

DeskPOS Quickstart

Private POS setup with sales, bookings, payments, receipts, stock, customers, and daily close actions.

  • First proof: Working checkout, booking flow, MMQR receipt, and daily close insight on their starting catalog.
  • Sample sources: service menu, staff list, payment wallet name
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

Viber / WhatsApp Business Ledger

Turn messy chat orders into customers, open balances, invoices, delivery status, and follow-up tasks.

  • First proof: Clean table of recent orders, who owes money, and which customers need follow-up today.
  • Sample sources: ten order screenshots, product list, delivery rules
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

Inbox & Calendar Operator

Read-only assistant that turns email and calendar context into drafts, prep notes, reminders, and approvals.

  • First proof: Morning action brief with drafted replies, meeting prep, and follow-up tasks waiting for approval.
  • Sample sources: Gmail labels, calendar categories, reply examples
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

Daily Intelligence Brief Agent

Start-of-day operating brief that watches chosen sources, flags changes, and turns signals into decisions.

  • First proof: One-page morning brief with what changed, why it matters, and exact follow-up actions.
  • Sample sources: watchlist URLs, company names, Gmail labels
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

Factory Ops Ledger

Plant ledger that turns production, quality, maintenance, receiving, and CAPA logs into one risk queue.

  • First proof: Dashboard showing production, quality claims, open issues, and the top risks to review today.
  • Sample sources: daily production sheet, quality claim log, maintenance notes
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

Data Cleanup & Reporting Agent

Repeatable agent that cleans files, validates columns, explains exceptions, and outputs a trusted report.

  • First proof: One messy file cleaned into the target table with exceptions highlighted and a short summary report.
  • Sample sources: messy spreadsheet, target report, validation rules
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

Document / PDF Intake Ledger

Turn repeated PDFs, scans, and document folders into one structured ledger with missing fields and source trace.

  • First proof: Five sample documents extracted into a clean table with confidence notes, missing fields, and source links.
  • Sample sources: five PDFs or scans, target field list, example completed report
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

CRM Follow-up & Pipeline Assistant

Combine leads, replies, quotes, and next steps into one follow-up queue with approval-only outreach drafts.

  • First proof: A ranked pipeline showing hot leads, stuck deals, missing next actions, and drafted follow-ups for approval.
  • Sample sources: lead spreadsheet, recent replies, offer list
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
build-ready

Proposal & SOW Builder

Turn intake notes, scope calls, price bands, and past examples into a structured proposal and SOW draft.

  • First proof: One client-ready draft with scope, assumptions, milestones, exclusions, and approval checklist.
  • Sample sources: scope notes, past proposal, service menu
  • Approval: owner approval before send/write/payment actions
Start setupSetup kit
Start safely

Choose one worker and one source pack.

The first useful output is the proof. The platform scales only after the first proof is accepted.

Choose a setup kit