Regie.ai

Three integration classes, by design. The documented connectors are HubSpot, Salesforce and Monday CRM, which RegieGO syncs in with a backfill rather than replacing; Gmail and Outlook for sending from the seller's own mailbox; and LinkedIn.

Enrichment, dialing and CRM are built into the workspace rather than integrated, since the product ships its own CRM so a buyer can start with nothing, and the vendor sells the absence of integration work as the feature: setup takes about ten minutes and there is no connector to troubleshoot, and it goes on your own card without any CRM to connect. That is three integration classes, CRM, mailbox and social, with no marketplace, no connector catalog and no route for a customer to add one. Custom CRM sync is listed as an Enterprise entitlement, which suggests more is available on quote but does not document what.

Sourceregie.ai/pricing and regie.ai/use-cases/outboundread 2026-09-02

A documented tool chain running end to end from one instruction. The vendor's own worked example shows a seller asking in plain language to be put in front of fifty heads of RevOps at Series B fintechs, and the agent executing six named steps in sequence: read the website across fourteen pages, update company context covering pitch, voice and wins, search people returning 240 matches, enrich contacts for mobile and email, verify emails leaving 47 valid, and bulk-create fifty email drafts. Each step's result feeds the next and the run reports its own duration and token usage.

Beyond the single run, agents are schedulable and recur unattended: a daily outreach list is documented running every day at 7:00am Pacific, finding new prospects, drafting the day's emails and updating the CRM, with a run history showing completed executions and the count added each day. The vendor's framing is choose an agent, edit it in chat, and schedule it, so the machine keeps running while you sleep. That is multi-step execution with state passing between steps and unattended recurrence.

Sourceregie.ai/use-cases/outbound and regie.airead 2026-09-02

Grounding is built from the customer's own material and every claim is traceable. The agent crawls the seller's website, reading the pages that matter, and builds a company context covering what is sold, who it is for, the pitch, the voice and the wins, which it then applies to everything after; the vendor describes this as turning your homepage into a target list, and it proposes titles and company sizes from what it read.

Per prospect it researches independently and shows its work: the worked example surfaces three open RevOps roles from a careers page, a Series B round from a press release, and a relevant customer win from the seller's own case study, each rendered as a source the seller can preview behind the claim that uses it. A voice profile is confirmed by the user rather than inferred silently. The vendor states plainly that every claim carries a source and that messages are grounded in research you can verify, and follow-ups adapt to what is true about the prospect that week.

Sourceregie.ai/use-cases/outbound and regie.airead 2026-09-02

A real sign-off gate, stated as the design rather than as reassurance. The agent drafts and then queues, in the vendor's words queuing the drafts for your sign-off and tees up follow-up tasks, and the FAQ puts it directly: you read every draft before it goes out, so the last word is yours. Two further protections sit around the send rather than after it. Every address is verified before anything goes out, with the worked example showing fifty drafts reduced to 47 verified recipients, so unverified contacts are not attempted.

And anyone on the do-not-contact list is blocked rather than flagged, which is the vendor's own distinction and is a meaningful one, since a flag depends on a person noticing it. Sending is throttled and unsubscribes are handled automatically, and messages go from the seller's own connected Gmail or Outlook rather than a vendor domain, so the identity carrying the risk is the same one holding the controls. The gate is per draft rather than configurable, with no approval routing, no role-based review and no policy engine documented, which fits a product built for a single seat.

Sourceregie.ai/use-cases/outbound and regie.ai/pricingread 2026-09-02

An attestation with no type and no customer-facing control named. The site footer carries a SOC 2 badge, monitored by Drata, with the report type nowhere stated, and a GDPR badge alongside it. A SOC 2 claim without a type is unverified rather than assumed to be Type II. No SSO, no SAML, no role-based access control, no audit log, no encryption detail, no penetration test statement, no sub-processor list and no trust portal is published.

SOC 2 and enterprise security are listed as an Enterprise-tier entitlement on the pricing page, alongside team workspaces and custom CRM sync, which is a point about packaging rather than posture. That says the security posture is not what the free-tier and $49 buyers are getting, which is what someone comparing tiers needs to know.

Sourceregie.ai/pricing and regie.airead 2026-09-02

A visible run record without an audit surface. A user sees a recent-runs list for each scheduled agent showing the date, the time, the outcome and the count added, with completed status against each; and, inside the chat, the agent's own working shown step by step as it goes, naming each tool it called and what came back, fourteen pages read, 240 matches found, 47 emails verified, fifty drafts created, with the run's elapsed time and token consumption displayed. Per message, source provenance is exposed and previewable behind every claim, so a user can reconstruct why the draft says what it says.

That is genuine visibility into what the agent did and on what basis. None of it is auditability. There is no audit log, no retention statement, no record distinguishing what the agent generated from what the seller edited before sending, and no attribution of a sent message to the person who approved it, which matters because the message leaves from that person's own mailbox. The run trace lives in the chat thread rather than in a queryable log.

Sourceregie.ai/use-cases/outbound and regie.airead 2026-09-02

Configuration and records persist; agent memory is not documented. What survives across runs is the company context the agent builds from crawling the seller's website (pitch, voice and wins), the voice profile the seller confirms, the ICP and targeting criteria, and prospects, drafts and settings, which the pricing page says are kept when credits run out.

Those are configuration and business records rather than agent memory. No cross session agent memory, facts about the user store or retention and forgetting control is named, and follow ups are described as adapting to what is true about the prospect that week, which is re-reading rather than remembering.

