Ideas

Planning

Next up

In Progress

Done

Roadmap

Enable easy tracking of leads generated inside platform where client can quickly view the leads generated for different campaigns, view if a meeting has been booked or not, send leads to CRM, channels leads have been engaged, recent touch points with leads, and follow up with leads (follow up can be automated in future)

In Triage

Summary of leads generated

Jeff RvdB

Provide integration support to generate follow-ups for Google based users

In Development

Support Gmail & Google Calendar

Andrei Hirdea

The inbound email routing infrastructure and auto-forwarding via Cloudflare Worker &amp; Postmark

Release 2025-08

Email postmaster routing infrastructure

Linear

Sharable, extendable, and user-friendly delivery tracking questions, metrics, &amp; dashboards w/ alerts-to-exceptions via Metabase

Internal delivery operations BI (Business Intelligence) platform

Implemented multi-layered security architecture for internal API access, combining edge network protection with zero-trust authentication. The solution enables secure automated task execution while maintaining DDoS protection and bot mitigation across different service endpoints. This infrastructure upgrade ensures reliable API access for automated workflows while maintaining enterprise-grade security standards.

Internal services request security (w/ Cloudflare Zero Trust)

<h2>ContactRich Pipeline Refactoring</h2>Project Goal: Modernize the ContactRich Pipeline to handle high-volume contact enrichment and form submissions more efficiently by transitioning from a monolithic architecture to a scalable, event-driven system powered by <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a>.Key Improvements:<ul><li>Decompose the pipeline into distinct, orchestrated stages to eliminate memory bottlenecks when processing large URL volumes</li><li>Implement explicit concurrency controls through <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Trigger.dev">Trigger.dev</a>'s queue management system</li><li>Automate sender email variation generation for improved deliverability</li><li>Organize processing scripts within the existing nx monorepo structure (<code>apps/contact-rich-pipeline/scripts/</code>) using Python and <code>uv</code> package management</li></ul>Expected Outcome: A resilient, scalable pipeline capable of handling enterprise-level contact enrichment workloads with improved performance, maintainability, and monitoring capabilities.

Event-driven service base architecture v2 w/ observability

Robust, fail-safe, and developer friendly tracking, exception handleing, and "health checks"

Form infrastructure/service robustness & downtime mitigation strategy

Release 2025-09

Contact form submission prompt improvements

Personal email-forwarder in cases of no "tagged" client domain

Website v5 revamp

Clean, integrated, and DRY architecture to query, find, and view inbound emails

Query, view, and investigate inbound emails

Centralized dashboard where all outreach activity, across ContactRich, Apollo, and LinkedIn, can be viewed in one place. This would eliminate the need to toggle between platforms and allow sales reps to quickly see whether a company has already been contacted and through which channel.

Sync with CRM to see how many touch points / account / contact

andrew-ringer

Weekly summary report showing which companies were contacted and in which geographic areas. This would help the sales team identify outreach history and coordinate second-touch efforts more effectively, especially when planning in-person visits or follow-ups.

Summary of which accounts were engaged for any given week

Users expressed a strong preference for the ability to reply directly from the same email address that initially sent the message, noting that replies from a different domain appear spammy and may reduce engagement. While current deliverability is generally strong, they flagged a minor risk that responses from new domains may still end up in spam folders, especially without prior domain warm-up. They also shared past experience using mail warmers due to spam-related issues, reinforcing the importance of a robust email infrastructure.

PipeRich