For 2–5 B2B products, start with four jobs: a lead source, a verifier, a sending/approval layer, and a follow-up queue. Consolidate the last two first. PortKnot covers sending, approvals, signals, and manual LinkedIn tasks; it does not sell a database or automate LinkedIn.
Outbound tooling gets sold as a stack, but the useful unit is a job. If two tools own the same job, you are paying twice and creating another place for context to die.
The four jobs
| Job | What good looks like | What to avoid |
|---|---|---|
| Find / import leads | You can bring your own CSV, crawl a site, or connect a data source | Per-seat database you never finish using |
| Verify | MX checks and suppression before sending | “Verified” lists with no refresh date |
| Send + approve | Human approval, reply routing, bounce handling | Auto-send with no review |
| Follow up | A queue that stops on reply and tracks manual tasks | Five spreadsheets and a reminder app |
Three realistic stacks
1. Lean founder stack
Data source → verifier → PortKnot → Resend. Import your own list, verify, approve drafts, send through your own Resend account, and manage manual LinkedIn tasks. Solo is $12/mo, Pro is $39/mo.
2. Sending-first stack
Instantly or Smartlead + data source + verifier + a CRM. Strong if you already live inside one of those tools. The cost is another login and another place where multi-product context has to be rebuilt.
3. Agency-style stack
Database + sequencer + LinkedIn automation + CRM + reporting. This can work for a team with dedicated operators. For a solo founder, it usually creates more management work than pipeline.
Where the costs actually hide
- Data credits. You pay for contacts you never contact.
- Duplicate sending tools. One tool sends, another tracks, both charge.
- Manual glue. CSV exports, copy-paste, and “which product is this lead for?”
- Deliverability damage. The most expensive line item is a burned domain.
- Seats. A tool that is cheap for one seat gets expensive as you add help.
Where PortKnot fits — and what it does not do
PortKnot is the command layer for multi-product outbound:
- One workspace; a project per product
- AI drafts with human approval; no auto-send
- BYO Resend; platform-managed sending on paid plans
- Signal ingestion on Pro; 500 signals on Solo
- Manual LinkedIn tasks; no LinkedIn automation
- Reply-stop across email and task steps
It is not a contact database, a CRM, or a LinkedIn bot. If you need those jobs, keep a dedicated tool and connect the workflow at the edges.
A simple decision rule
Buy the smallest stack that lets you answer four questions every week:
- Which product am I pushing?
- Which 25–50 people have a reason to care now?
- Who approved the message?
- What stops when someone replies?
If a tool does not improve one of those answers, it is probably overhead.
FAQ
Do I need a separate email tool for each product?
Usually no. Separate projects inside one sending system can keep ICPs and templates distinct while sharing suppression and billing. Use separate sending domains only when the products genuinely need different reputation.
Does PortKnot include a lead database?
No. PortKnot works with leads you import or crawl and verifies MX records; it does not sell a contact database. You can use your own data source.
Can I use PortKnot with my existing Resend account?
Yes, on Solo and Pro. Connect your Resend API key; PortKnot encrypts it and uses it for sending. Trial uses platform-managed sending.
Start with the command layer, not another database.
Solo $12/mo for email-only GTM. Pro $39/mo for multi-channel tasks and 5,000 signals.
See plans →