Should you build your own Sumora?
AI agents that run multi-step business workflows like prospect research and outreach, with browser automation and integrations.
The visible surface, a prompt box that produces a researched, personalized outreach message, is a one-sitting build. What takes real work is everything that keeps an agent from quietly going insane on step seven: persistent memory about your business and each contact, retries, browser sessions that survive logins and captchas, cost ceilings, and a human approval gate before anything is actually sent. For one person automating their own pipeline, you can get to genuinely useful in a weekend because you are allowed to be the approval step and the error handler. The gap widens fast the moment you want it unattended, multi-user, or connected to a real CRM and mailbox over OAuth. The failure mode also matters: a broken personal script wastes your evening, a broken agent emails the wrong prospect from your domain.
ENOriginal research content in English. Original prompt preserved in English.
Build a local, single-user AI outreach agent runner. No accounts, no cloud, no telemetry.
Stack: TypeScript, Node 20, better-sqlite3 for storage, Playwright for browsing, Hono for a tiny local HTTP server, and a plain server-rendered HTML UI with htmx. No React, no Next, no ORM. Secrets in .env: OPENAI_API_KEY, SMTP_URL.
Data model in SQLite:
- business_context: freeform notes about my company, offer, tone, and hard rules (one editable blob)
- targets: company name, domain, contact name, contact email, status
- runs: target_id, state (queued, running, needs_approval, approved, sent, failed), created_at
- steps: run_id, index, tool, input, output, error, tokens, cost_cents
- drafts: run_id, subject, body, revision
Agent loop per target, each step written to the steps table before and after execution so a crashed run is resumable:
1. fetch the target's homepage and one about or pricing page with Playwright, extract readable text
2. summarize what the company does and one specific hook
3. draft a short outreach email using business_context plus the hook
4. run a self-check pass: is the claim supported by the fetched text, is any name or fact invented, is it under 150 words
5. set state to needs_approval and stop
Hard rules to implement, not just mention:
- nothing is ever sent without an explicit approve click in the UI
- per-run and per-day cost ceilings from .env, abort the loop when exceeded
- exponential backoff with max 3 attempts on fetch and model calls, then mark the step failed and leave the run resumable
- a resume command that picks up any run stuck in running and replays from the first incomplete step
- dry-run mode is the default; sending requires SMTP_URL to be set and a --live flag
UI at localhost:8787: paste or import targets as CSV, edit business_context, list runs with their step timeline, view and edit a draft, approve or reject, see spend to date.
Out of scope: CRM integrations, OAuth, multi-user, LinkedIn or any logged-in site automation, scheduling, deliverability warmup, analytics.
Include a README with setup, an .env.example, a seed CSV of three fake targets, and one integration test that runs the full loop against a local fixture HTML page with the model call stubbed.The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
A local agent loop that takes a target company or list, researches it with search plus a headless browser, drafts a personalized outreach message against your stored business context, and queues it for your approval before sending.
What you will need
- An LLM API key
- Playwright and a machine willing to run a real browser
- A search API or scraping tolerance
- SMTP credentials or a mail API if you want it to actually send
- Patience for step-level debugging
Because the demo is the easy 20 percent and the remaining 80 percent is failure handling nobody enjoys writing. A business paying for this is buying the assumption that the agent will not send the wrong message to the wrong contact at 2am, and that when something does break, someone else's on-call rotation deals with it. A solo operator who is happy to review every draft can absolutely self-host their version and get most of the leverage. A team of ten with a shared pipeline and a reputation to protect generally decides that the subscription is cheaper than owning an agent orchestration layer.
xUnattended reliability: retries, resumable runs, and recovery when a step fails halfway through
xMaintained integrations and OAuth to CRMs, mailboxes, and calendars, plus keeping them working when those APIs shift
xSandboxed execution and guardrails so a confused agent cannot take a real action against a real person
xCost control and model routing, so one runaway loop does not become a surprise bill
xDeliverability and sending reputation work, which is its own unglamorous specialty
Nothing worth pointing at. That’s why the prompt exists.
How much does Sumora cost?
- Monthly billing
- $79.99/mo$79.99/mo
- Per year
- $960/yr$960/yr
- On a Brazilian card, with 3.5% IOF
- R$418/moR$5,016/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Sumora’s site. Vibe Radar does not handle payments.
Is it cheaper to build or buy Sumora?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (a weekend). Does not price what you give up (support, integrations, security).
Can I rebuild Sumora?
Kinda. The core of Sumora is buildable in a weekend with the prompt on this page, but there are real gaps: Unattended reliability: retries, resumable runs, and recovery when a step fails halfway through, Maintained integrations and OAuth to CRMs, mailboxes, and calendars, plus keeping them working when those APIs shift. Read the honest list above before committing.
How much does Sumora cost?
Sumora costs about $79.99/mo (Starter, checked 08/18/2026), which is $960 per year.
What do I lose by replacing Sumora?
Honestly: Unattended reliability: retries, resumable runs, and recovery when a step fails halfway through; Maintained integrations and OAuth to CRMs, mailboxes, and calendars, plus keeping them working when those APIs shift; Sandboxed execution and guardrails so a confused agent cannot take a real action against a real person; Cost control and model routing, so one runaway loop does not become a surprise bill; Deliverability and sending reputation work, which is its own unglamorous specialty. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Sumora?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.