OutreachFlow

A credit-metered SaaS that runs the whole SEO outreach workflow from one dashboard.

Type
SaaS platform
Role
Solo build: architecture, planning and all of the development
Context
MVP delivered in about four months
Links
app.outreachflow.ai
OutreachFlow dashboard showing available credits, on-hold credits and outreach activity

01Overview

OutreachFlow helps SEO professionals and marketing teams run the complete outreach process in one place: finding opportunities, enriching them with data, and contacting the right people.

Every paid action, whether finding a website, finding an email, pulling metrics or sending a message, is metered in credits that users get through Stripe subscriptions.

02What I built

  1. Users discover outreach opportunities, save searches, organize websites into databanks and custom lists, find contact emails and retrieve SEO metrics such as Domain Rating, Domain Authority, traffic and Trust Flow.
  2. The platform connects SMTP and IMAP mailboxes for campaign management, inbox warmup and reply handling, and includes activity tracking, CSV import and export, support tickets, notifications and detailed credit reporting.
  3. The entire authenticated product, user and admin alike, is a single FilamentPHP panel. There is no separate SPA; Livewire handles interactivity, and admin-only resources are gated rather than split into a second app.
Laravel 11FilamentPHPLivewireMySQLStripe & CashierOpenAIDatabase queuessystemd

03Engineering notes

01Credits that can’t be overspent

A naive "balance ≥ cost" check lets two concurrent jobs sell 160 credits of work against a 100-credit balance. Long-running jobs reserve their estimate as a pending activity, and spendable balance subtracts everything on hold. When a job completes, an observer charges the actual amount exactly once; if it fails, the charge drops to zero.

php
public function getAvailableCredits(): int
{
    return max(0, $this->getRemainingCredits() - $this->getOnHoldCredits());
}

02Five queues, so slow work never starves fast work

Crawling, enrichment and email sending run on the database queue driver, split across five named queues with dedicated workers: fast, slow, sending, a priority lane for replies, and one for an isolated subsystem. The default queue stays empty by rule; every job declares its queue, timeout, tries and backoff.

php
public string $queue = 'slow';
public int $timeout = 600;
public int $tries = 2;
public array $backoff = [30, 120];

03Idempotent billing

Credits reset on each successful Stripe invoice. The webhook grants them, and the post-checkout redirect runs an idempotent fallback for the race where the user returns before the webhook lands. Both paths key on the invoice ID, so a grant can only happen once.

04A hardening pass driven by production

Early transient failures surfaced missing retry declarations and worker timeouts shorter than job timeouts. The fix was systematic: explicit retries on every job, external-API batches cut from 500 records to 50 with a 15-second stagger, scheduled jobs guarded by both overlap prevention and unique locks, and workers recycled hourly under systemd.

04Interface

→Outcome

A scalable outreach system that brings research, prospect management, SEO analysis, email outreach and subscription billing into one application, maintainable by one engineer across 65+ migrations and a dozen integrations.

Next projectRAG Support Agent

→Get in touch

Building something
interesting?

hi@ahmadthedev.com