STEP 01
Triage every new message
An always-on agent classifies inbound mail the moment it lands — replied-to, fyi, scheduling, pitch, follow-up.
Now in early access
Your Gmail, triaged.
Your replies, drafted.
Your send button, still yours.
Pendraft minds your inbox so you can stop performing the daily email-conveyor-belt review. Cold pitches quarantine, scheduling proposes holds, and the rest surfaces as held drafts — ranked by CRM stage, prior-thread weight, and the role rules you set.
Held drafts · no auto-sendFlat per-seat · no usage caps
Stop the morning triage. Wake up to drafts, not unreads.
How it works
Four steps, all of them agentic. None of them irreversible.
Pendraft runs continuously against your inbox. Every action it proposes stops at a hold — a draft you open, a calendar slot you accept, a digest you skim.
STEP 02
Quarantine the cold pitches
Vendor outreach and one-off cold pitches collapse into a single daily digest. They never reach your reply queue.
STEP 03
Parse scheduling, propose holds
When a thread asks for time, Pendraft reads the intent, checks Google Calendar, and proposes a hold — never books it.
STEP 04
Hold the rest as drafts
Everything else surfaces as a ready-to-send draft, ranked by CRM stage, prior-thread weight, and your role rules.
What Pendraft never does
The line that other agents won't draw.
Privacy and unauthorized-send concerns are what's actually blocking adoption of fully-autonomous inbox agents. A held draft is the form factor that crosses it.
Never sends on your behalf
Your send button stays yours. Every outbound leaves only after you press it.
Never books a meeting itself
Calendar holds are proposed, not created. You accept the slot, never the surprise.
Never trains on your inbox
Your threads are not the product. Drafts are generated per request and discarded after you decide.
Never floods you with notifications
One morning digest, one held-drafts inbox. The notification every fully-autonomous agent sends is the one we cut.
Integrations · day one
Plugs into the stack your inbox already lives in.
- Gmail
- Google Calendar
- HubSpot
- Salesforce
- Drag (MCP)
- Other MCP sources
CRM signals flow inward — a draft already knows the deal stage, the shortlist position, or the prior-thread weight. Additional MCP sources can be wired in without a code change.
Built for
Operators whose unread counter is a daily line item.
If your inbox is the bottleneck between your morning and your day, the same held-draft posture fits.
- 01
Founders
The 30-minute morning inbox tax stops being a line item before the standup.
- 02
Sales leads
The draft your AE reads tomorrow already reflects the deal stage in HubSpot or Salesforce.
- 03
Recruiters
Candidate threads stay grouped by role; outreach drafts hold until you confirm the shortlist.
- 04
Agency operators
Shared-inbox volume stops being the bottleneck. Each client inbox gets the same held-draft treatment.
- 05
Executive chiefs of staff
You see only the threads a principal should read, ranked by prior-thread weight — not by sender count.
Pricing
Between the lower tier and Superhuman Business. Flat per-seat.
A single plan, priced per seat, no usage caps, no per-thread overage, no enterprise-only gate on the integrations on this page. The plan scales as your inbox grows — not as your unread does.
The Pendraft plan
Flat per-seat
Anchored between the lower third-party tier and Superhuman Business. Final pricing shipped with the GA announcement — early access pricing is locked in.
Lock in early-access pricing
Skip the queue: pendraft-7@polsia.app
Frequently asked
The questions adoption hinges on.
Anything else: pendraft-7@polsia.app. A human answers, not a queue.
Early access
Stop the morning triage.
Start tomorrow on held drafts.
Email pendraft-7@polsia.app with a one-line note: your inbox size, the tools you already have wired, and the role you're trying to recover time for.
Email pendraft-7@polsia.app
A human replies. Usually within a business day.