Origami
Agentic customer-discovery and outbound platform: scrape a company site, infer an ideal-customer profile, and run outreach agents toward early customers.
What It Is
Origami positions itself as a customer-finding workflow: provide a domain, let the product scrape the site, build an ideal-customer profile, and start outbound outreach through agents. The captured site copy also points to "Send" as a multi-channel outreach product included in paid plans. Source: X/@origamichat, 2026-06-25; Source: origami.chat fetched from bookmark enrichment, 2026-06-25
The 2026-07-03 artifact review confirmed the GTM workflow is broader than first-customer search. The video shows an inbox/replies surface, sent-count progress, a warm-intro reply from a recommended prospect, and an agent recommendation to re-engage 5,497 free users with a draft campaign. That makes Origami a lifecycle/outbound automation reference: acquisition, enrichment, replies, and reactivation sit in one agent-facing workspace. Source: local X video artifact review, 2026-07-03
Why It Matters
The important signal is not the exact product claim. It is the product shape: "agents as a go-to-market desk" where the interface is a business goal, not a chat box. That maps to Services-as-Software and Agent Product Surface: agent products increasingly package a workflow outcome, a source-of-truth profile, and continuous action.
Finn Mallery's conference-led GTM thread adds the concrete event-intent use case. The thread says to post about a conference roughly four weeks before, find people who posted about the event, then sequence warm outreach. The self-reply points directly back to Origami as the way to find and sequence those conference posters. That is the narrow product wedge: real-time social/web signal -> lead table -> outbound sequence. Source: X/@fin465 thread and reply, 2026-05-23
Source Snapshot
Public source authority is the hosted product and API docs, not a package registry. The site now describes live web search across 50+ sources, contact waterfall verification, social/email sequencing, and pricing tiers with Origami 1.2 Lite/Max model labels. The API docs expose Data API v1 for table enrichment and Agent API v2 beta for running an agent from code: send a plain-English brief, receive a table, poll asynchronous runs, and choose origami-lite or origami-max when the plan allows it. Source: Origami site/API docs, 2026-07-03; Source: Origami API docs, 2026-07-03
Routing
Keep this reference-only unless Kevin is comparing outbound/customer-discovery tools. If used for a project, verify deliverability, identity, consent, rate limits, data provenance, and unsubscribe/compliance before any real outreach.
Timeline
- 2026-06-25 | Added from the Origami bookmark as a reference for agentic customer discovery and outbound product shape. Source: X/@origamichat, 2026-06-25; origami.chat, 2026-06-25
- 2026-07-03 | Deep-reviewed the local video artifact and current API docs; recorded Origami as lifecycle GTM automation with Data API v1, Agent API v2 beta, async runs, and plan-gated
origami-lite/origami-maxmodels. Source: local X artifact review; Origami docs, 2026-07-03 - 2026-07-03 | Reviewed Finn Mallery's conference-led GTM thread and self-reply; recorded Origami's warm-lead targeting wedge for people posting about a conference before the event. Source: X/@fin465, 2026-05-23; Source: Origami site/docs, 2026-07-03