Paitho
Roadmap

Where we're
going.

Public roadmap. We don't promise dates, but we share what we're prioritizing and why.

In flight
Now
04
Platform
Per-customer Docker hardening
Stricter container resource limits, per-customer rate limits, and a clean teardown path. The bar is "an agency runs twenty clients in one container without one workspace bleeding into another."
Integrations
CRM sync — HubSpot first
Two-way sync of contacts, drafts, and reply state. HubSpot is the first surface; Salesforce is in Next.
Onboarding
Onboarding wizard
Walk a new operator from BYOK paste to first reviewed draft in under fifteen minutes. Replaces the current setup checklist.
Demo infra
Demo subdomain — per-prospect Docker
Spin up an isolated demo workspace per prospect on first contact. Pre-seeded with their ICP, real prospects, and a fresh BYOK key. Two-hour TTL.
Next 1–2 quarters
Next
05
Integrations
Salesforce sync
Once HubSpot is solid. Built on the same sync core. Same two-way contract.
Research loop
Prompt A/B simulator
Fork an angle, run it against a held-out lead set, compare reply-rate predictions before going live. Lets operators tune without burning real prospects.
Vertical Packs
Manufacturing pack
Industrial buyers, distributors, and field-service buyers. Built with operators who actually sell into the segment.
Billing
Self-serve credit purchase
Buy or top-up managed credits in-app, set auto-recharge rules, see real-time burn. Fewer support tickets, faster experiments.
Surfaces
Mobile review app — read-only
Approve or reject drafts from a phone. Read-only by design — editing on mobile is how typos ship. Native iOS first.
Signal-collecting
Later
05
Surfaces
Voice review
Listen to the brief, dictate edits, approve hands-free. For operators who review on commutes or between meetings.
Channels
Multi-channel — LinkedIn DM plus email
Same research, two surfaces. Strict opt-out parity and shared reply state. Only if we can keep the bar.
Replies
Calendar booking embed for replies
When a prospect replies positively, surface a booking link inline rather than a separate tool. Native, not Calendly-style hand-off.
Analytics
Forecasting — pipeline to revenue
Project cohort revenue from current pipeline state using historical close rates. Useful, but only after we have enough customer data to make it honest.
Platform
Public API
Full REST plus webhooks for the pipeline. Held back deliberately until the surface is stable enough to commit to.
What's not on the roadmap

Some things we won't ship.

A roadmap that doesn't say no is just a wish list. Here's what we get asked for and won't build, and why.

×Auto-send (no human review)
Violates Tenet 03. The loop that closes is the loop that teaches — remove the human and the model trains on noise. Won't ship.
×Generic templates and merge-field campaigns
Violates Tenet 02. If a draft could be sent to two companies, it's a failed draft. Templates are how outbound got broken. Won't ship.
×Bulk LinkedIn auto-DM
LinkedIn TOS plus account-burn risk plus mediocre signal. Even the careful version of this is a bad idea for the people we serve. Won't ship.
×Built-in lead database or scraping service
Commodity, conflicts with the bring-your-own-list philosophy, and would put us in a category we deliberately stay out of. Bring the list you trust; we do the research.
Suggest a feature
Have a feature you'd kill for?

We weight requests by how often they show up in operator review sessions. The fastest path is to email or open an issue.

roadmap@paitho.ai github.com/paitho-labs/feedback