LogiqLead
A B2B lead generation and outreach SaaS with prospecting, sequences, reply detection and a mailbox deliverability audit.
Last updated
The Problem
Founders who run outbound usually stitch together four or five tools: a data source, a spreadsheet, a sequencer, a CRM and a deliverability checker. Data goes stale between them, sequences send from shared domains, and nobody can see which mailbox is healthy.
I wanted one system where prospect data, sequences and sender health live together. I also wanted to understand outbound deeply enough to build it for clients, so I built it as a real product.
The Build
LogiqLead is a multi-tenant SaaS built on ASP.NET Core with Clean Architecture. It has four parts:
- Prospecting module: import leads, remove duplicates, and build segments for campaigns.
- Outreach module: multi-step sequences, follow-ups on a schedule, and reply detection that stops a sequence when the prospect answers.
- Mailbox deliverability audit: checks each connected mailbox’s SPF, DKIM and DMARC records and sending setup before it is used in a campaign.
- Embedded AI assistant: drafts personalized first lines from prospect data. The sender reviews and edits every draft.
The product is currently a working demo. [PLACEHOLDER: demo access details]
Stack
- ASP.NET Core
- Clean Architecture
- Multi-tenant data isolation
- SMTP and OAuth mailbox connections
- Embedded AI assistant
- [PLACEHOLDER: database and front-end framework]
Architecture
Clients
- Web app
- Connected mailboxes
API
- ASP.NET Core API
- Tenant resolution
Application
- Prospecting
- Sequences and follow-ups
- Reply detection
- Deliverability audit
- AI assistant
Infrastructure
- Tenant-scoped database
- Per-tenant SMTP / OAuth senders
- Background jobs
- LLM provider
Key decisions
The choices that shaped LogiqLead, and why I made them.
Per-tenant bring-your-own SMTP/OAuth
Why · Each tenant sends from its own mailboxes, so one tenant's bad list or spam complaints can never damage another tenant's sender reputation.
Tenant scoping enforced in one layer
Why · Clean Architecture puts tenant filtering in the application layer, so no query can forget it and the domain logic stays testable without a database.
Follow-ups stop on reply
Why · A follow-up sent after someone already answered is the fastest way to lose trust. Reply detection reads the connected mailbox and halts the sequence.
The AI assistant drafts, the sender approves
Why · Generated first lines save time, but the sender stays accountable for every email that goes out.
Screens
Prospecting module Outreach sequence builder Mailbox deliverability audit
What it proves
How this build maps to the GTM Engineering modules I offer clients.
- Lead data pipelines
- The prospecting module imports, de-duplicates and segments lead data inside one tenant-scoped store.
- Outbound automation
- Sequences, timed follow-ups and reply detection run without manual tracking.
- AI-personalized outreach
- The embedded assistant drafts personalized openers from prospect data for the sender to approve.
- GTM analytics
- The deliverability audit checks each mailbox's DNS authentication and sending setup before campaigns start.