Sourceregie.ai/use-cases/outbound and regie.ai/pricingread 2026-10-01

No deployment or residency control appears in the published entitlement list. The pricing page sets out the entitlements for each tier, and they contain no region selection, no EU hosting option, no single-tenant or private deployment and no residency commitment; the Enterprise tier adds volume credits, team workspaces and shared agents, custom CRM sync, advanced analytics, a dedicated account manager and SOC 2 and enterprise security, and stops there.

Nothing on the homepage, the use-case pages or the footer legal links states a hosting location or jurisdiction either. One architectural fact runs the customer's way, though it is not a deployment option: outbound sends from the seller's own connected Gmail or Outlook rather than vendor infrastructure, so the mail itself never sits in a Regie mailbox. With no hosting location stated, where processing happens is not published.

Sourceregie.ai/pricing and regie.airead 2026-09-02

Prebuilt plays that ship ready to run, without a catalog to browse. The vendor states the prompts and plays come prebuilt from billions of sends analyzed across its history, that a seller is engaging on day one rather than standing anything up, and that the workspace arrives with pre-built plays ready to run alongside connectors already in place. Agents are selectable and adaptable rather than authored: choose an agent, edit it in chat, and schedule it.

Named plays appear in the always-on panel, a post-funding outreach play, a new-exec intro play and a hiring-surge play, each tied to a signal class and each running daily. A public prompt library is published as a marketing resource. Nothing enumerates the set. No agent library, template gallery, marketplace or count is documented, so a buyer can see that prebuilt plays exist and cannot see what they are or choose from them before signing up.

Sourceregie.ai/use-cases/outbound, regie.ai and regie.ai/resources/prompt-libraryread 2026-09-02

A schedule wakes the agent. Work starts either from chat, where a seller describes the outcome and the agent plans and executes, or on a schedule: the outbound use case shows an agent set to run "Every day at 7:00am PT" with a Run now control beside it, finding new prospects daily, drafting emails, updating CRM records and queuing messages for approval.

Signal detection on why-now events such as a funding round, a new VP of Sales or a hiring surge shapes what the daily run does. Channels are email from the seller's own Gmail or Outlook, phone through a built in dialer, and LinkedIn, worked from one queue. The schedule appears in a worked example rather than on a reference page, and no webhook or event trigger is documented.

Sourceregie.ai/use-cases/outbound and regie.ai/pricingread 2026-10-01

No model named and no documented choice. Nothing across the homepage, the use-case pages, the pricing page or the FAQs identifies a provider or offers model selection, routing, bring-your-own-model or bring-your-own-key. Credits are metered against research, drafting, enrichment and dialing, so a buyer sees what model work costs without seeing what performs it.

The product screenshot of the chat composer carries a control labeled GO Max with a dropdown, which sits where a model or effort selector would sit. No page explains what it selects, and it may be an effort mode rather than a model choice. The vendor's own FAQ contrasts the product with ChatGPT and Claude as tools a seller would otherwise wire up themselves, which positions those as alternatives to Regie rather than as models inside it.

Sourceregie.ai/use-cases/outbound and regie.ai/pricingread 2026-09-02

Nothing programmatic, and the vendor sells that as the point. No API reference, developer site, SDK, MCP server, webhook documentation or partner program appears anywhere on the property: the navigation runs to Products, Use Cases, Who It's For and Pricing, and the footer carries product anchors, company links, resources and legal pages with no developer route among them.

The positioning is explicitly against needing one, that setup takes about ten minutes with no connector to troubleshoot, and that the product goes on your own card without anyone else signing off or any CRM to connect. That is a coherent design for a single-seat self-serve workspace, and it means the platform cannot be called from outside. Custom CRM sync is an Enterprise entitlement, which may imply an integration surface available on quote, though none is documented.

Sourceregie.ai/pricing, regie.ai and regie.ai/use-cases/outboundread 2026-09-02

The output can be checked before it goes; the agent cannot. Two pre-send checks are documented and both produce a readable result. Email verification runs on every address before anything sends, with the worked example showing fifty drafts reduced to 47 verified recipients, which is a pass rate on the artifacts the agent produced.

And source provenance is inspectable per claim: every assertion in a draft carries the source behind it and the seller can preview it, so the factual basis of the output can be tested rather than trusted. Alongside those, scheduled runs report counts and outcomes so performance is visible over time. None of it evaluates the agent.

There is no sandbox or dry run, no scored evaluation of generated copy, no judge, no comparison of one agent configuration against another, and no regression check when the voice profile or company context changes.

Sourceregie.ai/use-cases/outboundread 2026-09-02

LinkedIn steps that Regie runs itself, inside software it does not control. The product documents LinkedIn in two shapes on the same property. The site's meta description describes agents that source, enrich, dial and email from your own inbox plus LinkedIn tasks, which reads as work queued for a person. The channel orchestration panel on the homepage shows the other shape: a three-channel outreach play against a named prospect with an execution timeline of email on day one, LinkedIn on day two, an email follow-up on day four and a phone call on day six, labeled three channels, one sequence, run by Regie.

LinkedIn publishes no sanctioned interface for outreach at this scale, so an agent-run LinkedIn step is action inside software the vendor does not control. This is single-site automation with no general browser or computer control, and the mechanism is not stated; the panel is a product illustration and does not say whether the step drives a session, calls an integration or files a task. LinkedIn also appears as a listed connector alongside HubSpot, Gmail, dialer and enrichment.

Sourceregie.ai channel orchestration panel and regie.ai/use-cases/outboundread 2026-09-02